Advanced configuration

If needed, you can proceed a more specific conditioning by filling the information you need the CMP to verify before triggering the loading of the script.

You will find the list of attributes that can be specified in the table below:

Attribute	Description
data-cmp-src (requis)	URL of the script to condition (ex : https://www.abc.com/script.js). You can also specify a JavaScript function to execute, that is previously defined on the page (ex : loadScript).
data-cmp-vendor	IAB partner ID to verify (ex : 53). When specified, a list of purposes and/or special features must be specified as well. Exemples : 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 Access the full list of IAB partners
data-cmp-provider	Google partner ID to verify Exemples : Facebook : 89 AT Internet : 587 Tradedoubler AB : 486 Access the full list of Google partners
data-cmp-extra-vendor	Sirdata partner ID to verify. When specified, a list of purposes must be specified as well.
data-cmp-extra-purposes*	List of Sirdata's Purposes IDs* for which the specified partner requires user consent (ex : 1,3,4). WARNING : data-cmp-extra-vendor must be specified as well.
data-cmp-extra-purposes-li*	List of Sirdata's Purposes IDs* for which the specified partner requires user consent (ex : 1,3,4). WARNING : data-cmp-extra-vendor must be specified as well.
data-cmp-purposes**	List of TCF's Purposes IDs** for which the specified partner requires user consent (ex : 1,3,4). WARNING : data-cmp-vendor must be specified as well.
data-cmp-purposes-li**	List of TCF's Purposes IDs** for which the specified partner relies on its legitimate interest (ex : 2,5). WARNING : data-cmp-vendor must be specified as well.
data-cmp-special-features	List of special features IDs for which the specified partner requires user consent (ex : 1). WARNING : data-cmp-vendor must be specified as well.
data-cmp-publisher-purposes	List of purposes IDs for which you require user consent.
data-cmp-publisher-purposes-li	List of purposes IDs for which you rely on your legitimate interest.
data-cmp-publisher-custom-purposes	List of custom purposes IDs for which you require user consent.
data-cmp-publisher-custom-purposes-li	List of custom purposes IDs for which you rely on your legitimate interest.
data-cmp-require-choice	Boolean (true or false) to indicate if the CMP should wait for the user to validate his choices before triggering the checking.
data-cmp-disable-check	Boolean (true ou false) to indicate if the CMP must deactivate the default check on the purpose 1. NOTE: This is only functional if no specific condition on a purpose or a partner is defined.
data-cmp-parent	If the conditioned script must be loaded at a specific location in the page, it is possible to indicate the ID of the parent HTML element that should contain it (only available for <script> tags).
data-cmp-fallback-src	Allows to specify an alternative script when the loading conditions ofdata-cmp-src are not fullfilled. This script can be conditioned with the same attributes listed above by prefixing them withdata-cmp-fallback- instead of data-cmp-.
${SDDAN_GDPR_APPLIES}	Macro to be used in the url called via the data-cmp-src attribute to add the GDPR parameter of the TCF of the IAB Europe
${SDDAN_GDPR_CONSENT}	Macro to be used in the url called via the data-cmp-src attribute to add the TC String of the TCF of the IAB Europe

*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

When a partner and purposes are specified, it removes the default check on the purpose 1. If you wish to keep the check on the purpose 1, please make sure to include it in the data-cmp-purposes attribute.

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:

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