Hello,
thanks for your message.
After having installed the GTM script through our plugin have you followed this guide to correctly setup your GTM container?
I followed step 1 and 2 of the guide. The triggers and tags will be setup by our ads team. We do not need to import a container preset. Anyhow our main problem is, that tag manager is loaded prior to consent and I cannot find any option to avoid this.
We have now found a workaround. We deactivated GTM+Analytics integration in the wizard and added the GTM code manually via a custom script in the script center which is categorized in statistics and only loaded with consent given.
Hi @baumannmusic ,
What you experienced, it is normal because our Cookie Solution does not delete cookies, but rather “blocks” the script that generates them at the source. This means that the cookies you see are present in the browser cache, but they no longer perform their profiling function because the script that uses them is blocked upon rejection. Also consider that if your ADS team applied the correct triggers in your GTM workspace, you should not worry about whether a connection is established before consent, as the Complianz cookie categories will act as the main trigger for those tags.
You can easily check this from the “Network” tab of your development tools: upon rejecting cookies, if you refresh the page, the script that generates the cookie in question is blocked and does not appear in the list of scripts loaded by the page.
But, if you prefer your workaround, please feel free to use it. Enhancing personal preferences is always a great thing!
I hope this clarifies your doubts.
Best regards,
Antonio
