Hi @jadorwin,
The page will only reload when a decision has been made, with a lower level of consent than the user set before, and only if a page load is needed.
For example, if someone goes from statistics to functional, while an event from Tag Manager has already been fired. Reloading the page won’t ‘unfire’ the previous event. It will stop firing that event happening again, so a reload won’t be needed.
There are other examples, when it is needed. But configurations, and thus behavior might change per website, and per user.
If you want, you can share your URL, and I can check if everything works as it should. regards Aert
Hi @jadorwin, I just tested this, when I first accept marketing cookies, then revoke with the button generated by the shortcode [cmplz-revoke-link], the page reloads as expected. If this is not the case on your site, can you check if you have any jquery errors in your developer console?
Hi @jadorwin,
Do you have any further questions? Is there any particular reason that you need the page to reload?
Just let us know if you need further assistance.
Kind regards,
Leon
Hi,
With the previous version, I managed the consent in the privacy policy directly in javascript. The automatic reloading of the page after clicking on the button allowed me to modify the content of the page according to whether or not the visitor had consented to marketing cookies.
I will find another way to do that. Thanks for your quick responses.
Br,
