LogoLogo
Analytics HelperSirdata APISemantic APIA propos de Sirdata
English
English
  • Sirdata CMP
  • INSTALL
    • Web & Mobile web
    • AMP
    • Via a Tag Manager
      • Loading via Google Tag Manager
    • In a CMS
      • Loading in Shopify
      • Loading in Wordpress
      • Loading in Prestashop
      • Loading in Magento
      • Loading in Drupal
    • Cache Systems Exclusion
      • Autoptimize WordPress Plugin
      • Cloudflare WordPress Plugin
      • LiteSpeed WordPress Plugin
      • NitroPack WordPress Plugin
      • SG Optimizer WordPress Plugin
      • WP Super Cache WordPress Plugin
      • W3 Total Cache WordPress Plugin
      • WP Meteor Plugin for Wordpress
      • WP Rocket WordPress Plugin
  • CONSENT TRANSMISSION STANDARDS
    • Introduction
    • Google Consent Mode
      • Mandatory Prerequisite
      • Activation of Advanced Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation of Basic Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation via Sirdata CMP
      • Activation via Google Tag Manager
    • Microsoft UET Consent Mode
    • Microsoft Clarity Consent
  • CMP API
    • How it works
    • Examples
    • Working with iframes
  • Advanced features
    • Passive mode
    • Set language per user
    • Manually display the CMP
  • Script management
    • Remote Tags Management without a Tag Manager
    • Remote Tags Management with a Tag Manager
    • Tag Management with Google Tag Manager
    • Local script Management
    • Advanced configuration
    • Examples
    • Share the TC String
    • Tag Management setup service
  • Analytics
    • Google Analytics
  • F.A.Q.
    • Integration
      • Is Abconsent compatible with Stape?
      • Is ABConsent compatible with Addingwell?
    • Google Consent Mode V2
      • Google Consent Mode V2 utility
      • News Google Consent Mode V2
      • Advanced mode or basic mode
    • Packaging
      • Cookies management
      • Tags packaging
    • Cookie settings
    • Button operation
    • Button color
    • A/B test
    • Mobile, tablets ...
    • Multi-sites
    • Mobile display
    • Private browsing
    • AMP consent
    • AMP consent button
    • Tags conditionning
    • Google Ads
    • Error 6.1 Google
    • Google PageSpeed
    • Refusal & Targeted ads
    • Mozilla and adblocks
    • Wordpress, Joomla, etc ...
    • Shopify
    • Pricing
      • The Two Types of Licenses
      • What happens when I reach the limit of my monthly plan?
      • Do you offer a trial period?
      • What are the accepted payment methods?
      • Do you offer packages for very high volumes of hits?
      • Are unused hits carried over to the next month?
      • What is considered a Hit?
      • Can I change plans?
    • Content Security Policy (CSP)
    • Google
      • Problem gclid google
      • Google extensions
    • How to Verify the Integration of My CMP?
    • How to Identify the Cookies Present on Your Website?
    • Abconsent CMP is compatible with Taggr ?
  • CMP Services
    • CMP Configuration
    • CMP Integration
    • Tag Conditioning
    • Compliance audit
    • Extra-vendorlist
    • Video-Wall
    • Inventory Partners
    • Consulting
  • Links
    • Configure your CMP
    • Sirdata API
    • Semantic API
    • About Sirdata
    • Analytics Helper
Propulsé par GitBook
Sur cette page
  • Method
  • Specific case for Google Tag Manager

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

  1. Script management

Remote Tags Management with a Tag Manager

PrécédentRemote Tags Management without a Tag ManagerSuivantTag Management with Google Tag Manager

Dernière mise à jour il y a 5 mois

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

The Tag Management method described in the previous page can be used via a Tag Manager and the method remains the same except that it is necessary to manually trigger the processing of the stack via the following dedicated function.

<script>try{Sddan.cmp.triggerTM();}catch(e){}</script>

As this functionality is integrated within the CMP, it will only work if the CMP is loaded on the page.

This method allows a great technical simplification of the tag management. However, it is important to keep in mind that legal expertise is necessary to figure out how to apply it by yourself.

For each tag/beacon, you must:

  • Evaluate the possible presence of non-exempted trackers (cookies, indexdb, local storage, etc.) (ePrivacy Directive)

  • Evaluate the processing of personal data and, if applicable, the purposes pursued by your partners and their respective legal bases (GDPR)

  • Evaluate if a tag/beacon is automatically supported by your partners thanks to the CMP APIs (e.g.: Google and Microsoft Bing's "Consent Mode")

Don't hesitate to ask our team to set up these packaging for you:

Method

Proceed as described on the previous page but add the above function:

  • Either for each tag you want to condition

  • Either once as the last script loaded by the Tag Manager

<script src="https://www.example.com/script.js"></script>

becomes in the Tag Manager:

<script data-cmp-src="https://www.example.com/script.js"></script>
<script>try{Sddan.cmp.triggerTM();}catch(e){}</script>

If the tag is inserted in JavaScript :

<script>
(function() {
    var s = document.createElement('script');
    s.type = 'text/javascript';
    s.async = true;
    s.src = 'https://www.example.com';
    var _head = document.head || document.getElementsByTagName("head")[0];
    _head.appendChild(s);
})();
</script>

becomes in the Tag Manager:

<script>
(function() {
    var s = document.createElement('script');
    s.type = 'text/javascript';
    s.async = true;
    s.setAttribute('data-cmp-src','https://www.example.com');
    var _head = document.head || document.getElementsByTagName("head")[0];
    _head.appendChild(s);
})();
</script

All advanced features ar available for both tags inserted directly in the source code and via a Tag Manager.

Specific case for Google Tag Manager

It is possible to set each tag as explained above via the data-cmp-src attribute and to trigger the Sddan.cmp.triggerTM() function only once as the last script with a lower priority.

Careful : it is MANDATORY, for each tag, to check the "Support document.write" box.

<script data-cmp-src="https://www.example2.com/script.js"></script>
<script data-cmp-src="https://www.example3.com/script.js"></script>
<script data-cmp-src="https://www.exampleX.com/script.js"></script>
<script>try{Sddan.cmp.triggerTM();}catch(e){}</script>

This newly added last tag should bet set like that in GTM and triggered once per page:

https://cmp.docs.sirdata.net/v/en/script-management/tag-conditioning-service
-10 Tag firing priority