Google Tag Manager Consent Settings for Google Services
Not too long ago, Google announced a new consent mode for Google tags. It allows you to build a mechanism where Google’s tags parse, react, and respond to the consent status of your store visitors.
In short, consent mode is a feature, which lets you determine whether or not Google’s advertising tags (Ads and Floodlight) and GA tags can utilize browser storage when sending pings to Google’s servers.
Google Tag Manager (GTM) is a tool that allows you to manage and deploy tags (snippets of code or tracking pixels) on your website without having to modify your site code.
Consent mode has two variants. There are the default settings the page will use while waiting for the user’s consent status to be resolved. Then there are the updated settings that are sent as soon as consent has been resolved.
Our application makes all the appropriate preparation in order for this to work properly. The only requirement from our application side is to enable the Google Consent Mode integration.
First, you will need to enable consent overview which can be found in Container Settings.
To find out whether data is being transferred to Google correctly, open the collect request in the Network tab of the Chrome Dev Tools. There you will find the parameter gcs = G1XX sent with all Google hits (Analytics, Ads, or Floodlight). G1 is always identical. This is followed by 2 digits: 1 stands for approval and 0 for rejection.
Please use incognito mode on your browser to verify that ex. Google Ads isn’t setting cookies when consent isn’t granted, but at the same time, data are being sent with the correct value in the gcs-parameter.
Give consent, and verify that Tags are triggered correctly, and cookies from the respective Tags are being set. To verify Tags with built-in consent, you will have to check the Network Tab in your Browser Console.
If everything seems correct in GTM Preview Mode, you have now completed the setup.
In short, consent mode is a feature, which lets you determine whether or not Google’s advertising tags (Ads and Floodlight) and GA tags can utilize browser storage when sending pings to Google’s servers.
Google Tag Manager (GTM) is a tool that allows you to manage and deploy tags (snippets of code or tracking pixels) on your website without having to modify your site code.
How it works
Consent mode has two variants. There are the default settings the page will use while waiting for the user’s consent status to be resolved. Then there are the updated settings that are sent as soon as consent has been resolved.
Our application makes all the appropriate preparation in order for this to work properly. The only requirement from our application side is to enable the Google Consent Mode integration.
Activation of consent
First, you will need to enable consent overview which can be found in Container Settings.
Testing Google Consent Mode
To find out whether data is being transferred to Google correctly, open the collect request in the Network tab of the Chrome Dev Tools. There you will find the parameter gcs = G1XX sent with all Google hits (Analytics, Ads, or Floodlight). G1 is always identical. This is followed by 2 digits: 1 stands for approval and 0 for rejection.
Please use incognito mode on your browser to verify that ex. Google Ads isn’t setting cookies when consent isn’t granted, but at the same time, data are being sent with the correct value in the gcs-parameter.
Give consent, and verify that Tags are triggered correctly, and cookies from the respective Tags are being set. To verify Tags with built-in consent, you will have to check the Network Tab in your Browser Console.
If everything seems correct in GTM Preview Mode, you have now completed the setup.
Updated on: 19/12/2024
Thank you!