Developers rebuilding GA4 pipelines this quarter: this is the debug guide you need. Since 15 June 2026, the way GA4 handles user and ad data has shifted. Google Signals no longer controls what flows into Google Ads.
Consent Mode does. Sites that missed the update are seeing smaller audience reports, dropped Enhanced Conversions and Google Ads Smart Bidding drifting off target. Here is the step-by-step patch every dev team should run this sprint.
The Seers guide on Google Signals and Consent Mode in GA4 covers each Admin screen with screenshots.
What Google Signals is
Google Signals joins a person's sessions across their phone, laptop and tablet when they are signed into Google with Ads Personalisation on. It enriches demographics, interests and cross-device paths inside GA4. It does not fire tags and does not manage cookies. It only enriches data that has already been collected with consent.
What Consent Mode is
Consent Mode is the gatekeeper. It reads four flags before any Google tag runs: ad_storage, analytics_storage, ad_user_data and ad_personalisation. Basic mode blocks tags until the visitor accepts. Advanced mode sends cookie-less pings when consent is denied, which GA4 later feeds into behavioural modelling.
Why the order matters
Consent Mode runs first. Google Signals runs after, using only what consent allows. If your CMP loads late, the first pageview slips through with default values and Signals has nothing to enrich.
Behavioural modelling thresholds
Modelling only turns on when GA4 sees 1,000 daily events with analytics_storage denied for 7 straight days, plus 1,000 daily users with it granted for 7 of the past 28 days. Modelled data usually appears in reports within 7 to 14 days once both bars are cleared.
Real business impact
Enhanced Conversions and Google Ads Smart Bidding both read Consent Mode signals. A stale setup thins Smart Bidding inputs and drags campaign performance. A non-compliant setup can also trigger GDPR fines of up to 4% of global annual revenue under Article 83 of the UK and EU GDPR.
How to fix your setup
Turn Google Signals on in Admin > Data Collection.
Move your CMP tag to the top of Google Tag Manager firing order.
Switch to Advanced mode with your legal team's sign-off.
Validate with GA4 DebugView, Google Tag Assistant and Consent Mode Diagnostics.
Why teams pick Seers over building it
If you want to skip custom code, Google Consent Mode v2 by Seers is a TCF-certified consent banner that plugs into Google Tag Manager in minutes, writes default consent values before any Google tag loads, and handles all four flags automatically.
Bottom line
Run this in a staging property first with a fresh Chrome profile, then push the same config to production. Modelled data starts flowing back within 7 to 14 days once both thresholds are met.
50,000+ websites already run their cookie consent through Seers.ai, which includes a free cookie audit that flags weak points on your site in seconds.
Top comments (0)