Skip to content
Google tag checker / Free

Check your Google tag without Tag Assistant.

Find every Google tag on a page, the Google Ads and GA4 IDs it carries, whether it runs through GTM or is hard-coded, and which ad blockers stop it. Then see whether the gclid from an ad click survives.

Free · No extension · No signupSee a sample report

We load public pages only. Every tracking request the page makes stops in our browser, so GA4, Google Ads, Meta and the other ad platforms never receive it. Scan results may be used in aggregate for published studies. Terms

Google tag checker

What the Google tag check looks at

Google’s tag carries both your Google Ads conversions and GA4, so when it’s blocked both go quiet.

01 Every ID AW- Google Ads IDs, G- GA4 IDs and GTM- containers, and whether one tag is loaded twice.
02 Blocked or not Whether gtag.js and the conversion hits get past uBlock Origin, Brave, AdGuard and DNS blocking, with the rule that matched.
03 gclid, gbraid, wbraid We land with test click IDs and read what ends up in _gcl_aw and the other Google cookies, and who set them.
04 Consent Mode The ad_storage, analytics_storage, ad_user_data and ad_personalization defaults the page sets, if any.
What it checks

Not what’s installed. What gets through.

Other checkers list your tags. This one asks which conversions the ad platforms will never hear about, and why.

Tags and stack Google tag, GTM, GA4, Google Ads, Meta, Microsoft, TikTok, LinkedIn, Pinterest, Snapchat and Reddit, plus your platform, consent banner and any server-side endpoint.
Ad blocker test Each tag against uBlock Origin, Brave, AdGuard and DNS blocking: loads, blocked, or swapped for a stand-in script. Today we match against each blocker’s lists.
Click ID survival Test gclid, gbraid, wbraid, msclkid, fbclid and ttclid, followed through redirects to the cookie each one lands in.
Consent Your consent banner, the Consent Mode defaults, and every ad request sent before the visitor chooses.
Duplicates The same event sent twice, like GTM plus a hard-coded gtag, or two Meta pixels. Double counting skews bidding.
Page weight Third-party script bytes and the main-thread time your tags cost.
Real-browser blocker runsComing soon Each blocker in its real browser: Firefox with uBlock Origin, Brave, Chromium with AdGuard.
Conversion pageComing soon Paste your thank-you page and check the conversion tag fires with a value, currency and transaction ID.
No extension

Every platform at once, in a clean browser.

Meta Pixel Helper and Tag Assistant each check one platform, in your own browser. They’re the right tools for watching events fire live. This is the one that shows what ad blockers do to all of them.

This checker Meta Pixel Helper Tag Assistant
Platforms in one check Every ad and analytics tag Meta Pixel Google tags
Where it runs A clean browser on our side Your own browser Your own browser
What you need Nothing A Chrome extension Google’s web app, connected to your browser
What ad blockers do to each tag Four blockers No No
Click IDs followed to the cookie Six click IDs No No
Watch events live as you click No Yes Yes
Safe to run on any site

A scan reads your page. The tracking stops in our browser.

Scan your own site, a client’s or a prospect’s. The checker loads the page the way a first-time visitor does, and records every tracking request without letting it leave.

01 Nothing reaches your accounts Every tracking request the page makes is recorded and stopped in our browser, so GA4, Google Ads and Meta never receive it.
02 No forms submitted We load pages and read them. We never fill in or submit a form on your site.
03 Public pages only Private, internal and local addresses are refused, and only ports 80 and 443 are loaded.
04 No CAPTCHA tricks If your bot protection turns the checker away, the report says so. We never solve or get around a CAPTCHA.
For agencies

The opening line of your next pitch.

Scan a prospect’s site and send them what their tracking is missing. The fix is yours to sell.

The agency program →
Prospect audits in your brandingComing soon Your logo, accent color and contact details on the report, as a share link and a PDF.
Bulk scansComing soon Up to 50 URLs at once, ranked by score, with each site’s worst problem and a CSV.
Weekly monitoringComing soon An email when a client’s tag disappears, click IDs stop surviving, or a blocklist starts catching their endpoint.
Same scan, different starting point

Questions about the checker

How is this different from Tag Assistant?

Tag Assistant connects to your site in your browser and lets you watch Google tags fire as you click through, which is the right tool for debugging events. This checker needs nothing installed, checks every ad platform’s tag at once, and shows what ad blockers do to each one.

Can it see the conversions Google Ads receives?

Not yet. Connecting a Google Ads account read-only, to set what Google receives beside what your site sends, is coming soon.

Is the tracking checker free?

Yes. The score, the top problems, the tag map and the ad blocker test are free with no signup. The full report, with every finding and fix steps for your platform, comes by email.

Will a scan show up in my analytics or ad accounts?

Not from the browser. We record every tracking request the page makes and stop it there, so GA4, Google Ads, Meta and the other ad platforms never receive it. Your server still sees the page load, like any visit, so a tool that counts visits from server logs, or sends an event from your server when a page loads, can count it.

Which ad blockers do you test?

uBlock Origin, Brave Shields, AdGuard, and DNS blocking with hagezi Multi PRO and AdGuard’s CNAME tracker list, as Pi-hole and NextDNS use them. Today we match each request against those blockers’ default lists, and every report names the list versions and the date. Running each blocker in its real browser is coming soon.

How is the score worked out?

It weights the four things that lose conversions: ad tags blocked, click IDs lost, consent gaps and a broken conversion page. It only counts the checks that ran, and it’s a heuristic, not a measurement of your lost revenue.

Why couldn’t you scan my site?

Usually its bot protection refused a headless browser. We never solve or get around a CAPTCHA, so the report says it couldn’t scan the site. Your developer can allow the checker, or you can try another page on the same site.

What do you do with scan results?

We store the result so your report link works. Scan results may be used in aggregate for published studies, such as what share of sites run server-side tracking. We load public pages only and store no visitor data.

Find out what your pixels are missing.

The ad platforms optimize on the conversions they receive. See which ones they don’t.

Free · No extension · No signup