UPDATE: It looks like I did not make a mistake after all 😅 Ateeq Ahmad kindly contacted me via LinkedIn to point this out and sent me the links mentioned below (thanks Ateeq!). It turns out Simo Ahava just rectified some of his statements made earlier because of new research findings. His research shows that GA4 will reprocess hits that have been collected without consent, as long as consent is granted later on on that page. See links below for more info. - Simo Ahava LinkedIn Post: www.linkedin.com/posts/simoahava_gtmtips-consent-granted-reprocesses-previously-activity-7171499959047983104-odu5/ - Simo Ahava Blog Post: www.simoahava.com/gtmtips/consent-granted-reprocesses-previously-denied-hits/ Please note that this only applies to Google Tags. You still need to use the techniques from this video for every other (non-Google) tag to make sure they are fired on the first page.
Hi Leon, great content! Couple of questions here: 1) I have a "once per page" rule on the GA4 tag (as I also send a pageview). This is causing the tag not to fire again when the user gives consent. As far as you know, will this create any problem in data collection? 2) when using the setup you suggest in this video, also the Conversion Linker will fire when consent is denied. I guess this is the expected behaviour, as it has ad_storage, ad_personalization and ad_user_data built-in Consent Check. Do you know if this will create any privacy issue? Thank you and keep posting!
Hi Leon - Great Video. I was wondering if you had the chance to test scenarios where a user doesn't accept or deny, and browse the site leaving an open consent banner. is there no GA data reported in this case as consent_update wont trigger, if I am correct?
Ok, very good, you have set up the event update in GA4 as a trigger but why don't you ad also the initialization - All Pages, so will be both in trigger
In my solution this is not necessary, because I've made sure the custom event runs on every page with consent too. Adding Initialization - All Pages will lead to double counting page views on your site, so I don't recommend that. I chose this so you only have to manage one trigger, no two.
What I don't like about the configuration you explain is that the facebook pixel and GA4 tags are triggered twice on each page, because the cookie consent update event is always triggered on each page load(so the tags are being activated in the container load and then in the cookie consent update always)...so what I have done is to put a custom code so that when people click on the cookie banner in accept all or customize, the page reloads. Another way I understand is to create a time trigger, where the facebook and GA4 tags are triggered 2 seconds after the click on the banner. What do you think?
Hey! Thanks for your comment! That page reload is a great and simple solution, well done 👍🏻 I kindly disagree with you on the double loading issue from my solution. That does happen, but only on the first page where users haven't given consent. In that case you want it to fire twice, because the first time they will be blocked by consent settings. After consent has been given or denied those tags will load only one time per page. That time trigger is a great solution and something I show in this video here: ruclips.net/video/jXSnQvCkFzQ/видео.html&ab_channel=LeonKorteweg
@@LeonKorteweg Ok, thanks for your help! When I was trying the cookie consent update as a trigger I was keeping also the allpages trigger(I didn't remove it), so for sure it was for that reason..🤔 Apreciate your videos! I have also used your trick for the consent mode for any type of cookie banner on one of my web pages and it worked great!👏👌
Hello Leon, ik ga er even vanuit dat je Nederlands bent dus ik hou het in het Nederlands. Allereerst bedankt voor je heldere uitleg! Geen probleem dat je een klein foutje hebt gemaakt, gelukkig kan dat weer hersteld worden ( : Ik heb het voor een klant geïmplementeerd maar er is één ding niet helemaal goed gegaan na het toevoegen van de cookie_consent_update trigger voor alle tags. Sommige conversies worden nu voor 3 of 4 geteld waardoor de meting niet meer klopt in Google Ads. Heb jij enig idee waar dit aan zou kunnen liggen? Mijn vermoeden is dat ik de triggers niet aan de juiste tags heb toegevoegd of misschien wel té vaak heb toegevoegd.
Hi Jelmer, I'm keeping it in English so other non-dutchies can follow along ;) You're saying that Google Ads conversions are double counted. Can you please let me know how you've set up the trigger? Is it a thank you page trigger or something else?
Hey Leon. Thank you for all the great content you have been posting! I am facing an issue with my current set up. When a user accept the cookies the Event Consent State doesn't turn On-page Update and Current State to granted unless the user refreshes the page or moves to the second one which defeats the purpose of using the updated setup with the custom trigger. Is there a way of dealing with this? Thanks in advance!
Hi Leon Thanks for your video, I have this question, "The consent types functionality_store and personalization_store always show as denied even though the user has accepted consent. I'm using Usercentric with Termageddon banner." help!!!
Hi! I can't find the video with the manual setup rectified! I used your original setup for the Simo ahava tag but I need to make the changes you mention here!
Lekker bezig Leon, ik was gefrustreerd omdat ik het maar niet werkend kreeg met me Google ADS. Anyway, misschien een idee om eens een schone install video te doen. Gewoon tag maner, ga4 en google ads met conversie op een bedank pagina. Dat is toch wel de meest gestelde vraag zie ik overal. Keep it simpel. De diepte in gaan kan altijd daarna nog. Bedankt voor je lessen. Oja, ik heb gedoe met merdere verschillende campagnes en conversies meten binnen google ads op verschillende domeinen. Wellicht een video of combineren van TAGS en domeinen, dat is ook goede content. Je legt het goed uit namelijk. Suc6
Hello! Yes, you are right, but partially, because there are other countries, not only Europe, which do not need to show the consent window, or need to show it, but as a notification. And you can put cookies on Asian countries without consent, for example, without problems. Therefore, this method is working, but not completely. The problem is aggravated by the fact that all popular services include a million settings that are generally useless and confuse people.
Hello Leon, I set up consent mode v2 using the consent mode template. What happens if configure granted in the analytics storage, while the ad storage and the others are denied, in the default consent mode. Am I only using V2 for Gads while GA4 is not active?
Hi Leon, dank voor de heldere uitleg, super! Ik zit echter met een probleem. Tijdens het uit testen in tag assistant kloppen de instellingen voor on-page default. Echter, vanaf de api gtag("consent", "update", {...}) veranderen de consents van de on-page update en current state van alles, behalve de security_storage, naar denied in plaats van granted. (dus ook de analytics_storage). Dit gebeurt allemaal voordat ik mijn cookie banner heb aangeraakt. Enig idee waar dit door kan komen?
Hi there, I'm answering in English so other non-dutchies can follow along ;) I think there might be a hardcoded gtag consent mode command in your page source that is interfering with your setup. If it's there you should be able to find it by right clicking and inspecting your page source. Then Ctrl+F search for 'gtag'.
Of course you lose all the information before a visitor consents and that's the whole point. A visitor grants the site the permission to get information AFTER they consent. To get this right you have to stop thinking as a webmaster and start thinking as a visitor. You are a visitor on other sites too. Also take into account what the GDPR is about and what it is trying to protect. Also 'referrer' is many times not available so it's not reliable. Google even stopped sending the referrer from Google Search clicks decades back.
Hello Leon, I'm using CookieYes banner and I setted the reload page after cookies consent, in this case I do not have to configure the delay manually right?
hey Leon! maybe you can explain: i set up cookieyes banner via gtm. noticed one situation: user has already accepted cookies, then goes to another page - in gtm I see container loaded with consent denied, then I see update event with consent granted. Is that okay? i thought if user accepts cookies every time he goes to another page consent mode will be granted even on the container loaded level
Hello, What about approach that i use ? I run GA4 tag on 'all pages' view trigger with denied states of consents by default but after a user click on the consent button ( no matter if he change his mind or do it for the first time) i run update event with current states. So, for the first visit eventhough tag is fired with denied by default it collects data after a consent update event happens.
Hard to tell.. I'm not sure if I can follow what you're saying. But if your setup deviates from my instructions be sure to test every possible scenario thoroughly or you might miss out on some data.
Hi Leon, I have implemented this with cookiebot for GA4 events tracking. A user land on a product page for the firsty time. When consent banner pops up, view_item event fires in the backend but GA4 view_item tag is blocked because consent has not granted yet. To fire the tag I added 'cookie_consent_update' trigger and view_item tag is firing at 'cookie_consent_update' event level. The problem I am facing is that product information is being pushed when 'view_item' event is pushed into dataLayer. So my view_item tag is firing but not getting any data because the tag is firing at 'cookie_consent_update' event level instead of 'view_item' event level. view_item tag is firing when consent is granted but value, currency, items variables are not getting view_item data since it is not firing at 'view_item' event level. I hope I explained it properly. 1. So what should I do to solve this? Should I push 'view_item' event with information after 'cookie_consent_update' event? 2. I have another question. Should I fire page view tag like GA4 configuration tag on every page or for the first time page visit?
Yes this is one of the downsides of consent mode. If you set your default and update command at Consent Initialisation, the view_item event should come through if consent has been set. However on the first page without consent you will miss view_item data, because consent is likely given much later on. I've never made a solution for this problem so far, but I think it would be possible to make a script that re-fires every dataLayer events (or a selection of events) when consent changes.
ABOUT THIS VIDEO---> Just an FYI, I set up my GTM watching this video "Set up Consent Mode V2 with any cookiebanner in GTM." I can choose to leave it as is because in CookieYes, if you turn on "Reload page on consent action" under general settings, then the page reloads and the cookie consent is updated. I did test this out on several pages and it works great! However, my question is: When I add this new trigger does it reload the page as well? ABOUT CONSENT MODE---> Also, can you provide documentation about leaving the GA4 settings to built in consent. There are many videos about built in consent and adding consent. Most of them are conflicting information. We are in the United States, so GA4 is acceptable here, but I would like to better understand why you left it as built in consent mode and how you got your information. I would like to learn more about this. I feel as if Google landed a bomb on us, and now we are all trying to run as fast as we can to comply.
@@zerocontentTV well, not sure about your situation, but for me, it does not. For example, when testing this through Google Tag Manager after they have landed on a page from our Google Ads, when the page reloads, I can see in GTM it records the page they landed on. All the conversions are spot on for me. I have been checking the before and after results. Thank you for the comment.
UPDATE: It looks like I did not make a mistake after all 😅 Ateeq Ahmad kindly contacted me via LinkedIn to point this out and sent me the links mentioned below (thanks Ateeq!). It turns out Simo Ahava just rectified some of his statements made earlier because of new research findings.
His research shows that GA4 will reprocess hits that have been collected without consent, as long as consent is granted later on on that page. See links below for more info.
- Simo Ahava LinkedIn Post: www.linkedin.com/posts/simoahava_gtmtips-consent-granted-reprocesses-previously-activity-7171499959047983104-odu5/
- Simo Ahava Blog Post: www.simoahava.com/gtmtips/consent-granted-reprocesses-previously-denied-hits/
Please note that this only applies to Google Tags. You still need to use the techniques from this video for every other (non-Google) tag to make sure they are fired on the first page.
Whether you were wrong or not, thank you very much for your effort and for the simple way in which you explain things, greetings mate
Hi Leon, great content!
Couple of questions here:
1) I have a "once per page" rule on the GA4 tag (as I also send a pageview). This is causing the tag not to fire again when the user gives consent. As far as you know, will this create any problem in data collection?
2) when using the setup you suggest in this video, also the Conversion Linker will fire when consent is denied. I guess this is the expected behaviour, as it has ad_storage, ad_personalization and ad_user_data built-in Consent Check. Do you know if this will create any privacy issue?
Thank you and keep posting!
Hi Leon - Great Video. I was wondering if you had the chance to test scenarios where a user doesn't accept or deny, and browse the site leaving an open consent banner. is there no GA data reported in this case as consent_update wont trigger, if I am correct?
Ok, very good, you have set up the event update in GA4 as a trigger but why don't you ad also the initialization - All Pages, so will be both in trigger
In my solution this is not necessary, because I've made sure the custom event runs on every page with consent too. Adding Initialization - All Pages will lead to double counting page views on your site, so I don't recommend that.
I chose this so you only have to manage one trigger, no two.
What I don't like about the configuration you explain is that the facebook pixel and GA4 tags are triggered twice on each page, because the cookie consent update event is always triggered on each page load(so the tags are being activated in the container load and then in the cookie consent update always)...so what I have done is to put a custom code so that when people click on the cookie banner in accept all or customize, the page reloads. Another way I understand is to create a time trigger, where the facebook and GA4 tags are triggered 2 seconds after the click on the banner. What do you think?
Hey! Thanks for your comment! That page reload is a great and simple solution, well done 👍🏻
I kindly disagree with you on the double loading issue from my solution. That does happen, but only on the first page where users haven't given consent. In that case you want it to fire twice, because the first time they will be blocked by consent settings. After consent has been given or denied those tags will load only one time per page.
That time trigger is a great solution and something I show in this video here: ruclips.net/video/jXSnQvCkFzQ/видео.html&ab_channel=LeonKorteweg
@@LeonKorteweg Ok, thanks for your help! When I was trying the cookie consent update as a trigger I was keeping also the allpages trigger(I didn't remove it), so for sure it was for that reason..🤔 Apreciate your videos! I have also used your trick for the consent mode for any type of cookie banner on one of my web pages and it worked great!👏👌
Ah yes that should do the trick! Well done!
Hello Leon, ik ga er even vanuit dat je Nederlands bent dus ik hou het in het Nederlands.
Allereerst bedankt voor je heldere uitleg! Geen probleem dat je een klein foutje hebt gemaakt, gelukkig kan dat weer hersteld worden ( :
Ik heb het voor een klant geïmplementeerd maar er is één ding niet helemaal goed gegaan na het toevoegen van de cookie_consent_update trigger voor alle tags. Sommige conversies worden nu voor 3 of 4 geteld waardoor de meting niet meer klopt in Google Ads. Heb jij enig idee waar dit aan zou kunnen liggen?
Mijn vermoeden is dat ik de triggers niet aan de juiste tags heb toegevoegd of misschien wel té vaak heb toegevoegd.
Hi Jelmer, I'm keeping it in English so other non-dutchies can follow along ;)
You're saying that Google Ads conversions are double counted. Can you please let me know how you've set up the trigger? Is it a thank you page trigger or something else?
Hey Leon.
Thank you for all the great content you have been posting!
I am facing an issue with my current set up. When a user accept the cookies the Event Consent State doesn't turn On-page Update and Current State to granted unless the user refreshes the page or moves to the second one which defeats the purpose of using the updated setup with the custom trigger. Is there a way of dealing with this? Thanks in advance!
Hi Leon Thanks for your video, I have this question, "The consent types functionality_store and personalization_store always show as denied even though the user has accepted consent. I'm using Usercentric with Termageddon banner." help!!!
Hi! I can't find the video with the manual setup rectified! I used your original setup for the Simo ahava tag but I need to make the changes you mention here!
Sorry, late reply.. But I think you're looking for this video: ruclips.net/video/jXSnQvCkFzQ/видео.html
Lekker bezig Leon, ik was gefrustreerd omdat ik het maar niet werkend kreeg met me Google ADS. Anyway, misschien een idee om eens een schone install video te doen. Gewoon tag maner, ga4 en google ads met conversie op een bedank pagina. Dat is toch wel de meest gestelde vraag zie ik overal. Keep it simpel. De diepte in gaan kan altijd daarna nog. Bedankt voor je lessen.
Oja, ik heb gedoe met merdere verschillende campagnes en conversies meten binnen google ads op verschillende domeinen. Wellicht een video of combineren van TAGS en domeinen, dat is ook goede content. Je legt het goed uit namelijk.
Suc6
Thanks Alex!
Hello!
Yes, you are right, but partially, because there are other countries, not only Europe, which do not need to show the consent window, or need to show it, but as a notification. And you can put cookies on Asian countries without consent, for example, without problems. Therefore, this method is working, but not completely. The problem is aggravated by the fact that all popular services include a million settings that are generally useless and confuse people.
I've covered multi-region setups in a different video. Check it here if you're interested: ruclips.net/video/eGIaKe8FojI/видео.html
Hello Leon, I set up consent mode v2 using the consent mode template. What happens if configure granted in the analytics storage, while the ad storage and the others are denied, in the default consent mode. Am I only using V2 for Gads while GA4 is not active?
Hi Leon, dank voor de heldere uitleg, super!
Ik zit echter met een probleem. Tijdens het uit testen in tag assistant kloppen de instellingen voor on-page default. Echter, vanaf de api gtag("consent", "update", {...}) veranderen de consents van de on-page update en current state van alles, behalve de security_storage, naar denied in plaats van granted. (dus ook de analytics_storage). Dit gebeurt allemaal voordat ik mijn cookie banner heb aangeraakt. Enig idee waar dit door kan komen?
Hi there, I'm answering in English so other non-dutchies can follow along ;)
I think there might be a hardcoded gtag consent mode command in your page source that is interfering with your setup. If it's there you should be able to find it by right clicking and inspecting your page source. Then Ctrl+F search for 'gtag'.
Of course you lose all the information before a visitor consents and that's the whole point. A visitor grants the site the permission to get information AFTER they consent. To get this right you have to stop thinking as a webmaster and start thinking as a visitor. You are a visitor on other sites too. Also take into account what the GDPR is about and what it is trying to protect. Also 'referrer' is many times not available so it's not reliable. Google even stopped sending the referrer from Google Search clicks decades back.
Hello Leon, I'm using CookieYes banner and I setted the reload page after cookies consent, in this case I do not have to configure the delay manually right?
Yes, a page reload will do the job too! well done 👊🏻
Hello, I also used CookieYes. How do I implement the page reload?
hey Leon! maybe you can explain: i set up cookieyes banner via gtm. noticed one situation: user has already accepted cookies, then goes to another page - in gtm I see container loaded with consent denied, then I see update event with consent granted. Is that okay? i thought if user accepts cookies every time he goes to another page consent mode will be granted even on the container loaded level
Hello, What about approach that i use ? I run GA4 tag on 'all pages' view trigger with denied states of consents by default but after a user click on the consent button ( no matter if he change his mind or do it for the first time) i run update event with current states. So, for the first visit eventhough tag is fired with denied by default it collects data after a consent update event happens.
Hard to tell.. I'm not sure if I can follow what you're saying. But if your setup deviates from my instructions be sure to test every possible scenario thoroughly or you might miss out on some data.
Man thanks a lot for your job !! helping me a lot
Hi Leon, I have implemented this with cookiebot for GA4 events tracking. A user land on a product page for the firsty time. When consent banner pops up, view_item event fires in the backend but GA4 view_item tag is blocked because consent has not granted yet. To fire the tag I added 'cookie_consent_update' trigger and view_item tag is firing at 'cookie_consent_update' event level.
The problem I am facing is that product information is being pushed when 'view_item' event is pushed into dataLayer. So my view_item tag is firing but not getting any data because the tag is firing at 'cookie_consent_update' event level instead of 'view_item' event level.
view_item tag is firing when consent is granted but value, currency, items variables are not getting view_item data since it is not firing at 'view_item' event level.
I hope I explained it properly.
1. So what should I do to solve this? Should I push 'view_item' event with information after 'cookie_consent_update' event?
2. I have another question. Should I fire page view tag like GA4 configuration tag on every page or for the first time page visit?
Yes this is one of the downsides of consent mode. If you set your default and update command at Consent Initialisation, the view_item event should come through if consent has been set.
However on the first page without consent you will miss view_item data, because consent is likely given much later on.
I've never made a solution for this problem so far, but I think it would be possible to make a script that re-fires every dataLayer events (or a selection of events) when consent changes.
ABOUT THIS VIDEO---> Just an FYI, I set up my GTM watching this video "Set up Consent Mode V2 with any cookiebanner in GTM." I can choose to leave it as is because in CookieYes, if you turn on "Reload page on consent action" under general settings, then the page reloads and the cookie consent is updated. I did test this out on several pages and it works great! However, my question is: When I add this new trigger does it reload the page as well?
ABOUT CONSENT MODE---> Also, can you provide documentation about leaving the GA4 settings to built in consent. There are many videos about built in consent and adding consent. Most of them are conflicting information. We are in the United States, so GA4 is acceptable here, but I would like to better understand why you left it as built in consent mode and how you got your information. I would like to learn more about this. I feel as if Google landed a bomb on us, and now we are all trying to run as fast as we can to comply.
but even if you reload, don't you lose all the important info that the user had coming to your landing page? not sure about that
@@zerocontentTV well, not sure about your situation, but for me, it does not. For example, when testing this through Google Tag Manager after they have landed on a page from our Google Ads, when the page reloads, I can see in GTM it records the page they landed on. All the conversions are spot on for me. I have been checking the before and after results. Thank you for the comment.