Are you using the WRONG trigger with Consent Mode?!?

hey there I'm Benjamin from loves data in this video I'm going to answer a question that's been popping up about consent mode when we're using Google tag manager to send data to Google analytics the question is about which trigger we should be using for our Google analytics tag let's head to Google tag manager to answer this question as we can see I'm using the initialization all pages trigger this trigger will mean that the tag fires on all of the pages of our website and since the Google tag has consent mode built in it will automatically adjust based on the selections people make on our consent Banner however I've had a couple of people suggest that this isn't the best trigger to use and that I should be using the cookie consent update trigger Instead This trigger will fire the tag once someone provides consent the reason a couple of people are suggesting this is because they say you us the initialization all pages trigger will result in less accurate data the suggestion is that when people land on the website the basic hit will be sent to Google analytics then once consent is provided when the next event is tracked it will be missing important data this will apparently include the original method people use to find the website including the original Source medium and other information about acquisition so rather than just answering this question in the comments I thought we'd actually have a look and test things out to begin with let's click preview to open tag assistant and now I'm going to enter the URL of my demo site and click connect to see what happens our website loads and I've already implemented cookie bot on this website because I've done a couple of videos with cookiebot we can see the consent Banner pops up and currently consent hasn't been provided yet so let's see what we have in tag assistant so far let's open tag assistant and let's select the consent tab we can see that the original consent state for ad storage analytic storage and so on were all set to denied and they're still set to denied so this confirms we haven't provided consent yet now let's travel back to the tags tab we can see that some of the Google Tags have fired again these have built in consent checks for consent mode which means they're automatically adjusting their behavior so the Google tag is just sending basic information to Google analytics we can verify this by selecting the measurement ID at the top in tag assistant we can see a page view has been sent let's select this and here we can see the cookie consent State this parameter is set to g100 now in previous videos I've covered this basically g100 means consent hasn't been provided yet it's just sending basic information without cookies being stored in the browser once we have granted consent if we come back we'll see this switch to G11 which means consent has been granted okay so what we're going to do now is we're going to disconnect tag assistant this is because we're going to adjust the URL slightly before we do this let's head to Google analytics I've already opened the debug view in the admin area of my Google analytics demo property and since we haven't provided consent yet the debug view is also blank so again until we provide consent we won't see the events appear in Google analytics even in the debug view now let's head back to Google tag manager and let's click preview again this time I'm going to change the url slightly what we're going to do is we're going to add some campaign tags to the URL I'm going to add UTM campaign equals Benjamin and UTM Source equals Benjamin and UTM medium equals Benjamin and I'm doing this for testing if Google analytics will capture this information now let's click connect the demo site loads again but this time we can see the UTM parameters in the URL we now have the campaign source and medium we entered we can also see the consent Banner is still appearing which means I still haven't provided consent yet and let's click allow all now that we've allowed L cookies let's travel through to another page I'm going to navigate to the contact page let's take a look at TAG assistant [Music] again we can see again our tags are fired let's select the measurement ID at the top and let's select the most recent page view event that has been sent to Google analytics we can now see that the cookie consent mode parameter has been been updated to G11 which means all of the available information is being sent to Google analytics so now we can find out if we've lost the original source and medium along with the campaign that I added as UTM parameters to the URL to find out what is being collected into our reports let's head back to Google analytics it might take a moment for the event to appear in debug view so let's wait wa a moment and we can see they've [Music] appeared we can see there is a page view event and user engagement events the user engagement events were collected after we provided consent so theoretically they shouldn't include any details about how we found the website let's select one of the user engagement events and we can see there are parameters for medium source and campaign let's select one of these and we can see it contains the value from my UTM parameter so this is telling us we're actually capturing the original information even after consent was granted on the website we can also check this by navigating to the real time report and let's look for the event count by event name card and select the user engagement event again we can see the medium source and campaign and selecting these shows us the value I set for the UTM parameter so again this is telling us that the original method of finding the website is coming through to Google analytics this tells us that we can continue to use the initialization all pages trigger for all of the Google tags that have built-in consent settings including tags for Google analytics and Google ads and I also wanted to show you that this data appears in the standard reports so we're going to fast forward 24 hours now let's take a look at what appears in the reports after we've waited a day okay let's navigate to traffic acquisition under acquisition let's change the default Dimension to session campaign and I'm going to search for Benjamin to narrow the focus of the report now let's click the plus sign and search for and select landing page we can now see the homepage is reported as the landing page for the campaign tagged UR l i used for testing this tells us that Google analytics is reprocessing the original page view event that we viewed before providing consent on the website so again this shows us that we can use the initialization all pages trigger to fire our tags without losing data or ending up with missing information about the original method we used to find the website that's all for now I hope you enjoyed this video thanks for watching and if you haven't already please take a moment to subscribe to this channel for all of the latest updates I'll see you in the next video

Channel: Loves Data

Views: 2,024

Keywords:

Id: puVkxXMymg8

Length: 9min 39sec (579 seconds)

Published: Mon May 13 2024