Change to the cookiebot script on Nov 22?
Hi,
It seems that since november 22nd the behaviour of the cookiebot script has changed. Instead of the dataLayer event: cookie_consent_statistics only firing when the actual cookiewall interaction took place, it now fires on each and every page refresh.
Is this correct?
This caused double pageviews on our end...
Is there a changelog for the changes made to the cookiebot script and the effects this has? Then we can subscribe to that changelog and make sure all our implementations still function as expected.
-
Hi Peter,
For your issue we can suggest you adding an extra condition on the trigger to exclude refreshes:
If a tag is configured to trigger off pageview AND cookie_consent_statistics, then the tag will fire on every page load if consent has been submitted (including refresh).
We can add a condition though to detect if there indeed has been a navigation, or a refresh:
Add a custom variable (name it pageReloaded) with this value:
function() { return performance.navigation.type != 1; } (this should return false if the page isn't refreshed)Add a new "and" condition to the trigger: pageReloaded - equals - false
Regarding the changelog – Currently we do record a configuration change log but that it is not yet exposed in the user interface so there is no a public changelog on which you can subscribe.
Regards,
Elina
Please sign in to leave a comment.
Comments
1 comment