Analytics HelperSirdata APISemantic APIA propos de Sirdata

Late `default` signal

Google Consent Mode is enabled, but the default consent signal is sent too late, meaning after some Google tags have already fired. In such cases, those tags may load before the consent state is known, reducing the effectiveness of Consent Mode.

Possible causes

  1. A Google script is loaded before th CMP

  2. The gtag script is loaded asynchronously or deferred, or delayed by an optimization system:

    • presence of async or defer attributes on the main <script> tag;

    • interference from caching/CDN systems like Rocket Loader (Cloudflare);

    • dynamic or conditional loading of the gtag script.

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

    • the trigger used is not the expected "Consent Initialization" (gtm.init);

    • another tag also uses that trigger, which can create a conflict and delay Consent Mode.

What to check ?

  • If NOT using Google Tag Manager: ensure the CMP script is loaded before any other script, placed in fiorst position in the <head> section of your page.

  • If NOT using Google Tag Manager: ensure the gtag script is loaded synchronously, before any other Google tags, without async or defer.

  • If using Google Tag Manager:

    • make sure that only your CMP tag uses the "Consent Initialization" trigger;

    • do not reuse this trigger in other tags.

PrécédentMissing `default` signalSuivantIncorrect `default` signal (`analytics_storage`)

Mis à jour

Ce contenu vous a-t-il été utile ?