Google says your consent signals are missing: how to fix it in 2026

If Google Analytics or Google Ads tells you that consent signals are missing, your site is not passing the visitor's consent choice to Google in the form Google expects. Google looks for two Consent Mode v2 parameters in particular: ad_user_data for ads measurement and ad_personalization for ads personalisation.

The warning matters most for visitors from the European Economic Area: since March 2024, Google has needed these signals to use EEA visitors in measurement and audiences for linked ad products. For Gulf traffic it is not a Google requirement, but the same missing signal means Google cannot tell a visitor who refused from one who was never asked.

Where to see the status

In Google Analytics, open Admin, then under Data collection and modification click Consent settings. The page shows advertising-related consent signals and behaviour analytics consent signals, and which of them Google is receiving.

After you fix the cause, Google says the notifications can take 48 to 72 hours to update. Check the page again after that, not the same day.

The four usual causes

Almost every case is one of these. Check them in order: the first one you find is usually the whole problem.

• No consent banner sends Consent Mode at all. Tags load with no consent state, so Google has nothing to read.
• The banner sends version 1 only. It sets ad_storage and analytics_storage but not ad_user_data and ad_personalization, the two Google checks for ads.
• The default is set too late. Google's own debugging guide flags the case where an ad tag has already read or written a cookie before the default consent is set. The default must come before any Google tag.
• The default is set asynchronously. Google's guide says not to set default consent states asynchronously; a banner script that loads later and then sets the default arrives after the tags.

Check your site in ten minutes

Google's Tag Assistant shows exactly what your page sends.

• Open tagassistant.google.com and enter your website address.
• On your site, interact with the consent banner and accept everything.
• In Tag Assistant, select the earliest Consent event in the summary and look at the API call: you should see ad_storage, ad_user_data, ad_personalization and analytics_storage.
• Open the Consent tab. The On-page Default column shows the state before the visitor chose; the On-page Update column shows the state after. Both should list all four parameters.
• Repeat once with Reject all, and check that the update shows denied.

Or let a real browser do it for you: free website scan shows whether your site sends a Consent Mode v2 signal and which trackers load before consent.

How to fix each cause

• No Consent Mode: add a consent banner that sets the default before Google tags and sends an update when the visitor chooses.
• Version 1 only: update the banner or its Google Tag Manager template so it sends ad_user_data and ad_personalization as well.
• Default too late: move the banner's default call above the Google tag or Tag Manager snippet, or use the Consent Initialization trigger in Tag Manager.
• Asynchronous default: load the code that sets the default synchronously, at the top of the page head.

How common this is in Saudi Arabia and the UAE

In our September 2026 scan of 1,556 Saudi online stores, 751 (48%) ran Google Analytics or Google Tag Manager without a Consent Mode v2 signal. In our October 2026 scan of 547 UAE business websites, 223 (41%) did the same.

The full comparison: Google Consent Mode v2 in Saudi Arabia and the UAE.

If you use Arqam360

The Arqam360 banner sets a Consent Mode default covering all four parameters as soon as its script runs, then sends an update with the visitor's choice, in Arabic and English. If the warning persists on a site that runs it, check that the banner script sits above the Google tag in the page head.

How the four signals work: Google Consent Mode v2 guide.

Sources