• Dear sirs

    First of all, thank you for a great plugin. Though there seems to be a problem with the Google Consent Mode V2, when scanning we get the error: Consent signals not updated after consent.

    Google Consent Mode v2 is activated in backend

    Have I overseen something here? We have deactivated cache plugin just to be sure 🙂

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • gnavernesunivers

    (@gnavernesunivers)

    Hi Thomas.

    Have you solved the challenge? And if you have, what was the error? Because I’m considering starting to use that plugin myself, but it should work.

    Thread Starter Thomas Reinholdt

    (@bananajones)

    Hi there

    sorry, still not solved and working and still waiting for a reply. 😊 Too bad, seemed like a nice plugin.

    Have you checked in console with dataLayer if consent update is actually updated after granting/denying?

    Scanners are not always reliable unfortunely.

    mrsnowh

    (@mrsnowh)

    Hello everyone!

    I’m having an issue with Consent Mode v2, and since I see there’s already a topic about it, I won’t create a new thread.

    I installed the plugin, enabled Google Consent Mode v2 (GCM) under the Consent Mode tab, and I’m using the Google Tag Manager implementation. I followed the steps described on that screen to set up everything in GTM:

    1. I selected the template.
    2. I added the new tag based on the instructions.
    3. I didn’t do any additional configuration; I left everything at the default settings.

    During testing, all cookies load even before the user gives consent.

    Can any of you help me figure out where the issue might be or what I’m doing wrong?

    Thank you!

    • This reply was modified 6 months ago by mrsnowh.

    Hey @mrsnowh

    As for Consent Mode v2, and your screenshot, I think your setup is correct (if this is before the user accepts the cookies).
    In the screenshot, I don’t see any GA or GTM cookies, so that means they haven’t fired yet.

    As for the other cookies you see in the screenshot, for example the ones with prefix ‘pys_’ I believe these come from your PixelYourSite plugin. And since PixelYourSite is not set up via GTM with the ‘Consent Initialisation’ trigger, then they obviously fire earlier even if the user hasn’t given consent yet.

    I believe you shoud be using the ‘Blocked Scripts’ tab for this, to block any additional scripts befor the consent is given.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.