Privacy & consent

Personalized, non-personalized and limited ads: the three AdSense serving modes compared

Last updated Published By the editorial team6 min5 sources

Key takeaways

  • AdSense has three serving modes for consent-sensitive traffic: personalized ads, non-personalized ads (NPA) and limited ads.
  • Under the IAB TCF, personalized ads need consent for Purposes 1, 3 and 4; non-personalized ads need consent for Purpose 1 only; limited ads need neither, only transparency for Special Purposes 1 and 2 and Google as a vendor.
  • Non-personalized ads still use cookies or mobile identifiers for frequency capping, aggregated reporting and fraud prevention, so they still need cookie consent where the law requires it.
  • Limited ads disable personalization and features that need a local identifier, such as frequency capping, but still use the IP address to deliver the ad.
  • Limited ads are on by default in AdSense and can be turned off under Brand Safety, then Blocking controls, then Ad serving.
A balance scale
Image: Balance scale IMGP9755,Nikodem Nijaki,CC BY-SA 3.0,via Wikimedia Commons.

AdSense serves one of three ad types depending on the consent signals attached to a request: personalized ads, non-personalized ads (NPA), or limited ads. Personalized ads need consent for device storage and for profiling. Non-personalized ads need consent for device storage only. Limited ads need neither, but still require transparency about security and ad delivery. Each step down removes data uses and usually lowers revenue.

This guide compares the three modes using Google’s help center as of November 2026. It explains Google’s product behavior, not what the law demands of your site, and is not legal advice.

What is the difference between the three modes?

Personalized ads Non-personalized ads Limited ads
Targeting Past behavior, interests, demographics, remarketing Context: page content, coarse location from the current request Context only
Cookies or local storage Yes Yes, for frequency capping, aggregated reporting, fraud Only invalid-traffic-only cookies, and only if programmatic limited ads are on
Frequency capping Yes Yes No
IP address used Yes Yes Yes, to deliver the ad
Programmatic demand Google and third-party buyers Google and third-party buyers, with user identifiers removed Google demand and Authorized Buyers, contextual only
TCF consent needed for Google P1, P3, P4 consent plus P2, P7, P9, P10 P1 consent plus P2, P7, P9, P10 None; transparency for SP1, SP2 and Google as vendor

Google defines non-personalized ads, in its RTB article, as ads “not based on a user’s past behavior”, targeted with contextual information “including coarse geo-targeting based on current location and content on the current site or app”, and it disallows “all interest-based audience targeting, including demographic targeting”.

Limited ads go further. According to Google’s limited ads article, they “disable the collection, sharing, and use of personal data for personalization of ads”. The EU user consent policy help page adds that Google also “disables features that require use of a local identifier like frequency capping”.

How does AdSense choose the mode for each visitor?

In the EEA, the UK and Switzerland, the choice comes from the TC string your CMP writes. Google’s TCF integration article and the limited ads article give this decision table:

Region and signal What the user chose Mode Google attempts
EEA/UK/CH, certified CMP Consent to Google for P1, P3, P4, plus consent or legitimate interest for P2, P7, P9, P10 Personalized
EEA/UK/CH, certified CMP P1 consent, no P3/P4 consent Non-personalized
EEA/UK/CH, certified CMP No P1 consent, but transparency for SP1, SP2 and Google Limited (if enabled)
EEA/UK/CH, certified CMP Google refused as a vendor Reported as error 1.1 (Google not allowed)
EEA/UK/CH, non-certified CMP Any Non-personalized at best (error 9.1)
EEA/UK/CH, no TC string None Limited (if enabled), error 10.1
Elsewhere, no flags Not asked Personalized, unless another regulation or flag applies

Two details matter for configuration. Google is registered flexibly for Purposes 2, 7, 9 and 10, defaulting to legitimate interest, but is “not flexibly registered for purposes 1, 3, and 4 and always requires consent”. And legitimate interest for Purpose 7 is optional for limited ads, but without it “some click tracking and measurement functionality used by Google Demand will be disabled”.

The TCF guide explains these purposes in detail.

What do non-personalized ads still collect?

Many publishers assume NPA means “no cookies”. Google says otherwise. The EU user consent policy help page states that cookies or mobile identifiers support personalized and non-personalized ads “for frequency capping, and for aggregated ad reporting”, and that “the non-personalized ads that we serve on websites still require cookies to operate”.

That is why NPA alone does not answer the consent question in Europe. The ePrivacy rules on device storage apply whether or not the ad is personalized. NPA solves the profiling question, not the storage one.

When Google sends NPA requests to third-party RTB bidders, its RTB article says identifiers such as google_user_id, hosted_match_data, device advertising IDs and session_id are removed, while signals like the user agent and truncated IP address are still sent.

What do limited ads still use?

Google lists what remains active in limited ads:

  • Ad-serving JavaScript is still cached by the browser, and creatives are still sent to, and sometimes cached on, the device.
  • IP addresses “will still be used to facilitate the transmission of the ad to the device”.
  • Only when programmatic limited ads are on, invalid-traffic-only cookies and local storage are used against fraud. Google states it “does not require publishers to obtain consent for this use case”, but also that publishers “are legally responsible for the tools they use to gather consent”.

The limited ads article still mentions the Shared Storage API for invalid traffic detection. Chrome announced in October 2025 that it is retiring Shared Storage along with other Privacy Sandbox APIs, so treat that sentence as possibly outdated.

How do I force a mode in the ad code?

Google’s ads personalization settings article documents tag-level switches. They are per request and stateless: if you stop setting them, the next request reverts to the default.

Goal AdSense code Request parameter
Request non-personalized ads (adsbygoogle=window.adsbygoogle||[]).requestNonPersonalizedAds=1 npa=1
Disable personalization via privacy treatment (adsbygoogle=window.adsbygoogle||[]).push({params: {google_privacy_treatments: 'disablePersonalization'}}) ppt=1
Same, on the script tag data-privacy-treatments="disablePersonalization" ppt=1
Delay ad requests until consent is known pauseAdRequests=1, then =0 none

Set the flag before the first adsbygoogle.push() on the page. When a TC string is also present, Google applies “the most conservative” of the signals, so the flag can only reduce personalization, never override a refusal.

The pause switch is useful with non-TCF consent flows: hold requests, wait for your banner, then resume with or without the NPA flag. With a TCF CMP, you do not need it: the AdSense tag reads the TC string automatically.

Where are the account settings?

  1. Limited ads switch: “Brand Safety”, then “Blocking controls”, then “Ad serving”, then “Limited ads”. It is on by default.
  2. European regulations settings: “Privacy & messaging”, then “European regulations”, then “Settings”. Google’s RTB article notes you can set the account to serve non-personalized ads to EEA, UK and Swiss requests there, and choose which ad partners receive those requests.
  3. US state regulations settings: the equivalent card for US states, where restricted data processing is configured. See the US state privacy laws guide.

Which mode should I aim for?

The practical goal is not to pick a mode but to make sure each visitor gets the best mode their choices allow:

  • Consenting users should get personalized ads. If they do not, look for TCF errors in the Policy center (1.1, 1.4, 9.1).
  • Users who refuse personalization should get NPA. That requires a CMP that separates Purpose 1 from Purposes 3 and 4.
  • Users who refuse everything get limited ads if the switch is on, otherwise nothing.

If your reports show many limited-ad requests from consenting regions, your CMP is probably not sending a valid signal: start with the certified CMP checklist.

Common mistakes

  • Adding npa=1 globally and calling it compliance. It still sets cookies and does not replace a CMP.
  • Turning off limited ads without checking traffic. Refusals and missing signals then become unfilled impressions.
  • Setting the NPA flag after adsbygoogle.push(). The request is already sent.
  • Assuming limited ads use no data. The IP address is still used for delivery.
  • Misreading Google’s mixed guidance on Purpose 1. Google’s TCF article says “you should not call Google’s ad tag” without Purpose 1 consent, yet its own table says limited ads “can serve” in that case. With a certified CMP and limited ads on, the tag reads the TC string and picks the mode itself; if you turned limited ads off, not calling the tag after a refusal is the cleaner option.
  • Expecting cookie blocking to stop personalization. Browsers increasingly restrict third-party cookies; see third-party cookies and AdSense.

Frequently asked questions

Do non-personalized ads remove the need for a cookie banner?

No. Google states that non-personalized ads still use cookies or mobile identifiers for frequency capping, aggregated ad reporting and fighting fraud and abuse. Its EU user consent policy therefore requires consent for those cookies wherever the law requires cookie consent, which is the case in the EEA and the UK for advertising cookies.

Should I turn off limited ads?

Turning them off means EEA, UK and Swiss visitors who refuse device storage, or arrive without a valid TCF signal, may see no ads at all. Google lets you disable them because limited ads with programmatic demand use invalid-traffic-only cookies without consent. Whether that is acceptable under your local law is a decision for you and your legal adviser.

Is the npa=1 flag enough to comply with the GDPR?

It only changes the serving mode for one request. Google's TCF article says that if you send both a non-personalized flag and a TC string, it applies the most conservative signal. You still need a valid consent mechanism, and for EEA, UK and Swiss traffic Google expects a certified TCF CMP.

Why do non-personalized and limited ads earn less?

They cannot use interest, demographic or remarketing signals, so fewer advertisers compete for the impression. Limited ads also lose frequency capping and parts of measurement. Google does not publish a standard revenue gap, so compare RPM by country in your own reports before and after consent changes.

Sources

  1. Limited ads · Google AdSense Help
  2. Ads personalization settings in Google's publisher ad tags · Google AdSense Help
  3. Publisher integration with the IAB Europe TCF · Google AdSense Help
  4. Send non-personalized ad requests to third-party RTB buyers · Google AdSense Help
  5. Help with the EU user consent policy · Google