Consent Mode v2
Definition: Consent Mode lets you communicate your visitors’ cookie or app identifier consent status to Google, so that Google tags adjust their behaviour. It covers consent types, including ad_storage, analytics_storage, ad_user_data (sending advertising-related user data) and ad_personalization (personalised ads). You set defaults at load and update them when the visitor chooses.
It is Google’s solution for its own tags. It does not set consent for the shop and does not replace the consent banner or the cookie policy.
Also called: Google Consent Mode, consent signals, ad_user_data, ad_personalization
The demo has sample data; the login comes to your e-mail.
Why it matters for a shop
If a shop runs Google Ads campaigns or uses Google tags, passing the visitor’s choices decides which data Google may use for measurement and personalisation. A missing consent signal is a legal risk and a gap in measurement, so agree it with whoever owns consent.
How Basketly handles it
- The Basketly shop script does nothing until the consent tool calls setConsent(true), and withdrawing consent clears local data and deletes the stored attribution.
- Google click ids (gclid, gbraid, wbraid) are stored only after consent.
- This is not Consent Mode: consent signals for Google tags are set by the page’s consent tool.
Sources
- Google for Developers: Manage consent settings (consent mode): https://developers.google.com/tag-platform/security/guides/consent (read 2026-10-29)
- Google Analytics Help: About consent mode: https://support.google.com/analytics/answer/9976101 (read 2026-10-29)
What Consent Mode v2 does not do
- Consent Mode does not replace the consent banner or the cookie policy and is not legal advice.
- Setting the mode does not make measurement complete: that depends on what visitors choose.
ad_user_data and ad_personalization joined the earlier ad_storage and analytics_storage, as Google’s tag documentation describes.
It depends on which Google tags you use and for which audiences. Settle the rules with whoever owns consent and legal.
No. It is a Google tag mechanism. Meta has its own rules, and consent to collect fbp and fbc is set by the page’s consent tool.
See also
- Enhanced conversions (Google Ads)A Google Ads feature that supplements conversion measurement with hashed customer data from the shop.Read
- fbp and fbcTwo browser identifiers that help Meta tie a purchase to an ad click.Read
- Conversions API (CAPI)Sending events, such as purchases, to Meta from the shop’s server instead of the buyer’s browser.Read
- ConversionsShop purchases sent server-side to Meta and seven more platforms, and a day-by-day balance: how many orders, how many purchases accepted and where something got lost.Read
- GDPR and the Meta Conversions API: Hashing, Lawful Basis and How Long to Keep Customer DataIs SHA-256 hashing enough to send customer data to Meta under GDPR? Who is controller and processor, lawful basis, the DPA and how long to keep customer data.Read
Get started in under 5 minutes
Connect your shop and Meta and see how many purchases really arrive.
- Free up to 100 orders a month
- No developer needed
- Purchase balance and self-check