Siden du har forespurt, er ikke tilgjengelig på språket ditt ennå. Du kan velge et annet språk nederst på siden. Eventuelt kan du bruke den innebygde oversettingsfunksjonen i Google Chrome til å oversette en hvilken som helst nettside til det språket du foretrekker.

Publisher first-party identifiers for web and app (Beta)

We currently support AdSense (web) and Google Ad Manager (web and app) inventory outside of European Economic Area (EEA),  UK, Switzerland, California, and relevant US states.
Soon we will support AdMob inventory.

Publisher first-party IDs are a first-party cookie (on web) or ID (on app) set by Google when third-party cookies or device identifiers are not available. These IDs are scoped to a publisher’s domain or apps, and are not shared with other publishers.

They can be used for interest-based ad personalization, allowing buyers to generate first-party user profiles based on user activity on the publisher's site/apps. These IDs can also be used for frequency capping.

developer documentationTo support publisher first-party ID signals in your OpenRTB integration, refer to the protocol guide.

Publisher first-party ID buyer access

Most publishers share first-party IDs with both Google demand and RTB (Authorized Buyers, Open Bidders, and SDK bidders), potentially giving buyers high coverage access to these identifiers across a wide range of inventory where permitted. 

Interaction of publisher first-party IDs with other identifiers

If a publisher supports both Publisher first-party IDs and PPIDs, and both identifiers are available to be sent in an ad request, only one will be sent. Publisher-first party IDs are not passed when third-party cookies or device identifiers are available.

Learn more about publisher first-party identifiers.

Var dette nyttig for deg?

Hvordan kan vi forbedre den?

Trenger du mer hjelp?

Prøv disse trinnene:

Search
Clear search
Close search
Main menu
14834862699032028973
true
Søk i brukerstøtte
true
true
true
true
true
71030
false
false
false
false