Google Consent Mode is essential for ensuring your website is compliant with privacy regulations while allowing targeted advertisements. This guide walks you through verifying the correct installation and troubleshooting issues in your Google Consent Mode setup.
Verify your installation
Verify GCM is Enabled in Osano
-
Check the Osano Configuration:
- On my.osano.com navigate to Cookie Consent > your Configuration.
- In Settings, ensure the Google Consent Mode setting is toggled ON
- Ensure the Cookie Consent Configuration has been published after this setting was enabled.
Check the Installation Sequence
-
Check the Source Code
- Right click on your website and choose "View Source Code" option from the menu. In your source code, check the loading sequence to verify that the default data layer, Osano script, and Google Tag Manager container load in the correct order:
- The default data layer must load first, without asynchronous or deferred loading.
- The Osano script should execute second.
- The Google Tag Manager container should execute last
- Right click on your website and choose "View Source Code" option from the menu. In your source code, check the loading sequence to verify that the default data layer, Osano script, and Google Tag Manager container load in the correct order:
-OR-
-
Check the Elements Tab
- Navigate to the customer's website and opening your browser’s Developer Tools.
- Open the Elements tab and check the loading sequence to verify that the default data layer, Osano script, and Google Tag Manager container load in the correct order:
- The default data layer must load first, without asynchronous or deferred loading.
- The Osano script should execute second.
- The Google Tag Manager container should execute last
Check the Data Layer
-
View the Data Layer:
- On your website, open your developer tools and, in the Console tab, type
dataLayerand expand the data layer object. - Look for two key events:
"consent default event"and"consent update event."- The consent update event appears only after consent has been granted, which may not occur immediately in regions like the EU where consent is not granted by default. Both must be present to ensure consent is being set and then updated.
- On your website, open your developer tools and, in the Console tab, type
Verify Google Tags
-
Check Google Consent Services (GCS) Status:
- On your website, open your developer tools and, in the Network tab, select "All" entries and search for "GCS."
- Inside each Google tag, you should find a "GCS=G1xx" code. This code indicates the status of Google Consent Services and should reflect the level of consent granted:
-
No Consent:
GCS=G100 -
Ads ONLY:
GCS=G110 -
Analytics ONLY:
GCS=G101 -
All (Ads + Analytics):
GCS=G111
-
No Consent:
Use the Google Consent Mode Debugger
-
GCM Debugger:
- For further validation, use the Google Consent Mode Debugger. This tool provides insights into how consent status is being handled across your Google Tags.
Ensure Proper Classification of Google Content
Check the classification of the Google content within the Osano platform. Ensure that each Google tag (e.g., Analytics, Ads, etc.) is categorized correctly, depending on whether you're using a basic or advanced installation.
By following these steps, you can verify the correct installation of Google Consent Mode and resolve any issues that might arise. If you need further assistance, refer to the Google Ads Help Center or reach out to support for additional guidance.
Related to