From 31 July 2024, partners using Google advertising products will be required to obtain Swiss users’ consent to the use of cookies or other local storage, where legally required; and the collection, sharing and use of personal data for personalization of ads.
To comply with the EU User Consent Policy, partners using our publisher products — Google AdSense, Ad Manager, or AdMob — will be required to use a certified CMP that integrates with the TCF when serving ads to users in Switzerland, in addition to the EEA and the UK.
Beginning January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob will be required to use a Consent Management Platform (CMP) that has been certified by Google and has integrated with the IAB's Transparency and Consent Framework (TCF) when serving ads to users in the European Economic Area or the UK.
Review the following information to understand these new requirements, the timing of these changes, and what publishers can do to prepare.
New IAB TCF requirement
Publishers will need to ensure they are working with a Google-certified CMP when serving ads to users in the European Economic Area (EEA), the UK, or Switzerland. Google-certified CMPs are assessed by Google against Google certification criteria focused on TCF compliance. If publishers using the TCF also work with ad technology providers that are not registered with the TCF, Google supports that today—through our Additional Consent specification—and will continue to do so. Our CMP assessments will check that CMPs supporting our Additional Consent specification can do so correctly. Successful review of a CMP against the Google-certification criteria will make that CMP available in our list of Google-certified CMPs. Google does not check CMPs for full compliance with the TCF or applicable privacy laws.
Additionally, please note the following:
-
Web and app fallback behavior: If a partner does not adopt a Google-certified CMP, only limited ads will be eligible to serve. Traffic from a Google-certified CMP will continue to be eligible for personalized ads, non-personalized ads (NPA), or limited ads.
-
App off-platform versus on-platform: Our consent requirements apply to both on- and off-platform mediation.
-
CTV inventory: Earlier this year, we shared that a certified CMP would also be required for CTV inventory, with enforcement planned for July 2024.
In light of publisher feedback about the challenges of implementing the TCF in a CTV environment, we are granting an enforcement extension until July 2025. Please note that regulatory requirements around privacy and consent frequently develop, so we may need to revisit this extension prior to July 2025 if necessary. As such, we continue to encourage our CTV partners to adopt a certified CMP as soon as they are able.
If you work with an existing CMP that is not included on the following list of Google-certified CMPs, please contact your CMP to understand if they intend to be certified.
Guide to the information in this list
- Certified CMP: The name of the Google-certified CMP.
- TCF CMP ID: The unique identifier assigned to a TCF-validated CMP by the IAB.
- Platform: The environments in which the CMP offers support and in which Google has certified the CMP.
List of Google-certified CMPs
Timeline
- May 2023 and onward: Google has begun the process of certifying CMPs that work with our publishing partners. Google will work with CMPs to certify them against the certification criteria.
- Beginning January 16, 2024: In addition to our EU user consent policy, publishers and developers using Google AdSense, Ad Manager, or AdMob will be required to use a Consent Management Platform (CMP) that has been certified by Google and has integrated with the IAB's Transparency and Consent Framework (TCF) when serving ads to users in the European Economic Area or the UK. We will follow up with more details regarding timing.
Next steps
- Publishers already working with a CMP: To ensure a smooth transition, publishers currently working with a CMP should proactively talk with their provider about the certification process.
- Publishers with their own CMP: Publishers who have their own CMPs can register their interest in completing certification for their CMP. Learn more about CMP certification
- Publishers who need to find a CMP: For publishers seeking a new CMP partner, they can consider the list of Google-certified CMPs above. We will regularly add other CMPs as they become certified.
- Publishers using Google’s Privacy & messaging European regulations messages: We encourage publishers to consider which CMP solution is best for them. To support publishers, the European regulations message available to Ad Manager, AdSense, and AdMob publishers in the Privacy & messaging tab are certified in accordance with the new TCF requirement. Learn more about Privacy & Messaging GDPR support and integration with TCF
- App publishers: In addition to the features above, Google offers app publishers the User Messaging Platform (UMP) SDK. Learn more about adding the Google User Messaging Platform (UMP) SDK to your apps (Ad Manager, AdMob) and creating a European regulations message for apps (Ad Manager, AdMob).
- Publishers of child-directed apps: Regardless of consent signals, Google will not serve personalized ads to users if the publisher has indicated that a child is present, if the content has been labeled by a publisher as child-directed, or if Google has other signals to indicate that a child is present. For apps that comply with the Google Play Families policies, this treatment is automatically applied.
- Publishers that are using the User Messaging Platform (UMP) SDK (Android, iOS) are responsible for tagging an ad request from an app as being from users under the age of consent with the TFUA signal using the UMP SDK to suppress GDPR-related user messages.
- Review the Developers documentation on how to keep or remove the child flag in the UMP SDK (Android, iOS).
- Publishers that are using another Google-certified CMP should work with their CMP provider to understand how to suppress or manage messages for users under age of consent.