Support » Plugin: GDPR Cookie Compliance » Why is the page reloaded on Accept and Save

  • Resolved ddenev

    (@ddenev)


    Hi,

    Is there a particular reason why the whole page is being reloaded by the plugin when the user accepts either via the bottom bar or via the Save in the popup?

    Wouldn’t it be more efficient to not reload the page and just set the Moove cookie? We can catch the setting of the cookie event via JS (or fire a GTM custom event in my case) and take it from there.

    Thanks.

    • This topic was modified 1 year, 10 months ago by .
Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi there,

    Thanks for your comments. Currently the plugin reload the page to include the scripts defined, and the because the cookies shouldn’t be cleared immediately with javascript (only we can set the expiration to a past date) this task require reload. Also we can inject the scripts when you accept the cookies, but we can’t remove the injected script only if we reload the page and re-inject the selected scripts by user.

    I hope this makes sense. We’re working on an improvement to prevent the reload, this will be included in a future release.

    Hi Gaspar,

    Thank you for the detailed reply!

    One of the reasons I am asking is based on the following example situation: imagine a user enters the site and starts filling a form. If he/she is halfway with the form and then accepts the cookies then the page will be reloaded, the user will have lost the already entered data and will be VERY frustrated => this will lead to the user just abandoning the site, hence a lost conversion – all just because he/she decided to accept the cookies after starting to fill the form.

    I know of another cookie consent solution (Civicuk Cookie Control) which does not reload the page and deletes the cookies just fine when the user withdraws consent.

    Some additional comments:

    Currently the plugin reload the page to include the scripts defined

    I am sure scripts can be inserted without page reload. Google Tag Manager does this all the time 🙂

    and the because the cookies shouldn’t be cleared immediately with javascript (only we can set the expiration to a past date) this task require reload

    Could you please elaborate a little bit more? Why shouldn’t the cookies be cleared with JS? Cookies are set with JS after all.

    Also we can inject the scripts when you accept the cookies, but we can’t remove the injected script only if we reload the page and re-inject the selected scripts by user.

    Also do not agree here. IMHO, you can perfectly remove the inserted scripts without page reload.

    In a summary, I don’t see any benefits in reloading the page, while there are certainly drawbacks (as described above).

    It is then good to hear that you are working on disabling the reload

    Best regards,
    Drago

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Why is the page reloaded on Accept and Save’ is closed to new replies.