wesaw
FRGet started

First-party tracking

Also known as: first-party data collection, own-domain tracking

First-party tracking means the shop collects visitor events on a domain it owns, such as a subdomain of its own shop, instead of sending them to a shared vendor domain. Blockers and browsers treat the two differently: a request to the shop's own domain is part of the site, not a third party.

Can first-party tracking still be blocked?

Yes. A shop's own subdomain is not a guarantee against tracking protection. Browsers and blockers can apply rules to first-party requests or identify a third-party service behind a CNAME. Changing the hostname does not prove that an event will be collected.

Is first-party tracking the same as a first-party cookie?

Related but not identical. A first-party cookie is set by the site the visitor is on; first-party tracking is the wider practice of collecting on your own domain. Safari still limits how long some first-party cookies survive, which is why collection alone does not solve attribution.

What does first-party tracking still not solve?

It does not guarantee longer identification, create consent or prove advertising attribution. In wesaw, a custom collection domain is an advanced option without automatic activation in the current setup. Server delivery to Meta still requires recorded consent to be granted.

Sources

  • Safari can detect trackers cloaked behind first-party subdomains and block their requests in Private Browsing. A first-party hostname is not a guarantee against tracking protection.WebKit
  • Safari's Intelligent Tracking Prevention caps script-written first-party cookies at seven days, and at 24 hours when the visit arrived through a link with tracking parameters.WebKit

Last reviewed: