Notification

Get personalised optimisation tips, understand your account health and set up completion on the improved 'My AdMob page'.

GDPR overview and guidance

Limited ads

Limited ads (LTD) give publishers the ability to serve ads in a limited way. Limited ads disable the collection, sharing and use of personal data for personalisation of ads. Note the following:

  • Ad-serving technologies (our SDK code) will still be cached or installed as part of the normal operation of users' mobile operating systems, and ad creatives will still be sent to, and in some instances cached on, devices. Data like IP addresses will still be used in the course of basic ad serving. Data like IP addresses will still be used in the course of basic ad serving.
  • Only when programmatic limited ads are turned on, invalid traffic detection-only cookies and local storage will be used to help defend against fraud and abuse. Google does not require publishers to obtain consent for this use case.

If a publisher uses the IAB TCF v2.2 consent framework, we will attempt to serve an eligible limited ad when there is no consent for Purpose 1. Alternatively, a publisher can manually send a signal (see Implementation) and Google will similarly attempt to serve an eligible limited ad regardless of user location.

LTD on apps will only be supported for the IAB TCF v2.2 framework at this time.

Local identifier usage

Limited ads disable all personalisation and features that require use of a local identifier. This means that some features aren't available for limited ads.

Features not available with limited ads

Line items that utilise any of these unavailable features won't be eligible for limited ads:

  • Any ads personalisation
  • Audience targeting
  • Search lift measurement
  • Survey lift measurement
  • Remarketing 
  • Interest-based categories
  • Mobile carrier targeting
  • Bandwidth targeting
  • Features that rely on a local identifier, including:​​​​​
    • Conversion tracking metric
    • In-app conversion tracking
    • Unique reach measurement
    • 'Mute this ad'
    • Sequential creative rotation
    • Video creative rotation and storyboarding
    • Frequency capping
    • Reporting on cookie reach, unique reach or in-app conversions
    • Some invalid traffic detection, depending on your programmatic limited ads settings

Demand eligibility

Limited ads support waterfall mediation in AdMob. Campaigns won't serve in AdMob in the event of a limited ad signal. Programmatic demand and campaigns are only available for limited ads when programmatic limited ads are turned on by the publisher.

Programmatic limited ads

Programmatic bidding is available on inventory eligible for limited ads. A publisher can enable this serving mode to allow for contextual programmatic demand when serving limited ads and enables demand from Google demand, Campaigns, Authorised Buyers and SDK Bidding.

If publishers decide to use this new serving mode, Google will make use of invalid traffic detection-only cookies and local storage on consented and unconsented traffic. Accordingly, programmatic demand will be enabled (and an invalid traffic-only cookie and local storage used) when (1) there is no certified consent management platform (CMP) present, (2) when limited ads are enabled in the ad request or (3) a user has declined consent for Purpose 1 of IAB Europe’s Transparency and Consent Framework (TCF), and the signal for all other lawful bases required for limited ads are present in the TC string.

Where no CMP is present, publishers are reminded that they must still comply with all relevant provisions of the EU user consent policy (including, for example, the obligations to clearly identify each party that may collect, receive or use end users’ personal data and to provide end users with prominent and easily accessible information about that party’s use of end users’ personal data.)

Programmatic limited ads are an optional feature. Publishers are legally responsible for the tools that they use to gather consent, including consent for how they use cookies and local storage in online advertising. Publishers should work with their legal teams to determine for themselves whether to use this feature, taking into account relevant regulations and applicable regulator guidance.

Publishers that do not want to use invalid traffic-only cookies and local storage without user consent should opt out of this feature by turning it off in the AdMob user interface.

Turn off programmatic limited ads

Programmatic limited ads are turned on by default and can be turned off at any time. Complete the following steps to turn off programmatic limited ads:

  1. Sign in to your AdMob account at https://apps.admob.com.
  2. Navigate to Settings and then Account information.
  3. Turn off programmatic limited ads.
If you manage an app in both AdMob and Ad Manager, this setting will turn off programmatic limited ads regardless of the setting in Ad Manager.

Turn on programmatic limited ads

Complete the following steps to turn on programmatic bidding for limited ads if it was previously turned off:

  1. Sign in to your AdMob account at https://apps.admob.com.
  2. Navigate to Settings and then Account information.
  3. Turn on programmatic limited ads.

Creative eligibility

Mediation

For mediation, there is no creative enforcement when non-personalised ads are enabled using Google’s EU user consent tools and that same policy will be extended for LTD creatives served through mediation. Under TCF v2.2, all creatives in general are eligible, but similar to reservations, we check that ad technology providers and other programmatic demand sources don’t violate Google policy and have at least one legal basis for processing data.

Implementation

There are no new user interface controls to implement limited ads. Publishers can indicate whether limited ads treatment should be applied.
  • GMA SDK: Publishers can use the gad_has_consent_for_cookies key in platform shared-storage to enable limited ads on Android and iOS.
For publishers using the IAB TCF v2.2, we will respect the cookie or ID consent signal (Purpose 1) contained in the TC string. Limited ads will be requested when consent for Purpose 1 is missing but legitimate interest or consent has been obtained for Purposes 2, 7, 9 and 10.
For limited ads requests, reporting will be unavailable for in-app conversions. Reporting on impressions for limited ads are available using the Serving restriction dimension.
 

Action required for consent management platforms

Publishers using Privacy & messaging can create and traffic consent messages using the IAB TCF v2.2.

Other IAB TCF v2.2 certified consent management platforms (CMPs) shouldn't need to take any action to support limited ads. The existing TC string contains all of the relevant signals required to select the correct serving mode. If the following conditions are met for Google as an ad technology provider, we'll serve limited ads:

  • No consent for Purpose 1
  • Legitimate interest or consent for Purposes 2, 7, 9 and 10

Custom consent tools will need to ask for cookie consent, and if the user declines, should use the new APIs to signal ID-less ad serving behaviour.

The following ad serving modes will be available for publishers:

Ad serving mode Personalised ads Non-personalised ads Limited ads
Programmatic Non-programmatic
Invalid traffic and fraud protection Supported Supported Supported Not supported
Programmatic demand from Google Supported Supported Supported Not supported
Programmatic demand from third-party buyers Supported Supported Supported Not supported

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu