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
A Google script is loaded before th CMP
The
gtag
script is loaded asynchronously or deferred, or delayed by an optimization system:presence of
async
ordefer
attributes on the main<script>
tag;interference from caching/CDN systems like Rocket Loader (Cloudflare);
dynamic or conditional loading of the
gtag
script.
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.
If you use gtag without a GTM:
You must condition the gtag script with "data-cmp-src":
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, withoutasync
ordefer
.

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.

If you are using a gtag without a Google Tag Manager:
You must condition the gtag script with "data-cmp-src":

Mis à jour
Ce contenu vous a-t-il été utile ?