Tag ManagementWhat is Google Tag (gtag.js)?
The Google Tag (gtag.js) is the shared foundation that loads and configures Google products — GA4 and Google Ads — from a single snippet. It is the most common single technology in our scan corpus because nearly every Google-powered setup relies on it.
Why Google Tag (gtag.js) matters
A Google Tag being present tells you a site uses Google’s measurement stack, but not whether it is configured well. Duplicate Google Tags, missing consent defaults, and misrouted destination IDs are the everyday problems it hides.
Sites using Google Tag (gtag.js)
A sample of domains in the TagStack index where Google Tag (gtag.js) was detected.
What's usually deployed alongside Google Tag (gtag.js)
Share of indexed containers running Google Tag (gtag.js) that also run each tool. Based on a sample of the index, so treat these as approximate.
Is your Google Tag (gtag.js) set up correctly?
- Only one Google Tag loads per destination — duplicates cause double-counting.
- Consent defaults are set before the tag configures Google products.
- The tag routes to the correct GA4 / Ads destination IDs.
See Google Tag (gtag.js) on any website
Enter a URL to reveal its full tracking stack — every tag, pixel and consent tool — in seconds. No login or code access required.
Common Google Tag (gtag.js) alternatives
Google Tag (gtag.js) FAQ
TagStack has detected Google Tag (gtag.js) in 1,146,883 Google Tag Manager containers across its index of 3,278,587 scanned domains. That reflects sites deploying Google Tag (gtag.js) through GTM, so sites that install it directly in their source code are not counted.