Using Google Consent Mode Integration
Learn how to use Google Consent Mode integration in your Shopify store. Our guide provides step-by-step instructions to enhance privacy and tracking compliance.
Navigate to Settings > Integrations
Switch on the integration and some options will open.
Your options are:
With the integration enabled, the Google Consent Mode will be automatically enabled for the Google products you have manually setup in your theme.liquid without any further action. So you activate the integration and you save.
If you want to load your Google tags from our app, then you just add these tag ids below where it says Google properties. Then our app will load these Google Tags for you with Google Consent Mode enabled.
When you click any of these options you are able to add the corresponding tag id.
For Adwords, the AW property can be found here:
On the popup on top you can see the AW-xxxxxxxxxx property.
If you use the Google & YouTube channel just check the first option (Check if you are using the Google & YouTube channel).
Google Consent Mode supports seven consent types based on version 1 & version 2. Our application maps these consent types into the app categories. You do not have to change the mappings but if you need to here is the section to do it. Google supports the following types to adjust the behavior of Google tags on your store:
The default value of these types is based on the banner mode you have selected. You can read more about Google Consent Mode here.
When ad_storage is denied, new cookies will not be set for advertising purposes. Additionally, third-party cookies previously set on google.com and doubleclick.net will not be used except for spam and fraud purposes. Data sent to Google will still include the full page URL, including any ad click information in the URL parameters.
To further redact your ads data when ad_storage is denied, you can check the ads_data_redaction option.
When ads_data_redaction is checked and ad_storage is denied, ad click identifiers sent in network requests by Google Ads and Floodlight tags will be redacted. Network requests will also be sent through a cookieless domain.
The ads_data_redaction parameter will have no effect when ad_storage is granted.
When a user lands on your store after clicking an ad, information about the ad may be appended to your landing page URLs as a query parameter. In order to improve conversion accuracy, Google tags usually store this information in first-party cookies on your domain.
However, if ad_storage is set to denied, Google tags will not save this information locally. To improve ad click measurement quality when ad_storage is denied, you can optionally elect to pass ad click information through URL parameters across pages using URL passthrough.
Similarly, if analytics_storage is set to denied, URL passthrough can be used to send event and session-based analytics (including conversions) without cookies across pages.
The following conditions must be met in order to use URL passthrough:
The outgoing link refers to the same domain as the current page's domain.
A gclid/dclid is present in the URL (Google Ads and Floodlight tags only)
When using URL passthrough, a few query parameters may be appended to links as users navigate through pages on your website:
gclid
dclid
gclsrc
_gl
wbraid
For best results, ensure that:
Redirects on your site pass all the above query parameters.
Your analytics tools ignore these parameters in-page URLs.
These parameters do not interfere with your store's behavior.
Here is the time in milliseconds to wait until user updates the consent. This timeout determines how long Google’s tags wait for a possible update command, if the user’s consent choices are resolved asynchronously. This will allow those tasks time to complete before Google tags fire. You can increase the number if you see big differences in your sessions tracked in analytics.
In special cases that you have changed the dataLayer name to a different one you will need to edit this default property name on our integration with GTM as well in order to push the data to the property you finally use for this purpose.
Once you have enabled the integration for your store, our application will automatically signal the consent choices of your visitors to Google instead of blocking tags when not consented. The end user's granular consent will be used by Google to adjust tag behavior accordingly.
With the Google Consent Mode and our app's integration in place, will let our application allow tags to run and Google will act e.g. re-marketing and log analytics data according to the signal sent by our app.
Google describes the technical details of how supported tags changes behavior based on the end user's consent here.
With this integration, you can get valuable insights from campaigns and measure conversions while respecting users' consent choices. Google Consent Mode is a step toward honoring the privacy of individual users without altering the foundation of the digital economy.
How to enable Google Consent Mode
Navigate to Settings > Integrations
Switch on the integration and some options will open.
Your options are:
With the integration enabled, the Google Consent Mode will be automatically enabled for the Google products you have manually setup in your theme.liquid without any further action. So you activate the integration and you save.
If you want to load your Google tags from our app, then you just add these tag ids below where it says Google properties. Then our app will load these Google Tags for you with Google Consent Mode enabled.
Enable tag IDs
When you click any of these options you are able to add the corresponding tag id.
Adwords
For Adwords, the AW property can be found here:
On the popup on top you can see the AW-xxxxxxxxxx property.
Advanced settings
Google & YouTube channel
If you use the Google & YouTube channel just check the first option (Check if you are using the Google & YouTube channel).
Consent types
Google Consent Mode supports seven consent types based on version 1 & version 2. Our application maps these consent types into the app categories. You do not have to change the mappings but if you need to here is the section to do it. Google supports the following types to adjust the behavior of Google tags on your store:
| Key | Value | Description | Pandectes Category |
|---|---|---|---|
| ad_storage | denied or granted | Controls whether your tags will use cookies related to advertising. | Targeting |
| ad_user_data | denied or granted | Sets consent for sending user data to Google for online advertising purposes. | Targeting |
| ad_personalization | denied or granted | Sets consent for personalized advertising. | Targeting |
| analytics_storage | denied or granted | Controls whether your tags will use cookies related to analytics. | Performance |
| functionality_storage | denied or granted | Controls whether your tags will use cookies related to functionality. | Functionality |
| personalization_storage | denied or granted | Controls whether your tags will use cookies related to personalization. | Functionality |
| security_storage | denied or granted | Controls whether your tags will use cookies related to security. | Strictly necessary |
The default value of these types is based on the banner mode you have selected. You can read more about Google Consent Mode here.
Redact ads data
When ad_storage is denied, new cookies will not be set for advertising purposes. Additionally, third-party cookies previously set on google.com and doubleclick.net will not be used except for spam and fraud purposes. Data sent to Google will still include the full page URL, including any ad click information in the URL parameters.
To further redact your ads data when ad_storage is denied, you can check the ads_data_redaction option.
When ads_data_redaction is checked and ad_storage is denied, ad click identifiers sent in network requests by Google Ads and Floodlight tags will be redacted. Network requests will also be sent through a cookieless domain.
The ads_data_redaction parameter will have no effect when ad_storage is granted.
URL passthrough
When a user lands on your store after clicking an ad, information about the ad may be appended to your landing page URLs as a query parameter. In order to improve conversion accuracy, Google tags usually store this information in first-party cookies on your domain.
However, if ad_storage is set to denied, Google tags will not save this information locally. To improve ad click measurement quality when ad_storage is denied, you can optionally elect to pass ad click information through URL parameters across pages using URL passthrough.
Similarly, if analytics_storage is set to denied, URL passthrough can be used to send event and session-based analytics (including conversions) without cookies across pages.
The following conditions must be met in order to use URL passthrough:
The outgoing link refers to the same domain as the current page's domain.
A gclid/dclid is present in the URL (Google Ads and Floodlight tags only)
When using URL passthrough, a few query parameters may be appended to links as users navigate through pages on your website:
gclid
dclid
gclsrc
_gl
wbraid
For best results, ensure that:
Redirects on your site pass all the above query parameters.
Your analytics tools ignore these parameters in-page URLs.
These parameters do not interfere with your store's behavior.
Wait for update
Here is the time in milliseconds to wait until user updates the consent. This timeout determines how long Google’s tags wait for a possible update command, if the user’s consent choices are resolved asynchronously. This will allow those tasks time to complete before Google tags fire. You can increase the number if you see big differences in your sessions tracked in analytics.
DataLayer property
In special cases that you have changed the dataLayer name to a different one you will need to edit this default property name on our integration with GTM as well in order to push the data to the property you finally use for this purpose.
Benefits by using this integration
Once you have enabled the integration for your store, our application will automatically signal the consent choices of your visitors to Google instead of blocking tags when not consented. The end user's granular consent will be used by Google to adjust tag behavior accordingly.
With the Google Consent Mode and our app's integration in place, will let our application allow tags to run and Google will act e.g. re-marketing and log analytics data according to the signal sent by our app.
Google describes the technical details of how supported tags changes behavior based on the end user's consent here.
With this integration, you can get valuable insights from campaigns and measure conversions while respecting users' consent choices. Google Consent Mode is a step toward honoring the privacy of individual users without altering the foundation of the digital economy.
Updated on: 23/08/2024
Thank you!