Hi @arno-kools,
Those scripts are added with text/plain instead of a regular script (with text/javascript), thereby preventing these from being executed. Complianz converts these to text/javascript to load them after consent is obtained.
You can also control the location manually, i.e. by manually adding the script to the <head> of the page, and using the “Block a script, iFrame or plugin” field to block it before consent.
Or by directly including the consent parameters when adding the script to the header.
<!-- Consent Levels - Complianz -->
// Functional
<script type="text/javascript" data-category="functional"></script>
// Statistics
<script type="text/plain" data-category="statistics"></script>
// Marketing
<script type="text/plain" data-category="marketing"></script>Kind regards, Jarno
Thanks for the clarification and fast response, Jarno!
Your last solution is exactly what I was looking for.
Just a moment ago a client of me asked to me to insert a varierty of tracking codes which have to be loaden on specific type of pages.
This will not be any problem anymore with these parameters.
I’m glad this can be realised so easily.