Remote Tags Management without a Tag Manager

Sirdata CMP allows you to automatically manage your tags on the page upon loading. That is to say to the tags inserted "directly" in the page but not to the tags inserted by a third party tool such as a Tag Manager. To use this feature via a Tag Manager please refer to the next 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:

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

Before loading the partner scripts on your site, it is important to check that the user has given his consent or has not objected to the legitimate interest.

To do so, you can utilize the JavaScript commands available in the CMP API. With Sirdata CMP, you can also proceed to the conditioning of your tags, in a few minutes and a very simple way.

This functionality being integrated within the CMP, it cannot be applied to the tag of your CMP, which must always be deployed as provided in the installation procedure.

Consent needed for cookies

In order to link the loading of a script to the user's consent, you simply need to replace the src attribute with data-cmp-src in the HTML tag. Thus, after having collected the user choices, the CMP will automatically verify that he has given consent to purpose 1 (Store and/or access information on a device) and in which case will load the script on your site.

Most tags involve a prior consent for cookies. This simple change then allows you to meet regulatory requirements, while controlling the scripts that can load on your site.

Example for a remote script

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

becomes:

<script data-cmp-src="https://www.example.com/script.js" type="text/javascript"></script>

In this example the tag is manually integrated. You can see it because there's a space before src. If you see a dot (".") before src, it means the script is inserted by a JavaScript function. In that case, please use the setAttribute option as explained below.

<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:

<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>

This feature will work only if the tag is inserted directly in the HTML source code of your page and should not be used for tags inserted via a Tag Manager. To use this feature with a Tag Manager, please refer to the next page.

Supported tags

In the table below you will find the list of HTML elements to which the tag conditioning can apply:

Tag	Exemple
<script>	<script data-cmp-src="/script.js" data-cmp-vendor="53" data-cmp-purposes="1,3"></script>
<img>	<img data-cmp-src="/image.png" data-cmp-vendor="22" data-cmp-purposes-li="2" width="1" height="1"/>
<iframe>	<iframe data-cmp-src="/iframe.html" data-cmp-provider="89" width="250" height="200"></iframe>
<embed>	<embed data-cmp-src="/embed.html" data-cmp-vendor="178" width="250" height="200">
<video>	<video data-cmp-src="/video.mp4" controls width="320" height="240"/>
<audio>	<audio data-cmp-src="/audio.ogg" controls/>
<source>	<audio controls><source data-cmp-src="audio-consent.ogg" type="audio/ogg"><source data-cmp-src="audio-li.ogg" type="audio/ogg"></audio>
<track>	<video width="320" height="240" controls><source data-cmp-src="video.mp4" type="video/mp4"><track data-cmp-src="subtitles.vtt"></video>