Analytics and tracking
How do I check that GA4 is working on my website?
GA4 is working when each important action is sent once, arrives in GA4 and is marked as a key event. Your own visits, unwanted referrals and consent choices must also be handled. Test in Tag Manager Preview and GA4 DebugView first, then confirm in your reports.
Published . Last updated . By Hevaris.
What should a GA4 health check cover?
A health check covers nine things: whether events arrive, whether they are key events, and whether internal traffic, referrals, Search Console, consent, campaign links and access are set up correctly. Work through them in order, because the first three show whether data arrives at all.
| No. | Check | What to look at | A pass looks like |
|---|---|---|---|
| 1 | Each page sends its page view once | Tag Manager Preview for which tags fired and in what order, and DebugView for the events | One page view arrives for each page load |
| 2 | Important actions send events | Trigger each action yourself, such as a form submission or a phone click, and watch DebugView | Every action you care about arrives as its own event |
| 3 | Important events are key events | Whether each event is marked as a key event, and whether the Key events column in reports shows it | Each important action is marked |
| 4 | Your own visits are excluded | The internal-traffic rule and the state of the data filter | A rule exists, the filter is active, and your test visits no longer appear |
| 5 | Unwanted referrals are excluded | The referral exclusion list | Domains such as payment processors are not reported as referrals |
| 6 | Search Console is linked | The link between the GA4 property and the Search Console property | The two Search Console reports show data |
| 7 | Consent choices are respected | Test the site once with consent accepted and once with it declined | Tags behave differently for the two choices |
| 8 | Campaign links are tagged consistently | The utm values on links you control | Values are consistent, with one source value per platform |
| 9 | Access is in your hands | The access list for GA4 and Tag Manager | You hold an administrator role, and nobody who has left still has access |
Checks 4 to 9 matter because a failure in any of them changes what the reports show, even when events arrive.
How do I run the first three checks?
Use Tag Manager Preview to see whether the tag fired, then DebugView to see whether the event arrived. The two tools answer different questions, so use both.
- Open Tag Manager Preview. Google says preview mode lets you browse your site as if the draft container were deployed, and shows which tags fired and in what order.
- Open GA4 DebugView. DebugView shows the events GA4 collects in real time. Google says you must enable debug mode to use it, which preview mode or Tag Assistant does for your own device.
- Trigger each action. Load a page, submit the form, select the phone link, and tick each one off as the event arrives.
- Check the key events. Google says any collected event can be marked as a key event, and that reports include a Key events column.
How do I test consent and internal traffic?
Test consent by visiting once with consent accepted and once with it declined. Test internal traffic by checking the rule and filter, not by guessing.
- Consent. Google says DebugView does not show events when consent mode denies analytics storage, so an empty DebugView during a declined visit is expected.
- Internal traffic. Google says internal traffic is defined by IP address, that a data filter has testing and active states, and that an active filter changes the data permanently. Leave a new filter in testing first.
How long should I wait before judging the numbers?
Check DebugView immediately, Realtime within a few minutes, and standard reports after a day or more. Google gives different timings for different reports, so a quiet report on day one does not mean a failed setup.
Google says Realtime typically updates within a few minutes, key events can take up to 24 hours to appear in standard reports, and data processing can take between 24 and 48 hours.
What should I do when a check fails?
Fix one cause at a time and test again. The guides on form submissions, unassigned traffic and duplicate tags explain the three most frequent failures in detail.
What sources does this guide use?
The primary sources are linked below, so each statement can be checked at its origin.
- Analytics Help: DebugView
- Tag Manager Help: preview and debug containers
- Analytics Help: key events, limits and roles
- Analytics Help: data filters and internal traffic
- Analytics Help: referral exclusions
- Analytics Help: Search Console integration
- Analytics Help: consent mode
- Analytics Help: data freshness
- Tag Manager Help: user permissions
Frequently asked questions
How often should I run a GA4 health check?
Run one after any change to your site, your consent tool or Tag Manager, because those changes are the usual way tracking breaks. Otherwise, a check every few months is a reasonable habit. This is our suggestion, not a Google requirement.
Can I run the health check myself?
Yes, if you have access to your GA4 property and Tag Manager container. Some changes need a higher role. Google says marking an existing event as a key event needs the Editor role or above, and so does creating a data filter.
Does a healthy GA4 setup count every visit?
No. Visitors who decline consent or opt out of analytics are not fully captured, and Google says GA may model some of that data. A healthy setup gives you reliable trends, not a perfect count of every visit.
What should I fix first when a check fails?
Fix the earliest failing check first. If events never arrive, nothing after them can be right, so start with the tag and the trigger. Change one thing at a time and test again, so you know which change worked.