Build in public · Tracking

Google Ads said my website was missing a Google tag. The tag was there.

Maria Waters · 27 August 2026 · 5 min read

I build a Google Ads audit tool. In August, every campaign in my own account was flagged Eligible (Misconfigured) — Your website is missing a Google tag. My own tracking health check showed eight green ticks. Both were telling the truth, which is the interesting part.

Part one: it genuinely was missing

The first answer was embarrassing and simple. The marketing site carried the GA4 tag and nothing else. Google Ads' checker looks at an ad's landing page for the Ads (AW-) tag specifically, and it wasn't there. My tracking checks had interrogated the Google Ads account's configuration — conversion actions, statuses, counting settings — and none of them read what Google itself was already saying about the campaigns. I added the AW config, and a check that reads each campaign's primary status and its reasons, the same day.

Then the flags didn't clear.

Part two: the tag that was present and said nothing

I verified the tag on every page three times. Present, correct, loading. So I pointed a headless browser at the site and watched the network, which is the only thing that settles arguments like this.

With consent denied — the default state, and the state every crawler is permanently in — the Google Ads tag made zero requests to any Google Ads endpoint. Not a cookieless ping, nothing. After clicking Accept: five requests, immediately.

I tried the things you'd try: ads_data_redaction on and off, loading gtag with the AW id instead of the GA4 id, firing an explicit conversion event. All zero until consent was granted.

So for Google Ads specifically, on this setup, Consent Mode v2 behaves like basic mode: the tag loads, configures, and then stays silent until someone accepts. Google Ads has never received anything from the container, and it cannot tell "silent" from "absent". Hence the warning.

What that means for you

1. The warning is your consent rate showing up in the Ads UI. On a B2B site where most visitors ignore the banner, Google may never hear from your tag at all. No code change clears it; enough accepting visitors do. Verify the tag is present once, then stop hunting the HTML.
2. It doesn't stop ads serving. "Eligible (Misconfigured)" is still eligible.
3. The real problem is measurement, not the warning. Every non-consenting visitor is invisible for attribution — not modelled, not estimated. On a low-traffic site your conversion data is a sample of the people who clicked Accept. Worth saying out loud before anyone optimises bids on it.

The 90-second check for any site

DevTools → Network → filter doubleclick → hard refresh without touching the cookie banner. If the list is empty, Google isn't hearing from you either. Then click Accept and watch it fill up.

What I changed in the tool

Two things. The tracking audit now reads Google's own verdict on each campaign — primary status and reasons — instead of only inspecting configuration; and the site scanner records what the tags actually send, with consent denied and with consent granted, rather than whether they're present. Both came from being wrong about my own account, which is the only way I've ever learned anything useful about tracking.

Tested 10 August 2026 on campaignowl.co.uk with a headless Chromium session and Consent Mode v2 defaults set to denied. Your results will depend on your tag setup and consent tool.