Limited ads are a serving mode in Google's publisher products that delivers an advertisement without collecting, sharing or using personal data for personalisation. Google Ad Manager, AdMob and AdSense use the mode when a European visitor has not consented to cookies or other device storage but publishers still want to show something. It exists because European consent rules separate two questions: whether an ad may be shown, and whether data may be stored on a device to show it. Limited ads answer the first with yes and the second, almost entirely, with no.

Where limited ads sit among Google's serving modes

Google runs publisher inventory in three main modes. Personalised ads draw on a profile built from past behaviour. Non-personalised ads do not use behaviour for targeting, but still rely on cookies or mobile identifiers for frequency capping and aggregated reporting, according to Google's ad serving modes documentation. Limited ads go one step further and switch off "all personalization and features that require use of a local identifier", according to the Ad Manager help page on limited ads.

The difference maps onto the purposes defined in IAB Europe's Transparency and Consent Framework (TCF). Personalised ads need consent for Purpose 1 (store or access information on a device), Purpose 3 (create a personalised ads profile) and Purpose 4 (select personalised ads). Non-personalised ads need Purpose 1 consent. Limited ads need neither. They require only that transparency has been established for Special Purpose 1 (security, fraud prevention and debugging), Special Purpose 2 (delivering and presenting ads) and for Google itself, registered as vendor 755. Purpose 7, measuring ad performance, is optional, though without it some click tracking is disabled. The user's choices travel in the TC String, the encoded consent record a consent management platform (CMP) writes and every downstream vendor reads.

How a limited ad request works

A request reaches the limited path in one of three ways. The first is automatic: Google reads the TC String and finds Purpose 1 refused while the special purposes and the Google vendor signal are present. The second is geographic: requests from the European Economic Area (EEA), the United Kingdom or Switzerland that lack a TC String from a Google-certified CMP. The third is manual, and works wherever the user is.

The manual flag differs by product. Video publishers using the Interactive Media Ads (IMA) SDK append ltd=1 to the ad tag URL. App developers using the Google Mobile Ads SDK set the gad_has_consent_for_cookies key in the platform's shared storage. On the web, the Google Publisher Tag (GPT) exposes a limitedAds property in its privacy settings, but per-request control works only when GPT is loaded from what Google calls the limited ads URL. Google's published sample loads the library from pagead2.googlesyndication.com and toggles the mode with setPrivacySettings({limitedAds: true}). Loaded from the standard URL, those calls are ignored. The limited version delays some operations until the first display() call, a performance cost Google acknowledges.

Once a request is flagged, the ad server still does most of its usual work. Scripts and SDK code are cached, creatives are delivered and IP addresses are used to transmit the ad. What disappears is audience targeting, remarketing, conversion tracking, unique reach measurement, lift studies, sequential creative rotation and frequency capping, the last now in closed beta for in-stream video reservations. Line items that depend on these features never enter the auction.

Who can buy it

On the sell side, the publisher's ad server operations team decides how much demand competes. Directly sold reservations, guaranteed and non-guaranteed, are eligible on web, app and video, as is mediation. Programmatic demand is eligible only when a network-level setting called programmatic limited ads is on. It is on by default. With it on, contextual demand can come from Google's own buyers, Authorized Buyers, Open Bidding and SDK Bidding.

On the buy side, a bidder in Authorized Buyers or Open Bidding qualifies for a limited request only if it is registered for at least one purpose or special purpose with consent or legitimate interest as its legal basis, and the user has granted one of them, according to Google's Authorized Buyers documentation. The TC String reaches them in the OpenRTB field User.ext.consent. In practice a buyer bids on page context and coarse location, with no user identifier, no cookie match and, for AdSense, only a truncated IP address. AdSense's full IP address sharing option excludes limited requests.

Fraud detection is the awkward part. With programmatic limited ads on, Google sets cookies and local storage used only for invalid traffic (IVT) detection, and states that it does not require publisher consent for this. With the setting off, Google warns that fraud detection "may be reduced". Reporting isolates limited impressions; forecasting does not.

Origin and evolution

The mode was born out of a gap. When Google integrated its ad systems with TCF v2.0 on 15 August 2020, its own guidance said Ad Manager had no "cookieless capabilities" for users who refused Purpose 1, and that such requests would be dropped. The same document promised a "limited ad serving solution" for reservations only, with programmatic support under evaluation. Publishers without proper consent faced no Google monetisation in Europe after a 90-day grace period.

The first version drew criticism before it shipped. In October 2020 Eric Lo, an Ad Manager product manager, told Digiday that "our limited ads offering doesn't rely on cookies or mobile identifiers, but does utilize data like IP addresses." Publishers and vendors in the same report objected to Google deciding whether an ad loads at all. "This is the role of the publisher," said Fabien Scolan, vice-president of advertising at Leboncoin Group. By January 2021 the mode was available to all Ad Manager publishers for reservations and mediation only, according to MonetizeMore.

The decisive change came at the end of 2023. On 9 December 2023 PPC Land reported that Google would open limited ads inventory to programmatic bidding in the first quarter of 2024, with IVT-only cookies set regardless of consent and an opt-out for publishers. It coincided with Google's requirement that publishers serving personalised ads in the EEA and UK use a certified CMP from 16 January 2024, extended to Switzerland on 31 July 2024, according to Google's consent management requirements. Traffic without a certified CMP "may be eligible for non-personalized ads or limited ads", in Google's wording. AdSense for Search partners got an IVT-only cookie parameter as a stopgap.

Why it matters

For publishers, limited ads are a revenue floor rather than a revenue source. It keeps unconsented European traffic monetisable at prices Google does not publish. PPC Land cited platform data, without a named study, showing personalised ads earning 50% to 70% more than non-personalised ones, and limited ads strip out more signal still.

The mode also functions as Google's penalty box for consent errors. When Google announced on 3 November 2025 that TCF v2.3 would be mandatory, it warned that publishers who missed the deadline risked ad requests defaulting to limited ads. From 1 March 2026, validation errors in categories 2 and 5, and the new code 1.4 for a missing or Google-less disclosed vendors segment, sent requests to limited ads or dropped them. For advertisers, a share of European inventory is therefore contextual whether they planned for it or not.

Limitations and disputes

Three criticisms recur. The first concerns control. Google decides which requests become limited, and since 2020 critics have argued that serving a non-targeted ad should not depend on consent signals at all.

The second is measurement. Without frequency caps, conversion tracking or reach metrics, advertisers cannot see what they bought in their usual terms. The third concerns the IVT cookies. Google's position that they need no publisher consent rests on its own reading of security processing; the ePrivacy Directive's consent rule for device storage has narrow exemptions, and Google's help page does not cite a regulator's view.

Dates also conflict. PPC Land's TCF v2.3 coverage puts the programmatic opening in December 2023; the original report said the first quarter of 2024. The v2.3 deadline appears as both 28 February and 1 March 2026.

Limited ads versus adjacent terms

Non-personalised ads still use cookies or device identifiers for frequency capping and reporting, and still need Purpose 1 consent. Limited ads do not. Ad personalisation covers the full spectrum.

Limited ad serving is an advertiser policy, not a privacy mode. Google introduced it in November 2023 to cap impressions from advertisers it considers unqualified, extended it to YouTube from September 2024 and announced a phased rollout on Search from June 2026 through 2028. Google's AdMob help centre puts it plainly: one "limits the number of ads served", the other "limits what data can be used to serve ads".

Limited statuses in Google Ads and Merchant Center mean an approved item runs only in some situations. Google's ad status page defines "Eligible (limited)" as an ad that "can run, but not in all situations because of policy restrictions", such as trademark use. A "Limited" product in Merchant Center shows in some countries or surfaces but not others, short of a full product disapproval.

Recent developments

The mode's reach is growing as consent infrastructure gets stricter. On 18 June 2026 PPC Land reported that Google would begin using IP addresses for measurement and personalisation in the EEA, UK and Switzerland from 3 August 2026, adding TCF Feature 3 to its registration, and warned that strings failing to disclose it could face processing limits. Coverage in September 2026 of AdSense fallback banners again described invalid consent strings pushing requests into lower-yielding inventory. The next test arrives on 23 October 2026, when CMPs on the web must move to TCF v2.4.

Timeline

  • 15 August 2020: Google completes its TCF v2.0 integration; requests without Purpose 1 consent are dropped and a "limited ad serving solution" is promised for reservations.
  • 2 October 2020: Google's Eric Lo says limited ads will use IP addresses but not cookies or mobile identifiers.
  • January 2021: Limited ads available to all Ad Manager publishers for reservations and mediation, according to MonetizeMore.
  • 2 November 2023: Google introduces the separate limited ad serving policy for advertisers.
  • 9 December 2023: Google announces programmatic demand for limited ads, slated for the first quarter of 2024.
  • 16 January 2024: Certified CMP required for personalised ads in the EEA and UK.
  • 1 February 2024: Phased consent enforcement begins for AdSense for Search partners.
  • 31 July 2024: Certified CMP requirement extends to Switzerland.
  • 13 August 2024: Limited ad serving policy extended to YouTube, enforced from September 2024.
  • 16 May 2025: Google removes the non-personalised ads control from AdSense's European message settings.
  • 3 November 2025: Google mandates TCF v2.3, with limited ads as the fallback for non-compliance.
  • 1 March 2026: TCF v2.3 validation begins; error code 1.4 introduced.
  • 1 June 2026: AdSense full IP sharing launches, excluding limited ads requests.
  • 12 June 2026: Limited ad serving policy update announces a phased rollout on Google Search through 2028.
  • 3 August 2026: Google begins IP-based measurement and personalisation in the EEA, UK and Switzerland.
  • 23 October 2026: TCF v2.4 deadline for web CMPs.

Summary

Who: Google operates limited ads across Ad Manager, AdMob and AdSense. Publishers choose whether programmatic demand competes; Authorized Buyers, Open Bidding and SDK bidders with a TCF legal basis can bid; CMPs supply the signal that triggers the mode.

What: A serving mode that delivers ads without personalisation or local identifiers, keeping only IVT-specific storage, when a user has refused device storage or no valid consent signal exists.

When: Promised in August 2020, available to Ad Manager reservations by early 2021, opened to programmatic demand from early 2024, and used as the fallback for TCF v2.3 errors since 1 March 2026.

Where: Mainly the EEA, UK and Switzerland, where TCF consent governs Google's serving, though publishers can trigger it manually anywhere.

Why: To keep unconsented European traffic monetisable without storing data on devices, at the cost of targeting, frequency capping, measurement and, critics say, publisher control over when an ad may load.