Starting March 6th, 2024, Google requires that all advertisers send verifiable consent signals to Google to comply with the General Data Protection Regulation (GDPR) and ePrivacy Directive (ePD). This applies to anyone setting up new ad campaigns via Google Ads products, in the European Economic Area (EEA).
Sending consent signals is most commonly accomplished by setting up tracking using Google’s analytics tools: Google Ads, Floodlight and Google Analytics. Most advertising has this passed into Google Tag Manager.
Duda has several Consent Management Platforms (CMPs) integrated in which support this requirement.
At the heart of the consent signal requirements is making sure that user consent preferences are sent to Google. Since CMP tools already collect consent, it’s a perfect place to integrate the signals being sent to Google. Duda has two core products that support Consent and Consent Mode requirements by Google. Both of these products are verified by Google to support Consent Mode.
The Usercentrics and Springtime Apps do not currently support this.
Termly has two options for enabling consent:
-
Enable Consent Mode under your regional Consent Settings in the Termly dashboard.
-
Enable Consent Mode using Termly's Google Tag Manager template.
For additional information, please visit Termly's page Google Consent Mode and Termly CMP.
Google Consent Mode can be enabled on a region-by-region basis from the Termly dashboard. To do this, navigate to your consent banner settings and enable 'Google Consent Mode' for any region under your 'Consent Settings'.
When Consent Mode is enabled in your consent settings, gtags will be exempted from blocking by Auto Blocker. This means that gtags will always be allowed to run on page load.
If you prefer that gtags are not exempted by Auto Blocker when Consent Mode is enabled, you can use manual blocking to assign them to the appropriate blocking category.
You can also use the existing template, already inside of Google Tag Manager to set up Consent Mode. See the instructions from Termly here.
The Duda integration with Cookiebot is automatically configured to support Advanced Consent mode out of the box. There’s nothing you need to enable to support this.
Cookiebot is currently only available on a custom plan.
Consent mode allows Google to load lightweight, privacy-friendly tracking before users consent to being tracked. This data does not directly go into reporting tools, because it can’t be related to an individual site user. Instead, Google uses this data to create user behavior models for high-traffic campaigns.
Consent mode also provides the API and path for CMP tools to communicate with Google Tags about the consent status of the user on the site and what types of categories/services the customer has opted into.
Following Google's March 2024 EUUCP policy update, websites that do not obtain consent from visitors from the EEA, EU, or UK and do not have banners integrated with Consent Mode v2 may experience measurement loss for Google Ad campaigns.
To continue using measurement, ad personalization, and remarketing features, opt-in consent is required from end users in the above regions for the use of their data and these consent signals must be shared with Google. These requirements extend to the use of Google Analytics data with any Google service.