What Is First-Party Tracking?
·
First-party tracking means setting tracking cookies and sending tracking requests from the same domain the visitor is on, rather than from a third-party domain such as a vendor's own servers. It typically involves routing analytics and ad-platform requests through a subdomain the site controls, often via a server container, and setting cookies on the site's own domain instead of a third party's. First-party tracking changes where data is stored and where requests originate; it does not change what consent is required before that data can be collected.
In practice
Browsers increasingly restrict or block cookies set by third-party domains — Safari’s Intelligent Tracking Prevention and Firefox’s Enhanced Tracking Protection both target third-party cookies specifically, while leaving first-party cookies largely untouched. Moving tag requests to a first-party subdomain, commonly through a server container, and setting cookies on the root domain means those cookies persist longer and those requests are less likely to be blocked outright, which is why first-party tracking is often paired with server-side tracking setups.
Common confusion
First-party tracking does not mean consent-free tracking, and setting cookies on your own domain does not remove the obligation to get consent before setting non-essential cookies or processing personal data — that obligation is based on what the cookie does and what data is collected, not which domain set it. It’s also not automatically more accurate: a first-party setup that never receives the browser event in the first place, because a script was blocked, an ad blocker filtered it, or consent was denied, has nothing to forward, first-party or not. This is a technical distinction about where data flows, not a compliance strategy.
How to check
In the browser’s DevTools, Application > Cookies (Chrome) or Storage > Cookies (Firefox) shows each cookie’s domain — one scoped to the site’s own domain rather than a vendor domain is first-party. The Network tab shows request origins the same way: requests going to a subdomain of the site, rather than directly to a third-party endpoint, indicate first-party routing.
Related entries
First-party tracking is usually implemented through a server container and still depends on Consent Mode v2 signals to determine what it’s allowed to collect. For implementation, see server-side tracking services.
Related entries
- Knowledge BaseWhat Is a Server-Side GTM Container?The difference between a server container and a web container in Google Tag Manager, and what running one changes.
- Knowledge BaseWhat Is Google Consent Mode v2?Consent Mode v2's basic vs advanced modes, the consent signal parameters, and how they affect GA4 and Google Ads tags.
- ServiceServer Side Tracking
Not sure whether your tracking is actually broken?
Start with a Health Check — a fast, read-only diagnosis that tells you what is wrong before you spend anything fixing it. Prefer email? Send your store URL and one sentence about what looks off.