Goedemiddag Leon, In een eerdere video heb je het gehad over dat je Google Analytics zó hebt ingesteld dat je binnen Nederland tracking standaard mag inschakelen. Dit vind ik interessant, want ik heb hier eerder ook handleidingen voor gevolgd, maar ik twijfel er dan altijd nog aan of die handleidingen up-to-date zijn. Is er een bepaalde handleiding die jij volgt die 100% up-to-date is?
Hey there! Here are the guidelines that I'm currently following, but they are very broad and open for interpretation: www.acm.nl/nl/verkoop-aan-consumenten/reclame-en-verleiden/online-beinvloeden/cookies-plaatsen There used to be a PDF guide specifically for Google Analytics at www.autoriteitpersoonsgegevens.nl/ but that guide was more aimed at Universal Analytics. Also they announced that they were reconsidering there advice, but up until today we haven't back heard from them. They even took the PDF guide down a while back.
I have a script in the page that has nothing to do with google tag manager and causes the read consent error. Its a script about conversion from ads (conversion.js). How can i solve this?
Can I have your email? I have found the problem and I need to send you an email to confirm. Basically gtm tags runs asychronously and that means that other scripts that read consent values can run before even consent initialization!
That issue is pain in the hole. Can’t get rid of this on most of sites. Sometimes after refreshing cookies it occurs and sometimes not. I feel like GTM runs random state generator for it. 😅
Exactly ;) Right after publishing this video I saw this video from Simo Ahava confirming that the warning may be caused by the Consent Mode / Cookiebanner tag itself, just like I suspected in the video. In that case the warning can be ignored: www.linkedin.com/posts/simmeroy_gtm-consentstate-consentmode-ugcPost-7186660973615661057-Md07
