Testing the integration with Google Consent Mode
In order to test if the Google Consent Mode is set properly you should first clear your browser's cookies or open your store through incognito mode and follow those steps:
Start off by checking if Google Tag Manager's tags are fired initially, before the Cookie bar is accepted. In order to check if the tags are fired, you can either use Google Tag Manager's preview mode, or if you don't have access to Google Tag Manager use the Google Tag Assistant browser extension which you can download from here.
After that you should make sure that the ad_storage and analytics_storage are properly set to denied in the dataLayer. In order to do that, you can simply write dataLayer in the console and check if the first entry is:
{"consent","default",{"ad_storage":"denied","analytics_storage":"denied"}}
After making sure that the dataLayer is properly set, you should check your store's cookies since the cookies \_ga, \_gid, and \_gat should not be set before the Cookie bar is accepted. Note that if any of the cookies are set, then you are likely adding them through an inline script, like analytics.js (which doesn't support Google Consent Mode). In order to properly check which cookies are set to your store, we recommend using the EditThisCookies browser extension, which you can download from here.
Lastly, you should give your consent by accepting the Cookie bar and making sure that the Marketing and Analytics cookie categories are not blocked. After accepting it, you will have to check if the cookies that we mentioned in step 3 (_ga, _gid, and _gat) are set to your store and also if the ad_storage and analytics_storage are set to granted in the dataLayer as shown in this image:
If the cookies and the update settings in the dataLayer are set then the Google Consent Mode should be working properly.
If every step of the testing is successful but you are not getting the data you are expecting, unfortunately, we can't provide any further help in this regard.
Google Consent Mode is essentially an API which we use to pass consent data to Google Tag Manager. How a tag is supposed to respond to this data is beyond our purview. We can, and will be happy to check if you have correctly set things up in regards to our app's sending, and Google Tag Manager's receiving of consent settings.
However, we have no insight in what tags do with these settings. We can't comment on how Google Analytics should behave when it receives the Google Consent Mode instructions, or speak on Google's behalf in regards to what data should be logged.
This may seem dismissive, but there's nothing we can do on our end to improve the data logging in Google Analytics. Our app's scripts merely respectively set and update the consent state to Google Tag Manager.
For more information on Google Consent Mode and the behavior of tags, you can check Google's own documentation on Consent Mode from here.
Start off by checking if Google Tag Manager's tags are fired initially, before the Cookie bar is accepted. In order to check if the tags are fired, you can either use Google Tag Manager's preview mode, or if you don't have access to Google Tag Manager use the Google Tag Assistant browser extension which you can download from here.
After that you should make sure that the ad_storage and analytics_storage are properly set to denied in the dataLayer. In order to do that, you can simply write dataLayer in the console and check if the first entry is:
{"consent","default",{"ad_storage":"denied","analytics_storage":"denied"}}
After making sure that the dataLayer is properly set, you should check your store's cookies since the cookies \_ga, \_gid, and \_gat should not be set before the Cookie bar is accepted. Note that if any of the cookies are set, then you are likely adding them through an inline script, like analytics.js (which doesn't support Google Consent Mode). In order to properly check which cookies are set to your store, we recommend using the EditThisCookies browser extension, which you can download from here.
Lastly, you should give your consent by accepting the Cookie bar and making sure that the Marketing and Analytics cookie categories are not blocked. After accepting it, you will have to check if the cookies that we mentioned in step 3 (_ga, _gid, and _gat) are set to your store and also if the ad_storage and analytics_storage are set to granted in the dataLayer as shown in this image:
If the cookies and the update settings in the dataLayer are set then the Google Consent Mode should be working properly.
If every step of the testing is successful but you are not getting the data you are expecting, unfortunately, we can't provide any further help in this regard.
Google Consent Mode is essentially an API which we use to pass consent data to Google Tag Manager. How a tag is supposed to respond to this data is beyond our purview. We can, and will be happy to check if you have correctly set things up in regards to our app's sending, and Google Tag Manager's receiving of consent settings.
However, we have no insight in what tags do with these settings. We can't comment on how Google Analytics should behave when it receives the Google Consent Mode instructions, or speak on Google's behalf in regards to what data should be logged.
This may seem dismissive, but there's nothing we can do on our end to improve the data logging in Google Analytics. Our app's scripts merely respectively set and update the consent state to Google Tag Manager.
For more information on Google Consent Mode and the behavior of tags, you can check Google's own documentation on Consent Mode from here.
Updated on: 24/11/2023
Thank you!