Analytics HelperSirdata APISemantic APIA propos de Sirdata

Missing `default` signal

Description

Google Consent Mode is enabled, but the default signal is missing. This means that no default consent settings are being sent to Google before user interaction. As a result, Google tags have no instructions on how to behave, which prevents Consent Mode from working as intended.

Possible causes

  1. The gtag script (or Consent Mode stub) is:

    • missing from the page;

    • improperly integrated (e.g., loaded with async or defer, or delayed);

    • blocked or altered by optimization tools (e.g., Rocket Loader, CDN caching, etc.).

  2. If Consent Mode is initialized via Google Tag Manager:

    • the “Activate Google Consent Mode” checkbox is not selected in the CMP tag;

    • the “Default Consent Mode Settings” section is empty.

What to check

If you are not using Google Tag Manager:

  • Ensure the gtag (stub) script is placed at the very top of the <head>;

  • Remove any async or defer attributes from the script;

  • Make sure it is not delayed or modified by third-party systems like CDNs or optimization tools.

If you are using Google Tag Manager:

In your Google Tag Manager account, first ensure that your template is up to date. Update it if necessary.

Then:

  • In the “Tags” section, edit the ABconsent (Sirdata CMP) tag

  • Check the box labeled “Activate Google Consent Mode”

  • Add a line of default consent signals (e.g., "denied")

PrécédentInactive Google Consent ModeSuivantLate `default` signal

Dernière mise à jour

Cet article vous a-t-il été utile ?