Maximize message coverage

To help you maximize your IAB TCF coverage for end user traffic in the European Economic Area (EEA), the United Kingdom (UK), and Switzerland, a maximize message coverage control is available at the account level. This setting can be considered a safety net for IAB TCF coverage across all of your sites and apps.

When you enable this setting:

  • The Google CMP will attempt to serve a fallback consent message anytime we detect a request without a TC string in the EEA, the UK or Switzerland. This scenario could happen if you haven't implemented a CMP in your app or on your site, the CMP is not integrated with the TCF, or if the CMP malfunctions or fails to collect an end user’s consent decision for any reason. This behavior will apply to all of your existing sites and apps, as well as any new sites or apps you create.
    • For apps: The fallback consent message will be served via an eligible ad unit any time there's an ad request without a TC string in the EEA, UK, or Switzerland.
    • For sites: The fallback consent message will be served directly from the GPT tag on your site any time the user is in the EEA, UK, or Switzerland, but there is no TCF CMP detected on the page.
  • The Google CMP will automatically create a published message for every new site or app in your account.

This feature impacts all sites and apps in your account, including sites and apps that you manage in AdSense or AdMob.

Turn maximize message coverage on or off

To turn maximize message coverage on or off at the account level:

  1. Sign in to Google Ad Manager.
  2. Navigate to Privacy & messaging.
  3. On the "European regulations" message card, click Manage or Create.
  4. Click Settings.
  5. In the "Maximize message coverage" section, use the Allow Google to maximize message coverage checkbox to turn the setting on or off.
  6. Click Save.
Note: In the majority of cases the maximize message coverage account-level control and optimize consent message message-level control are both enabled by default, meaning all fallback consent messages and auto-created messages deployed on your sites under the maximize message coverage control are opted in to consent optimization. If you want to opt out of consent optimization completely, ensure that the maximize message coverage setting is disabled and that you manually opt out of optimization for every message you create, as we do not currently support disabling optimization at the individual message level when messages are served via fallback consent collection under the maximize message coverage setting.

Fallback consent behavior

If you don’t want to serve fallback consent messages across all your sites and apps, you can disable the account-level maximize message coverage control. For apps, you can optionally enable specific apps for fallback consent collection under the separate fallback consent collection control at the app level.

If no message is published for a site or app when maximize message coverage is activated, the fallback consent message will use default styles and the list of vendors configured in the European regulations settings page of Privacy & messaging. It will contain two buttons ("Manage Options" and "Consent"). If you want to customize the message for a specific app, you can create a published message for that app. Learn more about European regulations message configuration options.

Example of a European regulations messages with two buttons (Manage options, Consent):

Fallback messaging behavior for apps

When maximize message coverage is enabled, Google CMP will attempt to display the fallback message via an eligible ad unit when a TC string is missing for an ad request in the EEA, UK, or Switzerland. When the maximize message coverage control is enabled, it overrides any app’s fallback consent collection control status. For example, if an app is not opted in to fallback consent collection individually, a fallback message will still serve to end users if maximize message coverage is enabled and there is no TC string for an ad request in the EEA, UK, or Switzerland.

See below for further information on how the maximize message coverage control works for your apps. We encourage you to evaluate whether this control aligns with your data processing requirements and to verify that your consent messages are displaying correctly.

App’s CMP status What happens when maximize message coverage is enabled
App is successfully collecting end user consent decisions via Google CMP or a third-party certified CMP. No fallback message will be served since consent is successfully collected.
App is not successfully collecting end user consent decisions via Google CMP or a third-party certified CMP, for example, due to a bug or transient error with the CMP. Google CMP will attempt to serve a fallback message in an eligible ad unit if a TC string is missing when an ad is requested in the EEA, UK, or Switzerland.
App is not successfully collecting end user consent decisions because no CMP has been implemented in the app or because the CMP used is not integrated with the TCF. Google CMP will attempt to serve a fallback message in an eligible ad unit if a TC string is missing when an ad is requested in the EEA, UK, or Switzerland.
Notes:
  • If maximize message coverage is off at the network level, and you haven't optionally enabled specific apps for fallback consent collection under the fallback consent collection control, then no fallback messages are served regardless of the app’s CMP status.
  • Fallback messaging isn't yet supported with the Google Mobile Ads Next-Gen SDK. Implement the UMP SDK to get Google CMP functionality, or use another CMP when using the Google Mobile Ads Next-Gen SDK.

Fallback messaging behavior for sites

When maximize message coverage is enabled, a fallback message will be served any time the user is in the EEA, UK, or Switzerland, but there is no TCF CMP detected on the page.

Important: If you have Multiple Customer Management relationships, your MCM parents or children may also be eligible to show messages on your sites, including fallback consent messages. To ensure that a single account is used to control all messaging behavior on your site, you should append the desired Ad Manager network code into your ad tag. Learn more about User messages and Multiple Customer Management (MCM).

See below for further information on how this setting works for your sites. We encourage you to evaluate whether this control aligns with your data processing requirements and to verify that your consent messages are displaying correctly.

Site’s CMP status What happens when maximize message coverage is enabled
Site is successfully collecting end user consent decisions via Google CMP or a third-party certified CMP. No fallback message will be served since consent is successfully collected.
Site is not successfully collecting end user consent decisions via Google CMP or a third-party certified CMP, for example, due to a bug or transient error with the CMP. As a result, there is no TCF CMP detected on the page when the GPT tag is loaded. Google CMP will attempt to serve a fallback message from the GPT tag if the end user is in the EEA, UK, or Switzerland.
Site is not successfully collecting end user consent decisions because no CMP has been implemented on the site or because the CMP used is not integrated with the TCF. As a result, there is no TCF CMP detected on the page when the GPT tag is loaded. Google CMP will attempt to serve a fallback message from the GPT tag if the end user is in the EEA, UK, or Switzerland.

Automated message creation for new sites and apps

Also, when the maximize message coverage control is enabled, the Google CMP will automatically create a published message for every new site and app in your account. This message will use default styles and contain two buttons ("Manage Options" and "Consent"). You can customize or unpublish this message at any time in Privacy & messaging.

On apps, to successfully display these automatically created messages, you're required to implement the User Messaging Platform (UMP) SDK. Otherwise, the fallback consent solution under the maximize message coverage control will attempt to serve a consent message. Note these considerations when using fallback consent collection.

For sites, note that if you manage sites in both Ad Manager and AdSense, new messages will be created in Ad Manager by default. Learn more about how messages work for sites in Ad Manager & AdSense.

Note for both sites and apps: You are responsible for adding a consent revocation link to your sites and apps and ensuring the consent banner works for your intended purposes.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
17830444853759140624
true
Search Help Center
false
true
true
true
true
true
148
false
false
false
false
false