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:

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

Dernière mise à jour