First-party tracking reads identifiers that the domain in the browser’s address bar stored: the landing page sets the cookie, the landing page reads it back. Third-party tracking reads identifiers that a different domain stored, which is how pixels and tags used to follow one person across many sites. In Meta ads the difference decides how long a click identifier survives, because browsers now block third-party cookies and shorten the ones JavaScript writes.
Who sets the cookie, and who can read it
The label comes from the domain, not from the tool. A cookie is first-party when it belongs to the site the visitor is on, and third-party when it belongs to another site loaded inside that visit.
| First-party | Third-party | |
|---|---|---|
| Set by | the domain in the address bar | a different domain, embedded in the visit |
| Read by | the same domain | the domain that set it, on any site that loads it |
| Safari and Firefox | allowed, with limits on lifetime | blocked by default |
| Chrome | allowed | a user choice in Privacy and Security settings, and blocked in Incognito |
| What it can follow | one site | one person across sites |
A third-party cookie was the mechanism that made cross-site advertising measurement work: one identifier, seen on many publishers, gathered in one place. Once browsers refused it, the cross-site picture had to come from somewhere else, which is why server events and modelled conversions grew.
Where the Meta Pixel sits, and why it is the confusing case
The Pixel’s own cookies, _fbp and _fbc, are written by a script on your landing page, so the browser files them under your domain. By domain they are first-party. By writer they are not, and Safari’s tracking prevention judges the writer.
- A cookie created by JavaScript is deleted after 7 days without user interaction with the site.
- When Safari detects a click ID in the URL, cookies that JavaScript creates on that landing page are capped at 24 hours.
fbclid, the parameter Meta appends to an ad click, is a click ID.
So the Pixel can be first-party in the cookie list and still lose the identifier within a day, exactly when a lead takes a few days to decide. That is why the interesting question is not “first-party or third-party” but “who wrote this, and where”.
The three changes that removed the old model
| Change | When it started | What it stopped |
|---|---|---|
| Safari tracking prevention | 2017 | cookies written by JavaScript lasting more than 7 days, or 24 hours after a decorated link |
| App Tracking Transparency | iOS 14.5, 2021 | cross-app identity for apps that do not get permission |
| Third-party cookie blocking | browsers, ongoing | cookies a pixel or tag sets from its own domain |
Meta’s response was to accept partial data and model the rest. Modelled conversions are Meta’s estimate where data is missing, and they are a reasonable answer at platform level. They are a poor answer for a business that has to know which landing page produced which lead, because the estimate cannot be checked against a form submission.
Why a cookie written by the server survives
A cookie set in an HTTP response header is written by the server, not by JavaScript, so the 7-day and 24-hour limits that apply to script-written cookies do not touch it. A cookie set by the domain that serves the landing page is also first-party, so third-party blocking does not apply. Both conditions together are the design: one request to your domain, one response that renders the landing page and sets the identifier.
Two exceptions matter:
- A subdomain that resolves through a CNAME to a third party, or straight to a third party IP address, does not escape. Safari caps cookies from that server at 7 days.
- A redirect chain defeats the point. If the click lands on a tracking domain that redirects to the landing page, the identifier is set in a response the browser will not keep as the landing page’s own cookie. One request, one response, one cookie.
This is the mechanism behind server-side tracking for Facebook ads, and the timeline of what broke and when is in tracking after iOS.
What first-party tracking does not fix
Moving where an identifier is stored changes how it survives, not what you are allowed to do with it.
- Consent. Meta says the Conversions API, like the Pixel, is not designed to bypass App Tracking Transparency or European privacy rules such as the ePrivacy Directive.
- User controls. Server events follow the same off-Facebook activity and partner data settings as Pixel events.
- Attribution windows. A server event is attributed under the ad set’s attribution setting, like any other event.
- Modelled conversions. Meta may still model where data is partial, whatever the transport.
- Cross-domain journeys. If the person clicks on your landing page domain and converts on a different domain you own, that lead is not tied to the click.
- Events without identifiers. An event Meta cannot match to an account is attributed to nobody, however it was sent.
Read the list before the pitch, from any vendor. First-party tracking recovers the click, and consent, opt-outs and attribution settings stay where they were.
How to tell which setup you have
- Open the landing page in a browser, then look at the cookies for that domain and read their domain attribute. A cookie whose domain is yours is first-party.
- Check who wrote it. In the network panel, a
Set-Cookieheader on the document request means the server wrote it. An entry that appears after the scripts run means JavaScript did. - Follow the click from the ad. If the ad points at a tracking domain that redirects, the identifier is being set on the wrong side of a redirect.
- Check for a vendor subdomain. A name like
track.yourdomain.comthat resolves to a provider is a third-party server, and Safari treats it as one. - Submit the form and read the event in Events Manager or Test Events. If the click identifier is missing, the cookie was never there to read.
None of this requires a vendor, and all of it is visible in a browser. What changes with a setup you control is who owns the answer to “which ad produced this lead”, and the tracking domain glossary entry covers the naming side.
DropCPL runs that design as the default: the landing page is served from your tracking domain and the click cookie is first-party and HttpOnly in the same response, with no redirect, so each lead is tied to the ad, the creative and the landing page, and the conversion goes back to Meta through the Conversions API. If the CRM is the next step, first-party tracking with Pardot shows where the record has to sit. More questions on pixel, server events and attribution are in Meta Pixel, Conversions API and attribution.