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
  • 1) Triggers creation
  • 2) Tag management
  • 3) Creating granular parameters
  • 4) Using granular settings for events
  • 5) Using granular settings for tags

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

  1. Script management

Tag Management with Google Tag Manager

PrécédentRemote Tags Management with a Tag ManagerSuivantLocal script Management

Dernière mise à jour il y a 5 mois

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

Sirdata's intelligent CMP is developped to detect the existence of a dataLayer dedicated to Google Tag Manager (GTM) or to create one to inject into GTM the signals of choice (non-choice / consent / refusal / opposition of the user ).

You do not need to modify anything on your site, the CMP is autonomous.

The CMP injects a "consent" signal ("sirdataConsent") on page load if the user accepted cookies (or resides outside Europe), and/or "non-consent" ("sirdataNoConsent") if the user has refused cookies. If the user has not yet made a choice yet, an intermediary event "SirdataNoChoice" is triggered.

Be careful to handle the events well if you want to set up complex packaging: depending on the choice and any modification of the choice on the same page, there can be 2 events related to choice: sirdataConsent and sirdataNoConsent.

The CMP will also inject into GTM all the environment and choice information to enable the granularity of the legal bases to be implemented by purpose.

The basic strategy for quickly blocking tags (beacons) using cookies therefore consists of making the tags conditional on consent ("event"), while the advanced strategy consists of using the information transmitted ("variables") to verify the validity of the consent for a particular partner for example.

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:

1) Triggers creation

In your GTM account, go to the "Triggers" section of your workspace:

Click on "New", then set up a first custom event "Sirdata Consent" by selecting a trigger type "custom event" and using the event name "sirdataConsent" (without initial capital or space), as follows:

Save and repeat the operation to set up a second custom event named "Sirdata No Consent", selecting a trigger type "custom event" and using the event name "sirdataNoConsent" (without initial capitals or spaces), as follows :

You now have 2 events at your disposal, which will allow the CMP to automatically manage your tags.

2) Tag management

Now go to the "Tags" section where you manage your tags:

Edit an existing tag or create a new one, using the tag of your choice and using the second section ("Trigger") to trigger the tag only in case of consent (cf. event "Sirdata Consent "created in step 1) or on the contrary in case of non-consent if for example you want to trigger a tag without cookie in the absence of consent.

It is of course possible to use this trigger in addition to other triggers or conditions external to the CMP.

Your tag is now conditioned and will no longer be triggered without prior consent, for example. This is the major step, and we advise you to repeat this operation for all the tags that require it.

Then you can use the information sent by the CMP and create granular parameters to go further in the control.

3) Creating granular parameters

Parmètre

Valeur

sirdataGdprApplies

GDPR parameter of the TCF of IAB Europe: 1 if user subject to GDPR, 0 otherwise

sirdataProviders

Google AdTech Partner IDs with consent

Values framed and separated by pipes. Example:

|89|326|587|

Examples :

  • Facebook : 89

  • AT Internet : 587

  • Tradedoubler AB : 486

sirdataVendors

TCF GVL Vendor IDs with consent

Values framed and separated by pipes. Example:

|42|157|755|

Examples :

  • Amazon Advertising : 793

  • Awin : 907

  • BeOp : 666

  • Criteo : 91

  • Dailymotion : 573

  • Digiteka : 343

  • Effiliation / Effinity : 402

  • Google (Ad Manager, AdSense, Ads, Tag Manager, ...) : 755

  • Impactify : 606

  • Invibes : 436

  • Kwanko : 702

  • Microsoft : 1126

  • Opti Digital : 915

  • Outbrain : 164

  • Rakuten Marketing LLC : 60

  • Seedtag : 157

  • Taboola : 42

  • Teads : 132

sirdataVendorsLI

TCF Vendor IDs with legitimate interest established

Values framed and separated by pipes. Example:

|42|157|755|

sirdataExtraVendors

Sirdata Partner IDs with consent

Values framed and separated by pipes. Example:

|1|6|7|

sirdataExtraVendorsLI

Sirdata Partner IDs with legitimate interest established

Values framed and separated by pipes. Example:

|2|3|4|

sirdataExtraPurposes*

Sirdata's Purpose IDs* for which user gave consent to.

Values framed and separated by pipes. Example:

|1|2|3|4|5|6|

sirdataExtraPurposesLI*

Sirdata's Purpose IDs* for which legitimate has been established.

Values framed and separated by pipes. Example:

|2|3|4|5|6|7|8|9|10|

sirdataPurposes**

TCF's Purpose IDs** for which user gave consent to.

Values framed and separated by pipes. Example:

|1|2|3|4|

sirdataPurposesLI**

TCF's Purpose IDs** for which legitimate has been established.

Values framed and separated by pipes. Example:

|2|4|

sirdataSpecialFeatures

Special Features IDs for which user gave consent to.

Values framed and separated by pipes. Example:

|1|2|

sirdataPublisherPurposes

Standard Publisher Purpose IDs for which user gave consent to.

Values framed and separated by pipes. Example:

|1|2|3|4|5|6|7|8|9|10|

sirdataPublisherPurposesLI

Standard Publisher Purpose IDs for which legitimate interest has been established.

Values framed and separated by pipes. Example:

|2|3|4|5|6|7|8|9|10|

sirdataPublisherCustomPurposes

Custom (Non Standard) Publisher Standard Purpose IDs for which user gave consent to.

Values framed and separated by pipes. Example: |1|

sirdataPublisherCustomPurposesLI

Custom (Non Standard) Publisher Standard Purpose IDs for which legitimate interest has been established.

Values framed and separated by pipes. Example: |2|

sirdataTcString

TC String (IAB Europe' TCF)

*Purposes handled par Sirdata :

  1. Electronic communications (email, fax, SMS/MMS, or automated calls)

  2. Direct mail and telemarketing

  3. Personalized ads on TV (segmented TV)

  4. Personalized ads on radio (segmented radio)

**TCF's Purposes :

  1. Store and/or access information on a device

  2. Use limited data to select advertising

  3. Create profiles for personalised advertising

  4. Use profiles to select personalised advertising

  5. Create profiles to personalise content

  6. Use profiles to select personalised content

  7. Measure advertising performance

  8. Measure content performance

  9. Understand audiences through statistics or combinations of data from different sources

  10. Develop and improve services

  11. Use limited data to select content

To use them, go to the "Variables" section:

In the "User-defined variables" section click on "new" and choose the type of variable "Data layer variable":

Then use one of the parameters in the table above as variable name.

Save and go to the "event" or "tag" section to use these settings.

4) Using granular settings for events

You can create complex event triggers based on the sirdataConsent and sirdataNoConsent events sent to GTM, by coupling them with these variables created in the previous point.

For example, to condition a personalized advertising tag on the prior obtaining of consent for purposes 1, 3 and 4 and the partner Google (id 755), as well as a legitimate interest established for purpose 2 and this same partner :

Then use these triggers to trigger the specific tags for which they were created.

5) Using granular settings for tags

To transmit information in your tags, such as the TC String, for example, use the names of the variables you have created in your tags, surrounded by double brackets.

For example if you have created a sirdataTcString variable, you can use it in a tag by injecting it like this:

You can refer to the dedicated section on cookieless proxying to understand, if necessary, how trigger groups or trigger exceptions work.

Sirdata's intelligent CMP transmits the signals of choice to GTM in accordance with the :

https://cmp.docs.sirdata.net/v/en/script-management/tag-conditioning-service
IAB Europe's TCF
See the complete list of Google partners
See the full list of IAB partners
Example for the sirdataTcString parameter