Shake integrates an automatic diagnostic of your Google Consent Mode v2 configuration. Once a month, Shake verifies that your implementation is correct.
The "Google Consent Mode Diagnostic" section in Shake
From the Shake page in your Axeptio administration, click on the "Google Consent Mode Check" tab to access the diagnostic. You will find the "Google Consent Mode Diagnostic" table with the results of the latest scan.
This table lists your banners with, for each one, the status of the 4 verified criteria:
Criterion | What Shake verifies |
Late Consent | Are the Consent Mode v2 signals sent to Google before its tags load? A "late" consent means that the tags have already been triggered before the consent status was transmitted to them. |
Default Consent | Is a default consent state (denied) properly defined before any user interaction with your banner? |
Consent Types | Are the consent types required by Google (ad_storage, analytics_storage, etc.) correctly declared? |
Developer ID | Is the Axeptio developer identifier present in your configuration? It allows Google to verify that Axeptio is the CMP being used. |
For each criterion displayed as an error, click on the label in the table to display an explanation and access the documentation to fix the problem.
How the diagnostic works
The diagnostic is fully automatic — you don't have to do anything to launch it.
Frequency: on the 15th of each month, Shake automatically launches a new scan on your project.
Email: with each scan, you receive a summary email of the results, whether your configuration is correct or not.
Results in administration: the results of the latest scan are accessible at any time in the "Google Consent Mode Check" section of the Shake page.
The account-level alert
If one or more criteria are misconfigured, a warning is displayed at the account level in your Axeptio administration, as well as on the Shake page of the affected project.
Click on the project name in this warning to go directly to the diagnostic page and identify the criteria to correct.
Correcting your configuration
If criteria are in error, you must review your Consent Mode v2 implementation. Consult our implementation guides: