Incorrect default signal (`ad_personalization`)

Description

Google Consent Mode is active, but the default signal sets an incorrect value for ad_personalization. This parameter controls data processing by Google services for ad personalization. If the value is anything other than "denied", Google may begin tracking before consent is obtained, which defeats the purpose of Consent Mode.

Possible causes

1. If your CMP is not integrated via Google Tag Manager:

   • A hardcoded gtag command like:

     gtag('consent', 'default', {
       ad_personalization: 'granted'
     });

     is present somewhere in your code or injected by another script.

2. If your CMP is integrated via Google Tag Manager:

   • The ad_personalization field in the Default Consent Mode Settings is not set to "denied" ;

   • Another tag in GTM may override the value with a different gtag call.

What to check

If you are not using Google Tag Manager:

• Search your codebase for any gtag('consent', 'default', {...}) command;

• Remove or modify any line that sets ad_personalization to "granted" or another incorrect value.

If you are using Google Tag Manager:

• Open your CMP tag (e.g., ABconsent – Sirdata CMP) ;

• In the "Default Consent Mode Settings" section, make sure Advertising is set this way: