datascale

Tool

Google Consent Mode June 2026 Audit Checklist

A free 7-layer checklist to audit your GA4 and Google Ads Consent Mode setup after the June 15, 2026 single-control change. PDF + editable Google Sheet.

A structured, layer-by-layer way to confirm your GA4 and Google Ads Consent Mode setup actually works — after the June 15, 2026 change made Consent Mode the single control for Google Ads data collection from GA4-linked setups. For analytics, marketing, and engineering teams who need to verify, not assume.

New to the change? Read the full explainer: What the June 2026 Google Consent Mode change means for GA4 and Google Ads.

Who this checklist is for

  • Analytics leads confirming GA4 to Google Ads linking and consent settings.
  • Performance marketers worried about conversion, audience, and bidding impact.
  • Engineers who own the tag layer, default and update calls, and server-side GTM.
  • Privacy and legal stakeholders who need the setup documented (this is operational guidance, not legal advice — review requirements with counsel).

If your team has ever said "Consent Mode is enabled" without testing the accept and reject paths, this checklist is built for you.

Why audit now

The June 2026 change relocated where Google Ads data collection is controlled — from GA-side settings to Consent Mode. The practical risk is broader than compliance:

  • Unobserved conversions when ad signals stay denied after consent.
  • Smaller or stale audiences traced back to consent transmission, not lists.
  • Weaker Smart Bidding learning on a holed signal, quietly raising cost-per-acquisition.
  • Inconsistent reports that erode trust with finance and leadership.

A misconfigured consent chain now shows up as a measurement problem first and a compliance problem second. The checklist helps you catch both.

What's inside

The checklist mirrors The Datascale Consent Control Audit — our 7-layer model — and turns each layer into concrete checks with failure signals, a validation method, and an owner column:

  1. Consent banner and CMP configuration — is the CMP actually wired to Consent Mode, or just displaying a banner?
  2. Default consent state — is a default set before any Google tag fires?
  3. Consent update behavior — does an update call fire on the user's decision and change the signals?
  4. Google tag and GTM consent settings — are all four signals (analytics_storage, ad_storage, ad_user_data, ad_personalization) set?
  5. GA4 to Google Ads linking — does your setup reflect the June 2026 model?
  6. Conversion and audience activation — are conversions observed and audiences populating as expected?
  7. Reporting, documentation and governance — is the chain documented with a named owner per layer and a "last reviewed" date?

Formats: a print-friendly PDF for review meetings, plus an editable Google Sheet you can copy, assign owners in, and track status against.

Preview — 5 representative checks

You don't need the download to start. Here are five checks straight from the file:

  1. Default-before-tags: In the network panel, confirm a Consent Mode default appears before any Google tag request. Failure signal: tags fire with no consent state (a classic SPA race condition).
  2. Update on accept: Click accept and confirm advertising signals flip from denied to granted. Failure signal: conversions and audiences stay flat after consent — the update call never fired.
  3. All four signals present: Check that ad_user_data and ad_personalization are set, not just analytics_storage and ad_storage. Failure signal: a partial, v1-era template.
  4. Reject path holds: On reject, confirm advertising signals remain denied and no ad cookies are written. Failure signal: tags ignore the rejection.
  5. Server-side parity: If you run sGTM, confirm the server-side consent state matches the client. Failure signal: client says granted, server forwards denied (or vice versa).

Each check in the full file also lists the validation method and the team that should own the fix.

How to use it

  1. Make a copy of the Google Sheet and assign an owner to each of the seven layers.
  2. Run the checks in a single session across web and (if applicable) server-side.
  3. Log status (pass / fail / needs-fix) and a screenshot or note per check.
  4. Fix the signal chain first — default, update, four signals.
  5. Re-run conversion and audience checks after fixes; set a "last reviewed" date.

Get the checklist

Enter your details to download the PDF + Google Sheet. Soft gate — you'll see the download on the next page. We'll only use your details as described in our privacy policy.

Form fields: Work email · Company · Role · Current stack (GA4 / Google Ads / GTM / Server-side GTM / CMP / BigQuery / Other) · Consent checkbox.

Want a second pair of eyes instead of a DIY pass? Datascale can audit your GA4, Google Ads, GTM, CMP, and server-side tracking setup end to end — book a Measurement & Consent Audit Sprint.

  • Q01
    Is the checklist really free?

    Yes. Enter your work email and a few details and you get the PDF and the Google Sheet link on the next page. It is a soft gate, not a paywall.

  • Q02
    Will it tell me if I am GDPR-compliant?

    No. It is a technical and operational diagnostic. Compliance conclusions should be reached with qualified legal counsel, not from a checklist.

  • Q03
    Do I need server-side GTM to use it?

    No. There is a dedicated layer for server-side GTM, but the checklist works for client-side-only setups too.

  • Q04
    Is this Google-official?

    No. It is Datascale's framework, built on Google's official documentation, which is linked throughout the companion article.

More than 2 red checks?

An Audit Sprint delivers a prioritised action plan in two weeks.

Request an Audit Sprint →