Activation of Sirdata Analytics Helper
Dernière mise à jour
Cet article vous a-t-il été utile ?
English
Dernière mise à jour
Cet article vous a-t-il été utile ?
If you haven't already done so, just go to to create your account.
Once the account is created, you will be able to declare your website(s) and corresponding tags, i.e. the Google Analytics property identifiers you have written aside in the first step of this guide, in the form UA-XXXXXX-Y or G-XXXXXX.
You can declare multiple property identifiers for the same site, separated by a comma. For example, you can enter "UA-1111111-1,G-99999999" to get the properties UA-1111111-1 and G-99999999 supported.
Undeclared properties will be ignored by Sirdata Analytics Helper : as a result, Google Analytics cookies may be dropped without consent, and data transfers deemed illegal could be operated.
If you declare no property identifier, Sirdata Analytics Helper will seek to automatically support all Universal Analytics and GA4 properties loaded on the page via analytics.js (for Universal Analytics 360) and the Global Site Tag (gtag.js).
If you declare at least one GA4 property identifier or if you don't declare any property identifier, Sirdata Analytics Helper will attempt to automatically activate Google Consent Mode to block Google Analytics cookies in the absence of consent.
Otherwise, IF YOU DO NOT FIRE GOOGLE ANALYTICS FROM GOOGLE TAG MANAGER, copy the automatically generated script into your console and paste it as is on your site to activate the service. The script looks like that :
If you are using GTM and a non-standard dataLayer name ("dataLayer"), you can declare it using the "dl" parameter. For example if your dataLayer name is "customDataLayer", you can add "&dl=customDataLayer" to the helper script:
Put this script in the first position on the page, before the CMP script if necessary, or just after, but always BEFORE the Google Analytics or Tag Manager scripts.
Under no circumstances should this Sirdata Analytics Helper script be managed via a Tag Manager. Please refer to appropriate section and tags if you need to do so, or get in touch with Sirdata to consider this type of integration.
It’s very important not to change this script, except to remove the property identifier (tid parameter). In particular, its synchronous operation must be kept.
For example, the “defer” or “async” attributes should not be added.
Our infrastructure is based on a reliable and efficient CDN, so you don't need to cache this script. If you do so anyway, a refresh every 12 hours is recommended.
For Universal Analytics 360 via analytics.js, the integration ends here.
For Universal Analytics 360 via Global Site Tag, the integration ends here.
For GA4 via Global Site Tag, the integration ends here.
For Universal Analytics via GTM and/or GA4 via GTM the integration does not stop there : you have to modify the settings of your tags in GTM as indicated in appropriate section.
If you are loading Google Analytics ONLY from Google Tag Manager tags, AND if you do NOT want to activate the cookieless functionality of the Helper (tracking without consent), you can skip the rest of this page and proceed directly to the .
If you are loading Google Analytics ONLY from Google Tag Manager tags, AND want to enable the cookieless functionality of the Helper AND load the Sirdata Analytics Helper script via GTM rather than inserting it into your source code, you can skip the rest of this page and proceed directly to .
