# First-Party Data

> Data a business collects directly from its own audience on its own domain — via first-party cookies, logins, and submitted details — in a privacy-compliant way, without relying on third-party cookies.

# First-Party Data

First-party data is information a business collects directly from its own audience, on its own domain — through first-party cookies, account logins, and details people submit. Because it is gathered first-hand rather than bought from or shared by another company, it stays accurate and privacy-compliant (GDPR, CCPA) and does not depend on third-party cookies, which browsers increasingly block.

## First-Party Data vs Customer Data

- [Customer Data](/glossary/customer-data) — first-party data is the broad category of everything you collect first-hand, including anonymous signals; Customer Data is the personal-information subset (email, phone, name) AnyTrack hashes and forwards to ad platforms.

## First-Party Data in AnyTrack

AnyTrack is built on first-party data. It sets its identifiers as **first-party cookies on your own domain** — `_atcid` (an anonymous visitor ID, two-year TTL), `_atcid-pt` (the session timestamp), and `_atutm` (the last campaign parameters). It then collects the conversions and customer details that happen on your site and delivers them server-side to ad platforms via the [Conversion API](/glossary/conversion-api), enriching each session ([Session Enrichment](/glossary/session-enrichment)) so attribution and match quality survive without third-party cookies.
