Home › Guides › Consent Mode v2

Consent Mode v2: what UAE advertisers actually need

By Abhishek Thakral · abhi.performs, Dubai · Updated October 2026 · 9 min read

Most Consent Mode v2 guides are written by cookie banner companies for European websites. A Dubai business owner reads them and asks: do I need this if my customers are here? Google's EU user consent policy answers half of it, because it only sets duties for end users in "the European Economic Area, the UK and Switzerland".

The other half depends on your traffic. An off-plan launch advertised in London, or a clinic with enquiries from Europe, has visitors the policy covers.

What Consent Mode v2 does

Consent Mode passes each visitor's cookie choice from your consent banner to Google's tags, which then change what they store and send. It is not the banner: "Consent mode doesn't provide a consent banner or widget" (About consent mode, Google Ads Help). You still need a banner or a consent management platform (CMP). Consent Mode is the wiring between that banner and the Google tag, Google Ads, GA4, Floodlight and the Conversion Linker.

The "v2" dates from November 2023, when Google added two parameters and asked existing users to upgrade (Set up consent mode on websites, Google for Developers). There are now four core signals:

• ad_storage. Advertising cookies, such as the ones Google Ads uses for conversion tracking.
• analytics_storage. Analytics cookies, for example GA4's visit duration.
• ad_user_data. New in v2. Consent to send user data to Google for advertising.
• ad_personalization. New in v2. Consent for personalised advertising, including remarketing.

Does a UAE business need Consent Mode v2?

A UAE business needs Consent Mode v2 for its visitors from the EEA, the UK and Switzerland, because Google's policy applies to those users on any site you control that uses Google's products. For them you must get legally valid consent for cookies where the law requires it and for personalised ads, keep consent records and explain how to withdraw. Google says it may limit or suspend your use of its products if you do not (Google).

The policy speaks of end users in those countries, so my reading is that location counts, not nationality: a British expat browsing from Dubai is a different case from a buyer browsing from Manchester. That gives three cases:

1. Almost no European visitors. Check GA4's country report. If the EEA, UK and Switzerland are a rounding error, Google's policy has little to apply to.
2. A steady share from Europe. Typical for off-plan property, medical tourism and e-commerce that ships abroad. Set up Consent Mode v2 for those regions, with a banner that shows there.
3. You advertise in Europe. If campaigns target the UK or EEA, for example real estate lead generation aimed at overseas buyers, treat it as required.

UAE visitors are a separate question. The UAE's Personal Data Protection Law (Federal Decree Law No. 45 of 2021) applies to processing "inside or outside the country" and prohibits processing personal data without consent, with some exceptions (Data protection laws, UAE Government portal). The DIFC has its own Data Protection Law. Whether that means a banner for UAE visitors is a question for your legal adviser, not your media buyer.

What each signal switches off in Google Ads

Each Consent Mode v2 signal turns off a specific part of Google Ads measurement or targeting when it is denied, according to Google's consent mode reference.

Google says ad_user_data is "required for measurement use cases, such as enhanced conversions and tag-based conversion tracking", and both new signals must be granted for personalised advertising. A setup still on the old version, where neither is set, gets the same not-granted behaviour.

Basic or advanced consent mode

Basic consent mode blocks Google tags until the visitor answers the banner, while advanced consent mode loads them straight away and sends cookieless pings when consent is denied (Google).

• Basic. A visitor who declines sends "no data" to Google, "not even the consent status". Google Ads conversion modelling then uses a general model.
• Advanced. Pings carry a timestamp, the browser type (user agent), the referrer and whether the page had an ad click ID. Google uses them for an advertiser-specific model, which it describes as more detailed.

That modelling only starts at scale. The threshold for Google Ads conversion modelling is 700 ad clicks over 7 days for a domain x country grouping (Verify consent mode implementation, Google Ads Help). GA4's behavioural modelling has its own minimums: at least 1,000 events a day from visitors who declined analytics cookies for 7 days, and 1,000 daily users who accepted them.

My rule for UAE lead-gen accounts: if clicks from any one European country are far below 700 a week, the modelling case for advanced does not apply yet, so basic is the simpler, more conservative choice. Above that line, discuss advanced with whoever signs off your privacy policy, because it sends pings before consent.

Set the defaults by region

Google calls it "best practice" to scope default consent settings to "the regions where you are surfacing consent banners", which keeps measurement where banners are required and avoids losing it where they do not apply (Google for Developers).

1. Install the banner. Use a CMP that supports consent mode, or a consent mode template from the Tag Manager Community Template Gallery.
2. Deny by default in the EEA, UK and Switzerland. The consent default command takes a region list in ISO 3166-2 codes, such as GB and CH plus each EEA country.
3. Set a separate default for everyone else. A default with no region covers all other visitors. What it should be for UAE visitors is the PDPL question, decided with your adviser.
4. Give a slow banner time. wait_for_update holds tags briefly (Google's example is 500 milliseconds) so an asynchronous CMP can send its update first.
5. Consider URL passthrough. It carries the gclid and related parameters in links when cookies are denied. Check that redirects, such as to a thank-you page, keep them.

How to check it works

Google recommends Tag Assistant for checking a Consent Mode v2 setup on a website, with the Diagnostics tab in Google Ads as a second check (Google Ads Help).

• Tag Assistant. Start a session on your site and accept the banner. The earliest Consent event should show all four signals with an On-page Default of Denied, the latest an On-page Update of Granted. The Tags tab shows which tags fired or were blocked. If defaults are set by region, test from a European location too.
• Google Ads Diagnostics. Go to Goals, Conversions, Summary, open a website conversion action and choose Diagnostics. "Consent mode is implemented" means it works but you are below the modelling threshold. "Consent mode is implemented and modeling is active" means modelling is running.
• Give it time. Google says the status can take 48 hours to appear, and up to 2 weeks in some cases.

Mistakes that cost UAE advertisers data

• Granted by default in Europe. Setting EEA or UK defaults to granted to keep numbers up breaks the policy you are trying to meet.
• Consent lost on the next page. Google says updates must be tracked on the page where they happen, before any page transition. A banner that redirects on click can lose the choice.
• Treating it as compliance. Consent Mode carries a choice; it does not collect one or write your privacy policy. Data you upload needs consent too, see the Google Ads Data Manager guide.

Moving tags to your own domain as well? Read the Google tag gateway guide first, and test consent behaviour again after switching.

What to do now

1. Check in GA4 what share of your traffic comes from the EEA, the UK and Switzerland.
2. Agree with your legal adviser what the banner does for European and for UAE visitors.
3. Set all four v2 signals, denied defaults for the European regions and a separate default for everyone else.
4. Pick basic or advanced with the 700-click test.
5. Verify in Tag Assistant, then check Diagnostics in Google Ads after a week.

If your conversion tracking itself is shaky, consent is the second fix, not the first. My Google Ads management starts with both.

Frequently asked questions

Related