Automated · Reads + Writes

Consent Mode v2 on autopilot.

Verify your consent wiring against every tag, catch the gaps Google warns about in Ads, and stage the fixes — without waiting on a developer ticket.

By hand

1–2 days of ad-ops + developer time

With the audit

60 seconds

Run My Free Audit See a sample audit

Why it's painful

Consent Mode v2 is the single highest-stakes chore for every EU advertiser right now. Miss the wiring and Google degrades your Ads campaigns silently — your bid optimization goes blind, your remarketing lists shrink, your reported ROAS drifts. The pain lands in Ads a week after the consent banner changes, and by the time someone notices, two weeks of spend went through on partial signals. The configuration itself is straightforward; the problem is nobody has time to audit the 20+ tags, 5+ triggers, and the banner integration end-to-end every time the stack shifts.

How the audit handles it

Scans every tag in your GTM container for Consent Mode v2 configuration — flags tags that fire before the consent signal, tags with missing `consent_mode` settings, and tags using the legacy v1 API.
Verifies your Consent Mode implementation mode (advanced / basic / custom) matches what Google Ads expects for EEA traffic.
Cross-checks the banner against the tag set: if a banner vendor is detected (OneTrust, Cookiebot, Didomi, etc.), we confirm the `gtag('consent', 'update')` call fires before any tag that depends on it.
Flags the high-risk pattern of a Custom HTML tag firing without a consent trigger guard — the most common silent failure.
Emits a plain-English fix list with the exact GTM tag + trigger configuration change needed. Paste-ready.
Need to ship a banner from scratch? The free Consent Mode v2 Builder generates a jurisdiction-aware scaffold — default-state gtag, accessible banner HTML, GTM variable + trigger template, per-vendor wiring — in under a minute.

Real audit checks

Every check below is a real rule in our audit engine — not a marketing bullet.

GTM-CNS-01Consent Mode v2 presence

GTM-CNS-02Tags firing without consent trigger

GTM-CNS-03Custom HTML tags without consent guards

GTM-CNS-04Legacy Consent Mode v1 API usage

GA4-PRV-02Consent Mode reporting identity alignment

Sample finding

What a real audit report looks like for this chore.

Critical

3 tags firing before consent signal

Business impact

Google Ads cannot use these events for bid optimization in EEA traffic. Expected campaign performance degradation over 14 days as the bidding model loses signal quality. Remarketing audiences built from these events will shrink below usable thresholds.

Recommendation

Add a consent-gated trigger condition to the Facebook Pixel, LinkedIn Insight Tag, and Criteo Loader tags. Use the built-in `Consent State — ad_storage` variable and set the condition to `granted`. Detailed GTM menu path and trigger snippet in the audit report.

Related chores

Reads + Writes

Conversion tracking

Catch duplicate purchase events, drifted measurement IDs, and tags that send revenue to the wrong property. The bugs a GA4 report will never show you.

Reads

dataLayer hygiene

Audit the dataLayer pushes firing on your site, catch PII leakage, identify custom-event naming drift, and surface the variables GTM is already consuming.

Reads

GA4 audit

The 58-check audit a senior consultant would run on day one — Foundation, Data Accuracy, Measurement, Privacy & Security, Optimization. Delivered in 60 seconds instead of two weeks.

Hire a web analyst. Or install one.

Consent Mode v2 is one of 6 high-stakes chores the audit covers end-to-end. Your first audit is free, takes 60 seconds, and catches what your setup has been quietly getting wrong.

Run My Free Audit See every chore →