Check if Google Analytics 4 (GA4) tracking is visible on your website

GA4 has a reassuring way of looking healthy. The tag is on the page, Realtime shows a trickle of users, and the property is clearly receiving something — so it feels like analytics is working. But GA4 being present and GA4 recording the events you actually rely on are different things, and the gap between them is invisible from the outside. A page can load the GA4 tag perfectly and still send nothing when someone submits a form, clicks a WhatsApp button, or reaches a thank-you page.

The events that carry business meaning are the ones that break quietly. A consent banner holds the tag until the visitor accepts, a GTM trigger stops matching after a redesign, a key event was never configured, or a site change renames the element an event depended on. PageView keeps flowing, so Realtime looks alive and nothing appears wrong — while the conversions you report on quietly stop being counted. On a page running paid traffic, that runs in the background of a live campaign.

The free check works at the visible layer: it looks for whether GA4 appears present on the public page and flags it for review, alongside the forms, calls, and lead paths that usually need their own events. It does not open the property or prove event delivery — it tells you the tag appears to be there and where the events worth testing live.

GA4 is event-based: beyond the automatic page_view, the events that matter — a lead form, a WhatsApp click, a purchase — have to be defined and marked as key events, then sent from the page when the action happens. That send is the whole mechanism, and it is also the fragile part. If the event is never configured, never triggered, or triggered at the wrong moment, GA4 still looks live from PageView alone while the conversion data is wrong or absent.

Two failure shapes are common and pull in opposite directions. Some actions send no event at all, so real conversions are never recorded. Others fire on page load instead of the real action, so every visit looks like a conversion and the numbers inflate. A visible GA4 tag is not the same as a correctly firing key event, and that difference is exactly what makes a GA4 property's reporting drift away from what actually happened on the site.

The free check works at the visible layer: it looks for whether GA4 appears present and which lead actions are visible on the public page, then flags them for review. It does not access GA4 account data, prove data accuracy, or confirm an event fires — those need DebugView or Tag Assistant with account access. Naming that limit honestly is the point: the scan tells you where to test in GA4, not that the property is fine.

The usual way to verify GA4 is from the inside: open the property, watch Realtime or DebugView, or run Tag Assistant while you click through the site — all of which need account access and check one page at a time from the machine you are on. That is the right tool for confirming exactly what a property receives, but for an agency it is slow, and it needs a login you often do not have for a client's GA4.

TrackCanary takes the opposite approach for the first look. Paste a public URL — no login, no install, no account access — and the check reviews whether GA4 appears present alongside forms, calls, WhatsApp, and other lead paths, all in one pass. It is the fast preflight you can run on any page, including a client's, before more budget goes through it — a way to see whether analytics even appears to be on the page before anyone opens the account.

It does not replace DebugView or Tag Assistant — those still confirm event delivery and data quality downstream. TrackCanary is the step before that: a quick, honest read of what appears visible from the public page, and a way to keep watching it so GA4 quietly dropping off a page after a change does not go unnoticed.