The technical details.

We verify that the Google tag script (gtag.js) is present on the page, placed high enough in the <head> to fire early, loaded asynchronously so it doesn't block your site, and that it actually executes a network request to Google's servers when the page loads.

Why your business cares.

Gtag.js is the file that does all the heavy lifting for GA4. If it isn't loaded or isn't loaded correctly, none of your other tracking matters — no events, no conversions, no audiences, no reports. Even subtle problems (loading too late, loading twice, loading in the body instead of the head) silently corrupt your data.

What you're missing.

  • Pages that don't fire gtag.js are invisible to GA4 — they don't show up in real-time, page reports, or any funnel.
  • Late-loading scripts miss visitors who leave quickly, which under-counts bounce-prone traffic like mobile or paid ad clicks.
  • Body-placed scripts can race with other tags and double-fire — inflating page views by 50-200%.

What this looks like in different businesses.

A Shopify store launches a new theme. The dev forgets to add gtag.js to the product template. For three weeks, every product page view is missing from GA4 — the brand thinks their best sellers have zero traffic and pulls ad spend from them.

A B2B SaaS company loads gtag.js inside their cookie banner. Visitors who don't immediately accept consent never get tracked at all, even after they accept — so the conversion path from anonymous visitor to free trial is invisible.

A news site loads gtag.js at the bottom of <body>. Readers who skim the headline and bounce within 2 seconds aren't counted — making their actual top-of-funnel reach look 30% smaller than reality.

Curious about your site?

Find out if this is happening on your site.

A free audit runs all 12 detectors — including Gtag Script Detection — on every page of your site.

Request a Free Audit