Testing the integration with Google Consent Mode V2
In order to test if the Google Consent Mode V2 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 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 use or 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 parameters are properly set to denied in the dataLayer. In order to do that, you can simply type in dataLayer manually in the console of the browser > hit Enter and check if the first entry for the 'consent', 'default' is:
ad_personalization: 'denied', ad_storage: 'denied', ad_user_data: 'denied', analytics_storage: 'denied', functionality_storage: 'denied'
After making sure that the dataLayer is properly set, you should check your store's cookies since the cookies _ga, _gid, _gcl_au 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, _gcl_au and _gat) are set to your store and also if the parameters in the 'consent', 'update' are set to granted by typing in dataLayer again in the console and hit Enter.
ad_personalization: 'granted', ad_storage: 'granted', ad_user_data: 'granted', analytics_storage: 'granted', functionality_storage: 'granted'
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. 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'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 services in your store.
Note that if you have any Google tags set via the native sales channel in Shopify for this in the dataLayer of the store, there will be additional consent parameters set as well.
They are not affecting the integration from the Consentmo GDPR app that you have for the GCM V2 in any way, and as you can also see in the reference below, the parameters from the sales channel are set way after the ones from our solution as well.
We are in contact with the Shopify support on this and as per the latest information from their end, they are working on adding an option for this to be turned off and on as per the user preferences so it does not cause confusion when you have the GCM V2 integration already added from another source.
In need of any assistance with this, do not hesitate to drop us a line at support@consentmo.com or via our Live chat.
Consent Parameters set by the Consentmo GDPR app integration for the GCM V2:
Start off by checking if Google 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 use or 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 parameters are properly set to denied in the dataLayer. In order to do that, you can simply type in dataLayer manually in the console of the browser > hit Enter and check if the first entry for the 'consent', 'default' is:
ad_personalization: 'denied', ad_storage: 'denied', ad_user_data: 'denied', analytics_storage: 'denied', functionality_storage: 'denied'
After making sure that the dataLayer is properly set, you should check your store's cookies since the cookies _ga, _gid, _gcl_au 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, _gcl_au and _gat) are set to your store and also if the parameters in the 'consent', 'update' are set to granted by typing in dataLayer again in the console and hit Enter.
ad_personalization: 'granted', ad_storage: 'granted', ad_user_data: 'granted', analytics_storage: 'granted', functionality_storage: 'granted'
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. 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'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 services in your store.
Consent parameters set by the "Google & Youtube" sales channel in Shopify
Note that if you have any Google tags set via the native sales channel in Shopify for this in the dataLayer of the store, there will be additional consent parameters set as well.
They are not affecting the integration from the Consentmo GDPR app that you have for the GCM V2 in any way, and as you can also see in the reference below, the parameters from the sales channel are set way after the ones from our solution as well.
We are in contact with the Shopify support on this and as per the latest information from their end, they are working on adding an option for this to be turned off and on as per the user preferences so it does not cause confusion when you have the GCM V2 integration already added from another source.
In need of any assistance with this, do not hesitate to drop us a line at support@consentmo.com or via our Live chat.
Updated on: 01/04/2024
Thank you!