This made me smile, thank you ☺️

Blocking triggers are the old method of applying consent to specific tags. With consent mode that is not neccessary anymore. The cookie_updated event from cookiebot you mentioned is a good suggestion. I prefer Intialisation - all pages because that is the recommended trigger for GA4 to load. cookie_updated is fine too, but takes a while to load. You might miss some of the pageviews when people leave early.

​@LeonKorteweg oh I see thanks for explaining. is this the advanced consent mode implementation? When you use ghostery or any other cookie plug in, does it show no cookies before the banner has been approved?

Hey! Please contact the platform support for this if you're in doubt. I'm not familiar with the tool so cannot help here..

Hey there! You can choose what version of the cookiebanner you want (so with or without sliders) in the Cookiebot login panel. But if you ask me I prefer the two-button banner over the sliders. People rarely give consent for just one category. It is either all in or all out. The reason I used the sliders in my demo is because I'm using the free version of cookiebot as example. I simply cannot use a diferent banner template without paying.

Good question

Yes! In my head I assumed this was clear from the video, but in retrospect I should have talked about that a bit more. So thanks for asking 😁 This is how you treat Meta Ads and any other marketing tags in GTM with consent mode: In the consent overview you should add 'ad_storage' to these tags to prevent them from firing without consent. Does this help?

I believe this is because the Simo tag tries to read if consent has already been set previously. There is no harm to this as far as I can see.

Hey Max, thanks 👊🏻 I think you'll need to update your Cookiebot template. There is a section in GTM called 'Templates', if this is the case you'll be able to update there. Please check your setup afterwards carefully though. Updates can contain breaking changes.

@@LeonKorteweg Thanks, found it. In regards to the template changes and effects: in the Cookiebot CMP the fields are already changed and working. Will test it though ;) thanks again!

You have to set a custom html and add an additional script to fire the tags instantly after consent is given to capture that first page view.

Hey Marie! Its going to be hard for me to answer this here, because, even though I've read your comment multiple times, some things you write are not entirely clear to me. But perhaps these tips can point you in the right direction? - Consent mode and conversions require different triggers. - So i recommend that you implement consent mode like in the video with the 'consent initialisation - all pages' trigger. - Your conversion tags can just have their regular triggers, for instance a thank you page trigger. - Same goes for all remarketing tags. I usually use the 'initialisation - all pages' on meta ads pixel, but 'all pages' will work fine here as well. - If things are not working, try to isolate the problem. Check if consent mode or your setup causes the issue. For instance. What happens if you pause all consent mode tags? Does it solve the issue? Then the problem is probably in your consent mode setup. Is your issue not solved? Then your regular tag implementation might be wrong. - Always check if there are outside factors preventing the tags from firing. It could well be that an ad blocker or some other chrome extension is messing with your setup. If I get stuck I sometimes just disable every extension to see if that solves anything. I hope this helps..

Yes! I left that out of the video to keep things easy, but it is a great suggestion by itself. I only don't think this will solve the issues Marie has.

@@LeonKortewegthankyou both for your answers. It is highly appreciated! Leon if I understand you correctly, the only thing I have to do is set up cookieyes. (My cookiebanner) enable consent mode in the settings and get the custom template and put the trigger on consent initialisation? This is what I have done already. I only added the additional consent to the meta tags. And I added a second trigger when consent was updated. The only thing I am worried about is that what if a visitor does not give any consent since the banner is at the right bottom corner?! All the other tags have no consent triggers added or additional consent added since its already build-in. Am I missing anything else? 😃

Hey! Ah you're using a different cookiebanner. I've come across cookieyes a couple of weeks ago. I've found it not easy to get it working to be honest, but I have some extra requirements that might not apply to a simpler set up. Here is a detailed guide from cookieyes that might suffice for simpler setups: www.cookieyes.com/documentation/implementing-google-consent-mode-using-cookieyes/ Here are some tips that got it working on my end: - Don't include the banner via WordPress plugin or code snippet. Include it via the GTM template. - Disable Google Consent Mode under advanced settings in the cookieyes dashboard - Use the Cookieyes GTM template on consent initialisation to set the default Consent Mode command. - I used the Consent Mode template by simo ahava to set the Update command, also on consent initialisation (see my new video here kzfaq.info/get/bejne/r8Caet2XvKrHYI0.html&ab_channel=LeonKorteweg)

Hey! That is really different between countries. I usually look for the privacy authority in a specific country and search their site if they write anything about analytics cookies. Here in the Netherlands we are still allowed to use analytics cookies as long as they have little consequences for a users privacy. But it will also depend on what tools you fire under analytics_storage. Some countries in Europe prohibit the use of Google Analytics, but you can still use other tools like Piwik Pro or Matomo without consent. Hope this helps!

I would always load GA4 on the Initialization tag to comply with Google docs. The Google tag will load in case consent is given, even after the tag has been fired. However, Meta Ads doesn't do that. Therefore cookie_consent_update is probably handy to make sure it will load immediately after consent has been granted. But please test it, because I havent used that in a while ;)

I think that is not necessary. The conversions that you configure inside of GA4 work based on incoming events. So if you've set up consent correctly that will work fine. I don't know how this behaves on a hardcoded e-commerce setup or a scenario where you use a platform integration (i.e. WordPress plugin). It might work but to be honest I don't know. I always like to use GTM for more control.

Hmm strange. Do you have exactly the same template? Maybe you have a different variant of the template? I know that Cookiebot has a tendancy to leave things in place even though their outdated. For instance their login has an old and a new version. But let's wait a bit to see if anybody else has the same issue..

It depends really where your tracking setup is located.. I always lean heavily towards GTM, because all my tracking is set up there. But if your site is using plugin-based tracking (for instance via the Pixel Your Site plugin), you should probably use the WordPress plugin from cookiebot because that integrates better.

Hey! It turns out that I was wrong on this. Here is a full video with explanation: kzfaq.info/get/bejne/aLd5msmnl7vMopc.html

Good question, to be honest I'dd have to look this up myself. I'm considering a follow up video on consent mode where I go through some of the questions here. If I record that I will include your question and mention that here 👍🏻

Personally, I use them both for different purposes. I really like the cookiebot consent mode template for the ease of use. But in some cases I need more flexibility. For instance if I want to set analytics_storage to granted no matter what (that is in some cases allowed in The Netherlands). Or a client uses some isoteric CMP that is impossible to use. Or they have a custom built cookiebanner. In those latter cases I like to use the consent mode template by Simo Ahava to keep some consistency between my setups.

I'm not an expert in Google Ads, but as far as I know this is not necessary

@@LeonKorteweg appreciate your answer

Thanks for your question! Please note that this is not legal advice. But this is when consent mode is needed: - If you're using Google Ads, either linked to GA4 or tagged directly AND you want to keep using retargeting audiences. - If you're using GA4 with Google Signals engaged (this requires ad_storage). - If you're using GA4 in a country where Google Analytics is prohibited entirely. Technically, in the bottom two cases, consent mode is not required but recommended. You could keep using the old method with blocking triggers and the allow_all_signals parameter in those cases. But I'm not sure if that makes things easier for you 😁

Not nice :( If the timing lines up with your changes it is very likely that it is because of your consent mode config. Difficult to point out what causes this. But I'm guessing that you've set analytics_storage to denied by default and that very few people have accepted cookies. Or there might be something wrong in your setup.

@@LeonKorteweg I just read this comment. It happened to me too and now I am marking analytics_storage as granted. Waiting for it to work. My doubt is if we are violating the rules by putting it this way, since in all the tutorials I've seen about cookiebot, all indicate to put in GTM denied. Thank you very much

Hey I'm sorry, but I have no experience with AdSense and Consent Mode yet. If I come across a solution I'll try to remember to post it here. And others are welcome to chime in as well of course..