ConsentCheck

Didomi + Consent Mode v2: How to Verify It Actually Updates

Didomi can collect user consent, but Consent Mode v2 only works if you also push consent state into Google. If you're seeing Google Ads conversion issues, it's often not because Didomi is “wrong” — it's because the Consent Mode v2 updates don't fire when users accept or reject.

Use the checks below to verify your wiring, then run a free scan to confirm what happens on a real browser session.

Quick verify (60 seconds)

  1. Open incognito, show Didomi, then load your page.
  2. In DevTools → Network, filter for pagead or gtag.
  3. Click Accept and confirm requests carry granted consent state (gcs).
  4. Click Reject and confirm the same consent signal becomes denied.

The one requirement

You need two parts working together:
1) default denied Consent Mode v2 runs before any Google tags
2) your Didomi accept/reject flow calls Consent Mode updates (so Google knows whether to grant or deny storage after the user acts).

What to configure in your Didomi integration

When the user clicks Accept in Didomi, you should update Consent Mode to grant the key consent types for Google:ad_storage,ad_user_data,ad_personalization, andanalytics_storage.

When the user clicks Reject, you should update Consent Mode to deny those same types.

If you're not sure where to start

Generate the base Consent Mode v2 snippet (default denied) here, then wire only the “update” part inside your Didomi callbacks:

What to verify in DevTools (the exact evidence)

  1. Open your site in incognito with Didomi shown (no prior consent).
  2. Open DevTools → Network and filter for pagead or gtag.
  3. Click a conversion-related request and look for Consent Mode signals:gcs / gcd.
  4. After Accept, you should see consent updated in the request parameters. After Reject, you should see denied consent behavior.

If gcs is missing, Consent Mode v2 updates aren't being sent to Google. That's a wiring problem, not a “conversion tracking” problem. See why consent state never updates.

Run the full diagnostic scan

The browser checks above are the right evidence. Our scanner automates them (including timing) and tells you exactly what's missing.

Run Free Scan →

Related checks