• Resolved maxidavis

    (@maxidavis)


    Hi there,

    I have a few comprehension questions:

    • I have followed your instructions and implemented the Custom Consent Mode Script as well as Google Tag Manager. I also have the wordpress plugin active, so I did not integrate the code.

    However, I have now noticed that everything only works if I deactivate the WP plugin. Is it correct that the connection between your service and my site is already established by the Google Tag Manager, so I don’t need the plugin nor the code?

    • Then I have a question about the different statuses:
      do they have to be identical in the Tag Manager, as well as in the custom code? Or does the Tag Manager overwrite the custom code?
      Why do I need the custom code at all if I have the Tag Manager active?
    • If I activate “Allow Google tags to fire before consent” under the “Advanced Settings”. How does this affect the status? Does it override the tag manager?

    Thanks in advance 🙂

    Max

    P.s.: I also think your documentations are very confusing. You are always saying that there is option 1 OR option 2. But in both options you always need the custom code AND the tag manager? So why two options?

    You also say, that I don’t have to add the cookieyes code if I have the WP Plugin active, but in my case it only works without code AND without Plugin.

    I hope you can bring some clarity to the matter.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    Greetings from CookieYes!

    Please make sure that you have followed this documentation, which is exclusively for the plugin users to integrate Google consent mode. Also, please share your site URL so that we can check for any issues in the implementation on your site and provide you with a working solution.

    Thread Starter maxidavis

    (@maxidavis)

    Hi @cookieyesteam,

    yes, I followed your documentation and everything works fine now. But I had to configure it in a different way.

    Can you please answer to my questions:

    • The custom code is for the default status, correct? The GTM then loads the “Onpage load” status, right?
    • They don’t need to be the same I guess. But what do I need to set up, for the “advanced consent”?
    • When I activate the “Allow Google tags to fire before consent” under the “Advanced Settings”. How does this affect the status? Does it override the tag manager?
    • With the GTM setup in your documentation, can a user only decline “analytics” for example? Or do you have another documentation for this? Right now, it’s accept all or decline all.

    Thanks, Max

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    The custom code is used to set the default consent status until the cookie banner loads on your site. Consent will get updated to the default setting in your banner once the banner loads on your site.
    When you enable the option, “Allow Google tags to fire before consent” GTM and the related scripts will get unblocked on your site. Tags will get fired by default but the cookies will get set only after the user’s consent.

    Thread Starter maxidavis

    (@maxidavis)

    Hi @cookieyesteam,

    okay, thanks for the answer.

    • So the “Allow Google tags to fire before consent” doesn’t set anything to “granted”?
    • With the GTM setup in your documentation, can a user only decline “analytics” for example? Or do you have another documentation for this? Right now, it’s accept all or decline all.

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    Enabling the “Allow Google tags to fire before consent” option won’t set the consent to “granted” but only unblocks GTM and the related scripts from your site.

    You can set the consent types to either “denied” or “granted” as per your requirement. While setting it to “granted” consider seeking legal advice to ensure you’re meeting your obligations under GDPR and other relevant regulations.

    Thread Starter maxidavis

    (@maxidavis)

    Hi @cookieyesteam,

    okay, do you have a documentation for this? Right now, it only accepts all or declines everthying.

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    “Right now, it only accepts all or declines everthying.” Could you please provide additional details or clarify your query?

    Enabling the Support GCM option will only allow a basic implementation, that is, to fire the allowed/preferred tags based on user consent. If the user rejects the banner, some data is to be collected as per the advanced consent mode implementation, for this, “Allow Google Tags to fire before Consent” should be enabled.

    Hence, enabling both ‘Support GCM’ and ‘Allow Google Tags To Fire Before Consent’, will ensure that Google tags fire even if the user rejects the banner. However, this is associated with cookieless pings, and only collects the information required for behavioural and conversion modeling to fill the gaps in your data. For your information, even with the option “Allow Google tags to fire before consent” enabled, Google Analytics (GA) may not be able to track real-time data.

    It’s important to note that while Google may collect some data even if consent is rejected, this data won’t be included in analytics reports and is primarily used for behaviour modelling as said earlier. GA will only activate tracking when users explicitly accept the cookies associated with the Analytics service.

    Kindly refer to this documentation for more insights.

    Thread Starter maxidavis

    (@maxidavis)

    Hi @cookieyesteam,

    in the meantime I was able to figure it out. You need to activate the additonal setups in the Google Tag Manger Settings. With this, I was able to configure the behavior of each individuell consent and at what conditions a specific tag can be fired.

    In this google documentation you can find more insights: https://support.google.com/tagmanager/answer/10718549?hl=de

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    Thank you for sharing your insights.

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @maxidavis,

    This thread has been inactive for a bit, so we are going to mark it as resolved now. Please feel free to open a new thread or follow-up if you have any further questions or still need help.

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

The topic ‘Conset Mode v2 Implementation & Status’ is closed to new replies.