Policies

IAB Transparency and Consent Framework v2.0

IAB Europe has finalised v2.0 of its Transparency and Consent Framework developed with IAB Tech Lab and mutual member companies. Google will be integrating with v2.0. Our launch timing is in line with the IAB’s timeline for switching over fully from TCF v1.1 to v2.0. We'll provide greater detail on our integration approach in the coming months.

What to know before registering

If you're integrating with the IAB TCF v2.0, please review the information below about how Google will interoperate with the IAB TCF v2.0 based on the content of the IAB TCF v2.0’s Transparency & Consent (TC) string. Google may update this information from time to time.

For simplicity, we use the phrase 'Google will work with you via the TCF v2.0' below to encompass several aspects of interoperability via the TCF v2.0, including but not limited to:

  • Bidding on bid requests that Google receives
  • Sending bid requests from publishers using Google to bidders
  • Allowing third-party ad tracking and third-party ad serving to occur

Google Policies

The interoperability guidance below is intended to reflect Google's existing policy requirements, in particular the requirements of Google's EU User Consent Policy and our policies against fingerprinting for identification (for example, those contained in our Requirements for third-party ad serving). Please note that our policies continue to apply and are more restrictive than TCF v2.0 in some cases.

Purposes

For each purpose below, for Google to work with you via the TCF v2.0, the TC string must indicate that consent has been granted by, or legitimate interest has been established with, the user (as applicable).

Store and/or access information on a device (Purpose 1)

If you use cookies, mobile ad identifiers or other local storage, Google will work with you via TCF v2.0 if you're registered for consent for Purpose 1.

In some jurisdictions, for example Germany and Norway, in certain situations, consent for Purpose 1 may not be asked for by the publisher via the CMP and, as long as the TC string appropriately represents this, Google will interoperate in those situations. In line with our EU User Consent Policy, this position is subject to change based on legal developments and evolving regulator guidance.

Select basic ads (Purpose 2)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purpose 2.

Create a personalised ads profile and select personalised ads (Purposes 3 and 4)

Google will work with you via TCF v2.0 if you're registered for ‘consent’ for Purposes 3 and 4, as long as the TC string indicates that the user has granted consent for both those purposes.

Google will also work with you via TCF v2.0 if you're registered for ‘not used’ for these purposes, except for when the user hasn't consented to personalised ads via RTB (see note at the end of this section).

If you're registered for ‘legitimate interest’ for Purposes 3 and/or 4:

  • If the TC string indicates that ad personalisation (Purposes 3 and/or 4) is permitted under legitimate interest, Google will not work with you via TCF v2.0.
  • If the TC string indicates that no ad personalisation is permitted, Google will work with you via TCF v2.0, except for via RTB (see note at the end of this section).

If you're registered for ‘consent or legitimate interest as a legal basis’ for Purposes 3 and/or 4:

  • If there are no publisher restrictions, Google will work with you via TCF v2.0 as long as your default legal basis is consent.
  • If there are publisher restrictions:
    • If the publisher restriction is for you to operate on the basis of consent, Google will work with you via TCF v2.0 in that circumstance.
    • If the publisher restriction is for you to operate on the basis of legitimate interest, Google will not work with you via TCF v2.0 in that circumstance.

Note that, for RTB only, if the TC string indicates that the user hasn't granted consent for Purposes 3 and 4, Google will not pass a bid request to your bidder in those circumstances, irrespective of your registration. This is consistent with our treatment of non-personalised ads for RTB today.

Create a personalised content profile and select personalised content (Purposes 5 and 6)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purposes 5 and/or 6.

Measure ad performance (Purpose 7)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purpose 7.

Measure content performance (Purpose 8)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purpose 8.

Apply market research to generate audience insights (Purpose 9)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purpose 9.

Develop and improve products (Purpose 10)

Google will work with you via TCF v2.0 if you're registered for ‘consent’, ‘legitimate interest’, ‘consent or legitimate interest’ or ‘not used’ for Purpose 10.

Special Purposes

Ensure security, prevent fraud and debug (Special Purpose 1)

Google will work with you via TCF v2.0 if you're registered for ‘legitimate interest’ or ‘not used’ for Special Purpose 1.

Technically deliver ads or content (Special Purpose 2)

Google will work with you via TCF v2.0 if you're registered for ‘legitimate interest’ or ‘not used’ for Special Purpose 2.

Features

Match and combine offline data sources (Feature 1)

Google will work with you via TCF v2.0 if you register for Feature 1, as long as appropriate disclosure has been provided to the user.

Link different devices (Feature 2)

Google will work with you via TCF v2.0 if you register for Feature 2, as long as appropriate disclosure has been provided to the user.

Receive and send automatically sent device characteristics for identification (Feature 3)

Google will work with you via TCF v2.0 if you're registered for Feature 3. However, we remind you that our policies prohibit fingerprinting for identification (e.g. Requirements for third-party ad serving), and we require that you adhere to our policies, which can be more restrictive than the TCF v2.0 in some cases, whenever you work with us.

We actively enforce our policies and we're continuing to invest in technology to detect fingerprinting on our platforms.

Special Features

Use precise geolocation data (Special Feature 1)

Google will work with you via TCF v2.0 if you register for this feature, as long as appropriate disclosure has been provided to the user and users appropriately opt in to Special Feature 1.

Actively scan device characteristics for identification (Special Feature 2)

If the TC string indicates that a user has opted in to this special feature:

  • Google will not work with you via TCF v2.0 if you registered for Special Feature 2.

If the TC string indicates that a user hasn't opted in to this special feature:

  • Google will work with you via TCF v2.0 if you registered for Special Feature 2 (because, when the user hasn't opted in, the TC string itself indicates that processing under this special feature can't take place)

We remind you that our policies prohibit fingerprinting for identification (e.g. Requirements for third-party ad serving), and we require that you adhere to our policies, which can be more restrictive than the TCF v2.0 in some cases, whenever you work with us.

We actively enforce our policies and we're continuing to invest in technology to detect fingerprinting on our platforms.

Macro requirements

The IAB TCF v2.0 requires use of a macro in pixel URLs on creatives to indicate where in the URL the TC string should be inserted and sent onwards, as well as to identify which vendors are present. Consistent with TCF v2.0 requirements, Google requires this macro to be present. Please ensure advertisers that you work with include this macro properly, as ad serving may be interrupted if it isn't present.

If you have questions about Google’s IAB TCF v2.0 integration, please contact us via this form.

For any help or support with TCF v2.0 registration in general, independent of Google’s integration, please email IAB Europe at framework@iabeurope.eu.

FAQs

Scope

Which Google ads products are integrating with the IAB TCF v2.0?

Integration with the IAB TCF v2.0 will apply to third-party inventory (not Google owned and operated inventory). We obtain consent for Google owned and operated inventory through our own consent flows.

Products that will be integrated with the IAB TCF v2.0:

  • Google Ad Manager
  • AdSense
  • AdMob
  • Google Analytics (for advertising features used in conjunction with Google ads products)
  • Google Display Ads (for integrated properties)
  • Display & Video 360 and Campaign Manager (for integrated properties)
  • Google Authorised Buyers
  • Funding Choices

Timing

What is Google’s GVL ID and when this will be visible in the TCF framework?

Google’s GVL ID is 755. Google has been officially listed in the IAB’s GVL since 23 July 2020.
Although Google is listed in the GVL, we will not begin reading and passing TC strings until our integration launches. We plan to start ramping up TCF serving two weeks before our full integration launch date, which is targeted for 15 August 2020

Integration requirements

What are Google registration requirements?

There are two things to distinguish:
  1. Google registration as a vendor. Please see the IAB TCF GVL registry (.JSON file) for Google’s registration as a vendor. 
  2. Google’s requirements for vendors and publishers to work with Google. Please refer to Google’s Interoperability guidance for vendors

Can publishers using the IAB TCF v2.0 continue to work with vendors that are not registered on the GVL after Google’s integration is complete?

We will continue to support ad technology providers that are certified on our platforms but not registered on the GVL through 'Additional Consent', which is a technical spec that CMPs can implement to add Google’s ad technology providers (ATPs) to consent messages.
CMPs must implement this spec for publishers to continue working with vendors on Google’s ATP list that are not on the IAB GVL.

Why does a publisher need to obtain consent for both Purpose 3 (Create a personalised ads profile) and Purpose 4 (select personalised ads) to serve personalised ads? What if a publisher wants to personalise ads for that user, but not build personalised profiles for them?

Based on our interpretation of the GDPR and ePrivacy Directive requirements, various guidance from the Article 29 Working Party and our own dialogue with DPAs, we have come to the settled conclusion about the appropriate lawful basis. Further details on the nature and scope of processing including the applicable legal basis are also described in the Privacy Policy.
Google has not changed its consent requirements in relation to the TCF. Google customers (e.g. publishers and advertisers) using Google ad platform products must comply with Google’s EU user consent policy.
Without consent for Purposes 3 and 4, Google will not be able to offer personalised ads. Specifically, with just consent for Purpose 4 and no consent for Google for Purpose 3, only non-personalised ads will serve. These requirements are in line with our existing Google EU user consent policy which states:
You must obtain end users’ legally valid consent to:
  • the use of cookies or other local storage where legally required [Purpose 1]; and
  • the collection, sharing [Purpose 3] and use [Purpose 4] of personal data for personalisation of ads.
Google Ad Manager publishers can choose in the user interface to enable or disable whether or not user visitation data can be used by Google to help create user interest categories in order to target ads. Disabling these settings does not prevent publishers and RTB buyers from serving personalised ads, although publishers will still need to obtain consent for Purposes 3 and 4.

What would happen if a publisher decides to not integrate the TCF V.2 and send the consent to Google as they are doing right now?

Google is not integrated with TCF v1.0, so Google will continue to ignore v1.0 TC strings as if they were not there. 

Partners are not required to use IAB TCF v2.0. They can continue using other means to comply with our policies. 

  • The ad technology provider controls that we launched across Ad ManagerAdSense and AdMob last year for publishers will continue to function. 
  • When setting up their IAB-compliant CMPs and picking which ad technology providers (ATPs) they want to work with, publishers monetising with Google can select vendors IDs from both IAB’s Global Vendor List and Google's ATP list for any CMPs that implement Additional Consent. If there are vendors that are not available on the IAB GVL but are available in our ad technology provider controls, publishers can continue to work with those ad technology providers.
We will only support ad technology providers that are present in our controls as our certification process is still in place and vendors must be certified to run ads programmatically. Our certification process has always been open. If there are vendors on the IAB Global Vendor List that are not in our ATP controls, they will not serve.

Is AMP integrating with the IAB TCF?

AMP supports popular transparency consent frameworks including the IAB TCF v1.0, TCF v2.0 and the IAB US Privacy String. Please check with your consent management platform (CMP) and ad networks on their AMP support. AMP will read and pass the strings passed by the frameworks (IAB TCF v1.0, TCF v2.0 and the IAB US Privacy String) when received by CMPs/ad networks. Learn more about AMP and consent
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue