> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/integrations/google/google-limited-ads-2.0-web.md).

# Google Limited Ads 2.0 (web)

In April 2025, Google replaced Limited ads and Technical ad delivery with an updated serving mode : **Limited ads 2.0**. This update, according to Google, was designed to simplify their ad serving offerings and provide publishers with more feature-rich ad serving options across low data-processing purpose availability.  In this article, we will cover how to configure a consent notice integrated with the IAB TCF.

* [Google Limited Ads 2.0 overview](#google-limited-a-ds-2.0-overview)
* [IAB TCF requirements for Google Limited Ads 2.0](#iab-tcf-requirements-for-google-limited-a-ds-2.0)
* [Prerequisites](#prerequisites)
* [Configure consent notice (IAB TCF) for Google Limited Ads 2.0](#configure-consent-notice-iab-tcf-for-google-limited-a-ds-2.0)

***

### Google Limited Ads 2.0 overview

Google Limited Ads is designed to allow publishers to serve ads in a restricted manner when end-user consent is not obtained for the use of cookies or other local identifiers (as defined by IAB TCF Purpose 1: "Store and/or access information on a device").

Under the IAB TCF framework, serving standard Non-Personalized Ads (NPA) often still requires consent for Purpose 1 (for uses like frequency capping, aggregated reporting, fraud prevention). Limited Ads provide a fallback mechanism to monetize traffic when this consent is absent by relying on other TCF signals.

**Some key characteristics of Google Limited Ads are:**

* **No Cookies/Local Identifiers**: Designed to function without accessing or using cookies or local device identifiers for ad targeting or measurement purposes governed by Purpose 1 consent.
* **Restricted Functionality**: Features like frequency capping, audience targeting, conversion tracking metrics reliant on local identifiers, and certain reporting metrics (e.g., unique reach) are unavailable.

### IAB TCF requirements for Google Limited Ads 2.0

In order for Google to attempt the serving of Limited Ads via the TCF signal, the following conditions must be met by the Transparency and Consent (TC) string generated by any CMP for an end-user:

<table data-header-hidden><thead><tr><th width="265"></th><th></th></tr></thead><tbody><tr><td><strong>No consent for Purpose 1</strong></td><td>The end-user has <strong>not</strong> granted consent for IAB TCF Purpose 1 ("Store and/or access information on a device").</td></tr><tr><td><strong>Transparency for Special Purposes</strong></td><td><p>Consent notice has established that the vendor has declared IAB TCF Special Purposes:</p><ul><li>Special Purpose 1 ("Ensure security, prevent fraud, and debug")</li><li>Special Purpose 2 ("Technically deliver ads or content")</li></ul></td></tr><tr><td><strong>Optional TCF purposes</strong></td><td>IAB TCF Purpose 7 ("Measure advertising performance") utilizes either opt-in (consent) or opt-out (legitimate interest)</td></tr></tbody></table>

### Prerequisites

Before continuing with any configuration please ensure that your organization meets the following criteria:

* Your organization uses Google Advertising Products (Ad Manager, AdSense, Admob) to serve ads to end-users
* Your organization's consent notice is integrated with the IAB TCF and published on your property&#x20;

{% hint style="info" %}
**Important considerations**

In addition to the above prerequisites, we also recommend that your organization review and discuss the following before continuing with your configuration:

* **Legal Consultation:** The choice between relying on opt-in (consent) versus opt-out (legitimate interest) for Purposes 7 for Google (or any vendor) should be discussed with your legal counsel to ensure compliance with GDPR and local regulations.
* **Programmatic Limited Ads:** Your organization may need to enable "Programmatic limited ads" within your Google Ad Manager network settings (**Admin > Global settings > Network settings**) if it's not already enabled.
* **Testing**: After configuration, test scenarios where end-users reject consent for Purpose 1 but accept (or allow via Legitimate Interest) Purpose 7. Observe network requests to confirm if ad requests are being made and potentially filled as Limited Ads (often indicated by specific parameters in the ad request URL, like `&lad=1`).<br>
  {% endhint %}

### Configure consent notice (IAB TCF) for Google Limited Ads 2.0

In order to configure a consent notice for Google Limited Ads 2.0, navigate to your organization's Didomi account and click **Consent notices** from the left-hand panel.

<figure><img src="/files/KzviFdUKSjDLVCzFzqix" alt="" width="563"><figcaption></figcaption></figure>

Navigate to your consent notice integrated with the IAB TCF on the subsequent page and click the **Edit** icon inline with the consent notice name.&#x20;

<figure><img src="/files/hsr6RV5pj5bZdJj9cpyc" alt="" width="563"><figcaption></figcaption></figure>

Ensure the **Regulations** tab and **Regulations** sub-tab are both selected, and click **Edit Vendors & Purposes** inline with your enabled GDPR regulation

<figure><img src="/files/3UU3eLzjtT2LVQYu5zPX" alt="" width="563"><figcaption></figcaption></figure>

Use the provided space to add the **Google Advertising Products** vendor (ID: `google`) to the consent notice.

<figure><img src="/files/TphRc84qmPXL4hZ5i2uH" alt="" width="563"><figcaption></figcaption></figure>

By default, the Google Advertising Products vendor will be configured with the following:

<table data-header-hidden><thead><tr><th width="197"></th><th></th></tr></thead><tbody><tr><td>Purposes </td><td><p><strong>Opt-in (based on consent)</strong></p><ul><li>Purpose 1: Store and/or access information on a device</li><li>Purpose 3: Create profiles for personalized advertising</li><li>Purpose 4: Use profiles to select personalized advertising</li></ul><p><strong>Opt-out (based on legitimate interest)</strong></p><ul><li>Purpose 2: Use limited data to select advertising</li><li>Purpose 7: Measure advertising performance</li><li>Purpose 9: Understand audiences through statistics or combinations of data from different sources</li><li>Purpose 10: Develop and improve services</li></ul></td></tr><tr><td>Special Purposes</td><td><ul><li>Special Purpose 1: Ensure security, prevent fraud, and debug</li><li>Special Purpose 2: Technically deliver ads or content</li><li>Special Purpose 3: Save and communicate privacy choices</li></ul></td></tr></tbody></table>

<details>

<summary>Remove legitimate interest and utilize consent for IAB TCF Purpose 7</summary>

{% hint style="warning" %}
**Note**: Please confer with your organization's legal counsel before adjusting the legal basis used for any vendor or purpose.
{% endhint %}

By default, the Google Advertising Products vendor utilizes legitimate interest as a legal basis for IAB TCF Purpose 2, 7, 9, and 10. If your organization chooses to not leverage legitimate interest as a legal basis and instead utilize consent for one or more IAB TCF purposes then you will need to configure IAB TCF publisher restrictions.

In this section, we will cover how to utilize consent for IAB TCF Purpose 7 "Measure advertising performance" instead of the default legitimate interest as a legal basis.

{% hint style="info" %}
While IAB TCF Purpose 2, 7, 9, and 10 have been declared to have flexible legal bases (i.e. your organization can choose to use either legitimate interest or consent as the legal basis), in the scope of configuring Google Limited Ads only IAB TCF Purpose 7 has an impact on functionality.
{% endhint %}

From the GDPR regulation configuration page of the consent notice, navigate to the **TCF settings** section and click **Add restriction** inline with *IAB TCF Publisher Restrictions*.&#x20;

<figure><img src="/files/GB8B265O9hv08rTTNJzO" alt="" width="563"><figcaption></figcaption></figure>

In the subsequent modal, use the provided field to select **Measure advertising performance** and select whether this restriction will be applied to **all IAB vendors** or to just **Google Advertising Products**.

<figure><img src="/files/ev7lsu16XyZwa1JKqjJg" alt="" width="375"><figcaption></figcaption></figure>

Enable the toggle for **Require consent for selected vendors** and click **Save** when finished.

<figure><img src="/files/UJcdXcDlGZjKRssfNacS" alt="" width="375"><figcaption></figcaption></figure>

</details>

Click **Save** when finished.

<figure><img src="/files/y7lGwMMOvSMQJOaqtoH3" alt="" width="563"><figcaption></figcaption></figure>

If the consent notice utilizes legitimate interest as a legal basis then your organization should decide how purposes that utilize legitimate interest behave when an end-user selects a one-click action like *Disagree and close*, *Continue without agreeing*, and *Disagree to all*.

{% hint style="info" %}
If your organization has [removed legitimate interest and utilize consent only](#remove-legitimate-interest-and-utilize-consent-for-iab-tcf-purpose-7) in the consent notice, the following steps can be skipped.
{% endhint %}

Click the **Regulations** tab and select the **Consent settings** sub-tab from the consent notice configuration page

<figure><img src="/files/PQjsbTBkZdivsAuJZHOs" alt="" width="563"><figcaption></figcaption></figure>

Navigate to the **Legitimate interest (Opt-out)** section on the subsequent page and enable the toggles according to your organization's business rules.&#x20;

Click **Save & continue** when finished.

<figure><img src="/files/nBlJY5GZZsvPmXsvJ4fs" alt="" width="563"><figcaption></figcaption></figure>

With the configuration finished, click the **Publish** tab and click **Publish** to update the consent notice on properties where it is deployed.

<figure><img src="/files/XkKNMbZ97qrrXZ2YRrOQ" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.didomi.io/integrations/google/google-limited-ads-2.0-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.