Glossary/Privacy and identity/Publisher provided ID (PPID)
What is a PPID (publisher provided identifier)?
How a publisher provided identifier works in Google Ad Manager, what it lets you do without third-party cookies, and the rules for creating one.
Written by Samhub with the help of AI·Updated 5 Nov 2026·2 min readA PPID (publisher provided identifier) is an ID a publisher creates for its own readers, usually logged-in users, and sends to its ad server with every ad request. Google Ad Manager uses it for frequency capping, audience segments and, when the publisher allows it, programmatic deals.
How a PPID works
When a reader logs in, the publisher gives that reader a stable, random ID. The ID is set in the ad tag, so every ad request from that reader carries it. The ad server can then recognise the same reader across visits and devices, without a third-party cookie.
What publishers use a PPID for
Frequency capping
Limit how often one reader sees the same ad, even in browsers that block third-party cookies.
Audience segments
Build first-party segments on logged-in readers and target them in direct campaigns.
Programmatic deals
Pass the ID to buyers in private marketplace and programmatic guaranteed deals, so they can value the impression.
16 pages for publishers, with a checklist for data, programmatic and direct sales.
Rules for a PPID
Google requires the PPID to be pseudonymous. It must not contain an email address, a name or any other personal data, so most publishers generate a random string per user and store the link to the account on their own side. The reader’s consent rules still apply, and the ID should be the same every time that reader logs in.
Why a PPID matters now
Signal loss in Safari, Firefox and consent banners means fewer readers carry a usable cookie. A PPID gives the publisher an identifier it owns, which works wherever readers log in. The more readers who log in, the more of your inventory becomes addressable.
Addressability at Stampen Media, using Samhub.
Frequently asked questions
No. A hashed email is derived from the reader’s email address. A PPID is a random ID the publisher creates and must not contain personal data.
In practice, yes. The ID needs to be stable, and a login is the reliable way to recognise the same reader again.
No. You still need a lawful basis to process the reader’s data for advertising, usually consent collected through your CMP.
Related terms
Readers who are signed in to your site or app.
An email turned into a code that cannot be read back.
A shared identifier that can replace third-party cookies.
Google’s ad server and exchange for publishers.
One EU-based platform to collect, unify and enrich your first-party data, installed with one script.
- A walkthrough with your own data
- Built for publishers and media houses
- 30 minutes, no commitment
Turn your audience data into more revenue
Get the Media Monetization Playbook: how media houses turn first-party data into higher CPMs, data deals and direct sales. With checklists for every step.
The Media Monetization PlaybookFREE GUIDE · PDF