Analytics

Google Consent Mode v2 Setup Guide for Dubai Websites Advertising to the EU

Published 24 Aug, 2026 Updated 19 Sep, 2026 Analytics 3 min read

This one applies specifically if you run Google Ads campaigns reaching users in the European Economic Area, tourism, e-commerce, and B2B businesses based in Dubai but selling into Europe most commonly. If that’s not your account, this setup doesn’t apply to you and the UAE-focused PDPL post elsewhere on this site is the more relevant read. If it is, Consent Mode v2 isn’t optional.

What Consent Mode v2 Actually Requires

Google requires updated Consent Mode for Google Ads advertising reaching EEA users, built around two consent parameters added alongside the original two. The original pair, ad_storage and analytics_storage, controlled whether advertising and analytics cookies could be set at all. The two additions, ad_user_data and ad_personalization, are more specific: ad_user_data governs whether user data can be sent to Google for advertising purposes, and ad_personalization governs whether that data can be used to personalise ads.

Without all four parameters correctly implemented, ad measurement and remarketing for EEA traffic degrades, and in some cases certain features stop working for that traffic entirely.

Setting It Up

Confirm which consent management platform you’re using. Most major CMPs, the tools that show your cookie consent banner and manage the underlying consent state, added support for the two newer parameters as this requirement rolled out. Check your specific CMP’s own documentation for whether it’s sending ad_user_data and ad_personalization automatically or whether manual configuration is needed.

Verify the signals through Google Tag Manager’s preview mode. Rather than assuming your CMP handles this correctly, load your site in GTM’s preview mode, interact with the consent banner in different ways (accept all, reject all, partial consent if your banner offers it), and check that all four consent parameters update correctly in the data layer for each scenario.

Check your actual Google Ads and GA4 tags reference these parameters correctly. The consent signals need to actually reach the tags that use them. A correctly configured CMP sending the right signals doesn’t help if your Google Ads conversion tag or GA4 configuration tag isn’t set up to respect them.

What Happens If You Skip This

For EEA traffic specifically, incomplete Consent Mode implementation degrades conversion measurement accuracy and can limit remarketing audience eligibility. Google fills measurement gaps with modelled data where possible, but modelled data is an approximation, not a replacement for accurate, consented measurement. If EEA traffic is a meaningful part of your account, this is worth getting right rather than working around.

Frequently Asked Questions

No, Consent Mode v2’s specific requirement is tied to reaching EEA users. A Dubai business advertising exclusively within the UAE isn’t subject to this particular requirement, though general consent and tracking practices are still worth reviewing under UAE PDPL considerations separately.

Check your consent banner’s interaction with GTM’s preview mode as described above, or check your CMP’s admin dashboard directly for confirmation it’s sending all four current consent parameters.

The requirement itself is specific to EEA traffic. Correctly implementing it shouldn’t change measurement or targeting for traffic outside that region.

Need Your Tracking Setup Actually Verified?

If you’re not confident your consent implementation is correctly configured for EEA-facing campaigns, a free audit will check it against the current requirement.

Book your free consultation at as86.pro — bilingual service in English and Arabic across all UAE markets.

Related reading: