Glossary/Privacy and identity/First-party cookies
What are first-party cookies and how are they used?
How first-party cookies differ from third-party cookies, what publishers use them for, and when consent is needed.
Written by Samhub with the help of AI·Updated 13 Oct 2026·3 min readFirst-party cookies are small files set by the website the reader is visiting, under that site’s own domain. They remember logins, settings and visits.
First-party vs third-party cookies
| First-party | Third-party | |
|---|---|---|
| Set by | The site you visit | Another domain, such as an ad vendor |
| Works across sites | No | Yes |
| Browser support | Supported everywhere | Blocked in Safari and Firefox |
What publishers use them for
Logins
Keep readers signed in.
Analytics
Count returning readers.
Audiences
Recognize readers to build first-party segments.
16 pages for publishers, with a checklist for data, programmatic and direct sales.
Consent still applies
Addressability at Stampen Media after moving its reader data into one layer with Samhub.
Frequently asked questions
No. Browsers block third-party cookies, not first-party ones.
Yes, unless they are strictly necessary for the service.
Some browsers shorten cookies set by scripts, so server-set cookies last longer.
Yes, to build your own audiences, with consent.
Related terms
Cookies set by another domain than the site you visit.
Data you collect directly from your own readers.
Collecting data through your own server instead of the browser.
Collects and stores readers’ consent choices.
Google’s project to replace third-party cookies.
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.
