Tag Watch: how detection works
Tag Watch reads the HTML your server returns, without running it, and looks for these vendors:
- Google Tag Manager container IDs (
GTM-) - Google Analytics 4 measurement IDs (
G-) - Google Ads tags (
AW-) - Meta Pixel IDs (from
fbq('init', ...)) - LinkedIn Insight Tag partner IDs
- TikTok Pixel IDs (from
ttq.load(...))
What we count
- Standard install snippets: a script URL that carries the ID (
googletagmanager.com/gtm.js?id=GTM-...,gtag/js?id=G-..., the TikTok pixel script), the Google Tag Manager loader call,gtag('config', ...)and thesend_toof a gtag event,fbq('init', ...),_linkedin_partner_id = ...,ttq.load(...), and the no-JavaScript fallback images and iframes. - Named references (shown as lower confidence): a Google ID that is the whole value of a string assigned to a name that mentions a tag, such as
window.ANALYTICS_GTM_ID = "GTM-..."or a script attributedata-gtm-id. Sites that load tags through their own code often look like this. - Consent-held scripts: scripts with
type="text/plain", which consent tools use to hold a tag back until a visitor agrees, are read and marked as held for consent.
What we ignore
- IDs inside HTML comments or JavaScript comments.
- IDs in visible text, in JSON or JSON-LD data blocks, in templates, or inside a textarea.
- An ID inside a longer piece of text (for example
"GTM-ABC was removed"), a whole snippet quoted inside a string, or an ID passed to an unrelated call such asconsole.log. - Placeholder IDs from install guides, such as
GTM-XXXXXXXorAW-123456789.
Heuristics and limits
- We separate code from comments and strings with a small JavaScript reader. It decides whether a
/starts a regular expression from the character before it, which is the usual rule but can be fooled by unusual code. - GTM container IDs in the page HTML are checked; the container file itself is not read.
- Inline scripts are read up to 256 KB per page (small scripts first, where install snippets usually sit), and up to 2,000 script and 2,000 image or iframe elements; a page that needs too much work to read is reported as "could not be checked (page too complex)", never as a missing tag.
- Scripts with
type="text/partytown"are read like normal scripts; other unknown script types whose source is a vendor URL are treated as held for consent. Agtag('config')withsend_page_view: falsedoes not count towards "configured twice". - GA4 and Google Ads destinations that are configured only inside Google (for example through a Google tag with a
GT-ID) are not visible in the page. - Tag Watch reads the HTML your server returns. It does not run the page, so it cannot see tags that other scripts add later, tags a consent tool holds back until a visitor agrees, tags added by custom or server-side loaders without the standard install code, what a Partytown worker loads, or tags on pages it is not watching.