TrackCanary guide · Pixel and conversion tracking checks

How to check if Google Analytics (GA4) is working

You added the GA4 tag, published, and saw... nothing obvious change. So the natural question is: is Google Analytics actually working? A GA4 tag can be on the page and still send nothing — wrong measurement ID, a consent signal it never gets, a tag that fires on the homepage but not the pages that matter. This guide covers four practical ways to check whether GA4 is really collecting data, from the Realtime report to a quick look in your browser's devtools, and what 'working' has to mean before you trust a single report.

TrackCanary checks visible browser-side signals. It does not prove final attribution accuracy, ad account setup, analytics account data, legal compliance, or every possible conversion event. Manual verification may still be recommended.

Installing GA4 is not the same as GA4 working

A GA4 tag is a small piece of JavaScript (gtag, or a GA4 tag inside Google Tag Manager) that sends events to your Analytics property. Adding it to the page and having it actually send data are two different things.

A tag can sit on the page and send nothing: the wrong measurement ID, a consent banner that blocks it, a trigger that never fires, or a container that was never published. And a tag that works on your homepage can be completely absent on the checkout or campaign landing page where the data really matters.

So the goal is not 'is the tag there' — it is 'are events actually reaching my GA4 property, on the pages I care about'.

Method 1 — The Realtime report

The fastest sanity check is the Realtime report. In GA4, open Reports and then Realtime, then visit your own site in another tab.

Within a few seconds you should see yourself appear — an active user, your page, the events you trigger. If Realtime stays empty while you are clicking around your own site, GA4 is not receiving data, and that is the signal to dig deeper.

Realtime confirms data is flowing, but it does not prove every event and parameter is correct — for that you want DebugView.

Method 2 — DebugView and the GA debugger

DebugView shows the exact events coming from one device in debug mode, in real time — the best view for QA. You put your session into debug mode, then watch each event stream in with its parameters.

There are a few ways to switch debug mode on:

  • Install the Google Analytics Debugger Chrome extension and toggle it on — it also prints verbose event logs to the browser Console.
  • Use GTM Preview mode, which sends your session's GA4 events to DebugView automatically.
  • Then open GA4 → Admin → DebugView and watch events appear as you interact with the site.

Free tracking check

See what’s visible on a real site.

Run a free browser-based scan — no login, no install, ~10 seconds.

Run a free check

Method 3 — Check the hits in browser devtools

You can also confirm GA4 is sending data without any extension:

  • Open devtools → Network tab, reload the page, and filter for 'collect'. Requests to google-analytics.com/g/collect mean GA4 events are being sent.
  • Click a collect request and check the tid or measurement ID — it should match your G-XXXXXXXXXX property, not an old or wrong one.
  • Trigger an action (a click, a form submit) and watch for a matching collect request to fire.
  • No collect requests at all means the tag is not sending — go back to the tag or container setup.

What 'working' actually means

A real pass is more than one green check. Four things all have to line up, and the methods above each cover part of it:

  • Events are actually sent (collect requests fire).
  • They go to the right property (the measurement ID matches).
  • The events and their parameters are the ones you expect.
  • It happens on the pages that matter, not only the one page you tested.

The catch: these are all one-time checks

Realtime, DebugView, the debugger extension, and devtools all share one limit: they confirm GA4 works in the session you are watching, right now. They tell you nothing about next week.

Most analytics failures show up after launch, silently — a redesign drops the tag, a consent update starts blocking it, a developer removes a script. Nobody has DebugView open at the moment it breaks, so the data just quietly thins out or stops, and you often notice only when a report looks wrong weeks later.

So a one-time 'it works' is worth re-confirming on a schedule, not just once.

The fastest check: a free GA4 checker on a live URL

When you just want a quick answer for one page, you do not need to open GA4 at all. TrackCanary's free GA4 tracking checker inspects a live URL and tells you whether a GA4 tag is present and loading on it, in seconds.

Use it as your fast first pass on the exact page that matters, then reach for DebugView or the debugger extension when you need to verify specific events. And when analytics has to stay reliable over time, monitoring re-runs that check for you so a future change can't quietly stop your data.

Next step

Check if GA4 is live on any URL — free

Run a free GA4 tracking check on any live page to confirm the tag is present and loading, then keep it monitored so a future change can't stop your data unnoticed.