Google Consent Mode tells Google tags what the visitor agreed to. Google requires it for ads personalisation and remarketing for visitors from the EEA and UK.
Turn it on
Go to ClearCrumb → Services & cookies → Consent signals. Consent Mode v2 is on in basic mode by default.
| Mode | Before consent | Good for |
|---|---|---|
| Basic | Google tags are blocked completely. | The safest choice; no data reaches Google before a yes. |
| Advanced | Google tags load with every signal set to “denied” and send cookieless pings. | Sites that use Google’s conversion modelling. |
What ClearCrumb sends
Before any Google tag runs, ClearCrumb sets the default state from the visitor’s saved choice (or “denied” for a new EU visitor), with wait_for_update of 500 ms. On every choice it sends an update for ad_storage, ad_user_data, ad_personalization and analytics_storage.
- Redact ad click IDs while ad consent is denied (ad data redaction) removes ad click identifiers while ads storage is denied.
- Pass ad click info through links while cookies are denied (URL passthrough) keeps click information in links instead of cookies.
Google Tag Manager
ClearCrumb pushes a clearcrumb_consent event to the dataLayer on every choice. Use it as a trigger for tags that need consent, or rely on Tag Manager’s built-in consent checks.
Microsoft UET and Clarity
Switch on Microsoft UET consent in the same card. ClearCrumb sets the UET default and updates it with the visitor’s choice, and sends the Clarity consent signal.
Meta Pixel and TikTok
With Pixel consent APIs on, the Meta Pixel snippet runs with consent revoked and the TikTok snippet runs on hold until the visitor agrees to marketing. Pixels included as a file stay blocked.