Policies

Personalized and non-personalized ads

EU user consent controls in AdMob provide several options for enabling personalized and non-personalized ads (enabled via the Google Mobile Ads SDK). This article details the differences between these two types of ads. Learn more about ads personalization settings in Google's publisher ad tags

Personalized ads

Personalized advertising (formerly known as interest-based advertising) is a powerful tool that improves advertising relevance for users and increases ROI for advertisers. In all our publisher products, we make inferences about a user’s interests based on the sites they visit or the apps they. This allows advertisers to target their campaigns according to these interests, providing an improved experience for users and advertisers alike. Learn more about our advertiser policies for personalized ads.

Google considers ads to be personalized when they are based on previously collected or historical data to determine or influence ad selection, including a user's previous search queries, activity, visits to sites or apps, demographic information, or location. Specifically, this would include, for example: demographic targeting, interest category targeting, remarketing, targeting Customer Match lists, and targeting audience lists uploaded in DoubleClick Bid Manager or Campaign Manager.

Non-personalized ads (NPA)

Non-personalized ads are ads that are not based on a user’s past behavior. They are targeted using contextual information, including coarse (such as city-level) geo-targeting based on current location, and content on the current site or app or current query terms. Google disallows all personalized targeting, including demographic targeting and user list targeting. 

Although non-personalized ads don’t use cookies or mobile ad identifiers for ad targeting, they do still use cookies or mobile ad identifiers for frequency capping, aggregated ad reporting, and to combat fraud and abuse. Therefore, you must obtain consent to use cookies or mobile ad identifiers for those purposes where legally required, per the ePrivacy Directive in certain EEA countries. 

Was this article helpful?
How can we improve it?