Mismatch in Google Consent Mode

Waarom dit belangrijk is

Als Consent Mode denied signaleert maar Analytics- of Ads-requests toch laden, wekt de site alleen de schijn van compliance. Meestal zijn defaults, tags of runtime-updates inconsistent geconfigureerd.

Hoe je dit handmatig controleert

1. Open the site in a fresh session and inspect Google requests before any banner interaction.
2. Check whether Consent Mode defaults are set to denied before Google tags initialize.
3. Compare runtime consent state against actual network behavior after Accept and Reject.

Typische oorzaken

• Consent defaults are set too late, after Google tags already loaded.
• GTM tags ignore consent checks even though Consent Mode is enabled.
• Banner updates UI state but does not send a matching consent update to Google.

Fix in GTM

1. Use Consent Initialization for your default denied state before any analytics or ads tags run.
2. Require consent checks on GA4, Google Ads, Floodlight, and remarketing tags.
3. Audit custom HTML tags that may load Google scripts outside GTM consent controls.

Fix in WordPress of CMP-plugins

1. Enable Consent Mode integration in your CMP plugin if available.
2. Verify that plugin-generated consent events fire before GA4 or Ads plugins load.
3. Disable duplicate analytics plugins that bypass the CMP integration.

Algemene developersfix

1. Initialize Google tags only after a denied-by-default consent state is established.
2. Send explicit consent updates on accept and reject actions.
3. Ensure fallback defaults are denied whenever consent state is unknown.

Hoe je bevestigt dat de fix werkt

• Reject optional consent and confirm that Google analytics or ads requests do not fire.
• Accept consent and confirm requests start only after the consent update.
• Run a fresh scan and verify the mismatch finding disappears.