FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 6 of 6

Checking it works and a monthly report

The test script, common mistakes, the monthly page and checklist.

5 min readUpdated 2026-11-16
All chaptersChapter 6 of 6
  1. 01What to track and why
  2. 02Google Tag Manager and GA4 setup
  3. 03Consent done right
  4. 04Events that matter
  5. 05Clarity, Search Console and Bing
  6. 06Checking it works and a monthly report

The short answer

Test every event in Tag Manager preview, confirm it reaches GA4 in DebugView, then send a real form and book a real call and check they arrive once, in GA4 and in your inbox or calendar. After you publish, check again the next day. Then, once a month, compare GA4 with your real lead count, read the channel report, and look for anything that suddenly changed. One page is enough.

The tools you test with

  • Tag Manager preview. Google's preview help says it runs your current draft as if it were published, in your browser only. Click Preview in the Workspace, enter your URL and connect. Tag Assistant then shows which tags fired, in what order and with what data. Regular visitors see nothing. You can share a preview link with a colleague.
  • GA4 DebugView. In Admin, under Data display. Google's DebugView help says preview mode or Tag Assistant puts your browser into debug mode. It also says events will not appear if consent mode is on and you have not consented to analytics, so accept the banner first. A blank DebugView often just means you have not accepted.
  • GA4 Realtime. The Realtime report shows activity from the last 30 minutes. Useful after publishing, when preview is off.
  • Your browser's Network tab. The final word on what actually left the page.

The test script

Run this on the live site or a staging copy, from a tagged test link, with a test email address you can spot later.

ActionIn previewIn GA4In your tools
Load a page and reject the bannerConsent denied, tags held as plannedNothing, or cookieless pings in advanced modeNo analytics cookies
Accept the bannerGoogle tag fires onceOne page view in DebugViewClarity consent shows granted
Click each main buttoncta_click with text and linkSame event in DebugView
Click the email and phone linksemail_click, phone_clickSame events
Send a real formlead_sent custom event, GA4 tag firesOne generate_lead with form_nameLead in inbox or CRM with UTM values
Book a real call on a test event typecall_bookedOne call_bookedBooking in the calendar
Reload the thank-you screen, send an empty formNothing newNo new leadNo new lead

Repeat the form and booking steps on a phone. Then publish the container with a note, and check Realtime the same day and the standard reports the next day.

Common mistakes

MistakeWhat it looks likeFix
GA4 loaded twicePage views roughly double, engagement looks lowRemove every copy outside the container
Lead counted on a thank-you page viewMore leads in GA4 than in the inboxFire on the accepted submit, or guard against reloads
Event fires in preview but never arrivesTag shows as fired, DebugView is emptyCheck consent, the measurement ID and the destination. On our own site, custom events only arrived once they named their GA4 destination with send_to
Staging traffic in reportsVisits from a staging domainLoad tags only on the live domain
Personal data in URLsEmails in page paths or parametersKeep names and emails out of URLs and redirects
Filter switched to Active too earlyReal visits missing for goodLeave filters in Testing until checked, since Active is permanent
Too many key eventsKey events far above real leadsKeep only real outcomes as key events
Tracking broke after a redesignLeads in the inbox, none in GA4Rerun the test script after every form or template change

Most of these show up the same way: the gap between GA4 and the inbox changes. That is why the monthly check below starts with that gap.

The one-page monthly report

Keep it short enough that someone reads it. This is the page we use.

LineSourceWhat to write
Leads this monthInbox or CRMThe real count, by form
Calls bookedCalendarThe real count, minus cancellations if you track them
GA4 coverageGA4 generate_lead divided by real leadsA percentage. Flag it if it moved a lot
Leads by channelGA4, your custom channel groupTop channels, including AI assistants
Top pages before a leadGA4 exploration or path reportThe three pages most leads read
SearchSearch Console and BingClicks, top queries, any new indexing errors
BehaviourClarityOne thing you saw in recordings worth fixing
ChangesTag Manager versions, site changesWhat changed this month that could move numbers
Next actionYouOne fix or test for next month

The Changes line is the one teams skip and later wish they had. A consent change, a new form or a redesigned page can move every number on the sheet. Writing it down the month it happens saves a long argument the month after.

Monthly checklist

  • Compare GA4 leads with the real count. Investigate if the gap changed sharply.
  • Send one test form and book one test call, then delete them from the CRM.
  • Check that every tag in Tag Manager's consent overview is Consent Configured.
  • Look for new scripts on the site that are not in the container.
  • Check that your internal traffic filter still matches your office IP addresses.
  • Review the AI assistants pattern against your source report.
  • Check Search Console and Bing for new indexing or sitemap errors.
  • Watch five Clarity recordings of your highest traffic page on a phone.
  • Update the measurement plan if an event was added, renamed or removed.

For a deeper check once a quarter, run through our GA4 audit.

When to get help

Everything in this guide can be done in house with a few days of care. If you would rather hand it over, our analytics and tracking service starts from $500 and covers GA4, Tag Manager, conversion events and the consent setup, tested the way chapter 6 describes. Care plan clients get tracking upkeep as part of the plan, see the Webflow care plan or the Astro care plan.

We set up and test the technical side. What your site legally needs is for your adviser to decide. Want us to look at your current setup first? Get in touch.

Takeaways

What to remember from chapter 6.

  • Preview first, DebugView second, a real lead and a real booking last.
  • Accept the banner before you expect anything in DebugView.
  • Start each monthly report with the gap between GA4 and your real lead count.
  • Write down what changed each month, so a jump in numbers has an explanation.

Keep a copy

Take the whole guide
as a PDF.

It all stays free to read here. If you want a copy for your team, leave your email and the download link shows up right away.

Nothing gets emailed to you, the link appears on this page. We do not send marketing email unless you ask. Privacy policy

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.