Tracking & DataFirst-Party Cookie
What is a First-Party Cookie? How It Differs from Third-Party
Also known as: first party cookie, third-party cookie
Short answer
A first-party cookie is a small record stored by the website you are actually visiting. Because it comes from that site, browsers block it far less often than a third-party cookie set by another domain.
Side by side
| First-party | Third-party | |
|---|---|---|
| Written by | The domain in the address bar | Another domain on that page |
| Blocked by browsers | Rarely | Often, and increasingly |
| Lifetime | Longer | Frequently shortened |
| Used for | Remembering Click IDs and visits | Cross-site tracking |
What to watch
- Store the Click ID in first-party storage from the very first visit.
- Never rely on third-party cookies to link a click to a sale.
- On sites spanning several domains, make sure the marker travels between them, because first-party storage is separate per domain.
Frequently asked questions
- How does it differ from a third-party cookie?
- A first-party cookie is written by the domain in the address bar. A third-party cookie is written by another domain loaded on the page. Modern browsers block the second broadly, which is why ad tracking moved to server-side paths.
- Why store the Click ID as first-party?
- Because first-party storage lasts longer and is blocked less often. A Click ID stored there is still present when the purchase happens days later.
- Are cookies still needed when I send from the server?
- Yes, to remember the Click ID and earlier visits while the visitor stays on the same device. Server-side sending reports the conversion; first-party storage remembers where it came from.
Related terms
Konektor guides
Your ad numbers are only as accurate as the data behind them
Konektor captures the Click ID and sends conversions that close on WhatsApp, over the phone, or in a shop back to the ad platform.