Skip to main content
 

Google Tag Manager

Nicolas Gieß

Dear Community, 
I have a couple of questions I would like to adress: 

  1.  

I have implemented the cookie consent banner within GTM successfully as well as the cookie consent state. Do I understand the next step correctly, that I need to change the trigger for all my tags which I find in the scan report so that they fall under one of the three cookiebot triggers (preferences, statistics, marketing) → 

 

E.g. what used to be:

Facebook Page Load with Firing Trigger - “All Pages”

Now becomes:

Firing Trigger - “cookie_consent_marketing” AND “All Pages”

 

I would have to do this change for all cookies mentioned in the scan report? Can I keep the original firing trigger and just add the cookie-consent or will it have to replace it? I am thinking about cases such as a firing trigger “fire when 20 seconds on landing page” or “fire with scroll depth of xx px” which should stay even after the cookiebot implementation. 

2.

What do I have to do when a user has accepted only necessary cookies on the “open-for-the-public” website but then moves on into a platform which is only accessible via previous login. Can I track cookies and usage of the user within the platform, as that person has previously accepted the consent via our terms and conditions and is free not to use the platform when he/she does not want to be tracked?

3.

I have seen that subdomains can be grouped into a Domain Group which will carry over all settings from a user. In our case, the user is lands on example.com and then moves over to accounts.cloud.example.com for login/registration and then moves on to app.cloud.example.com. 

With the above question in mind: Could I group example.com & accounts.cloud.example.com in one Domain group so the user is not asked again but then not ask for consent again in app.cloud.example.com (which is only accessible after login) and track all cookies? If that is legally not allowed, the best way would be to combine all subdomains in a Domain Group?

 

4.

We currently have a special setting, that the GTM for the platform after being registered is a different GTM then on the public domain. If cookie consent is needed for the logged-in user as well, can the data be transferred from one GTM to another or is there no way around creating a single GTM for website & platform in order to track and treat all users according to their selection?

 

Thank you for your help,

 

Nicolas 

1

Comments

1 comment

Date Votes
  • Spas – vConnect – Community Supporter

    Hi Nicolas,

    Regarding your first question, firing trigger - “cookie_consent_marketing” and “All Pages” will probably work, but keep in mind that "All Pages" is redundant and can just be replaced by the Cookiebot event.
    For scroll depth, you would want to change "This trigger fires on" from "All Pages" to "Some Pages".
    If you have Cookiebot variable template, you could then add "Cookie consent contains Marketing" under "Fire this trigger when an Event occurs and all of these conditions are true"

    About the second and third questions, you could use domain group and then activate Bulk Consent in order to control multiple domains from one account. By enabling the Bulk Consent feature, your users will only be prompted for a consent the first time they visit any one of your websites.

    Regarding the fourth question, you would need to configure both GTM containers, and since those containers are separate and can't exchange data.

    Regards,
    Spas

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post