In short: Pixels see less every year and platforms fill the gaps with modeled estimates. First-party data, server-side tracking, tagged links and consent are the measurement layer that survives, and the company should own it, not whoever runs its media.
Key points
- Each platform tracks conversions independently, so their reported totals have always exceeded actual customers.
- Cookie blocking, app tracking consent, privacy law and ad blockers mean reported conversions are partly inferred.
- Server-side tracking records events on the company's own server and forwards them through platform conversion APIs.
- Tagged links and unique codes are the primary tracking method for affiliate, creator and clipping programs.
- The company should own the analytics, tag manager, server-side setup, consent platform and first-party data.
Every marketing number depends on tracking: the ability to connect a person who saw or clicked something with a person who later did something. The mechanics have changed a great deal in a few years, and the changes explain why numbers that used to agree no longer do.
The old model: pixels and third-party cookies
A pixel is a small piece of code on a website that reports back to a platform when a page loads or an event happens. Each ad platform issues its own. The pixel sets or reads a cookie, a small file in the visitor's browser that lets the platform recognize the same browser later.
For a decade this worked well enough. A person clicked an ad, the platform's cookie followed them to the purchase, and the platform reported a conversion. Every platform did this independently, which is why the sum of all platforms' reported conversions has always exceeded the number of actual customers.
What changed
Browsers began blocking third-party cookies, the ones set by a domain other than the site being visited. Apple's mobile operating system began requiring consent before apps could track users across other apps, and most users declined. Privacy regulation in Europe, several U.S. states, and elsewhere required consent for many kinds of tracking. Ad blockers and privacy tools spread.
The result is that pixels see a shrinking fraction of what happens, and platforms fill the gaps with modeled estimates. Reported conversions became partly measured and partly inferred, and the inference is done by the party being measured.
First-party data
First-party data is information a company collects directly from its own customers and visitors, on its own properties, with their consent: email addresses, account activity, purchases, product usage. It is not affected by third-party cookie blocking because there is no third party.
It has become the foundation of measurement because it is the one source that does not depend on a platform's cooperation. A company that knows which of its own customers came from which source, by asking, by tagging links, by matching emails, can measure channels the pixels cannot see.
Server-side tracking
Instead of the visitor's browser reporting events to each platform, the company's own server records the event and forwards what is appropriate to each platform through their conversion APIs. The company controls what is sent, the data is not blocked by browser tools, and the record exists in the company's own systems first.
Server-side tracking is more work to set up and requires care about consent and what is shared. It is also the only way to keep platform reporting meaningful as browser-based tracking degrades, and it is the natural home for first-party data.
Tagged links and codes
The oldest tools still work. Parameters appended to URLs identify the source, medium, and campaign of a visit in the company's own analytics. Unique codes and landing pages per partner or creator attribute outcomes without any cookie at all. For affiliate, creator, and clipping programs, these are the primary tracking method, and they should be in the company's analytics, not only in the partner's.
Consent
Consent is not a formality. In most jurisdictions where a company sells, some form of it is required before tracking beyond what is strictly necessary. A consent management platform, a clear policy, and tracking that respects the visitor's choice are the minimum. Numbers gathered without consent are a liability, not an asset.
What a company should own, regardless of who runs the media
The analytics account. The tag manager. The server-side tracking configuration. The consent platform. The first-party data. The naming convention for tagged links. And a document that says which events are tracked, where, and how each channel's outcomes are confirmed.
A media partner can and should run the accounts on the company's behalf. The measurement layer underneath them should be in the company's name, because it is the record of what the money did.
lowob takeaway: Pixels see less every year and platforms fill the gaps with estimates. First-party data, server-side tracking, tagged links, and consent are the measurement layer that survives, and it should be owned by the company, not by whoever runs the media.
Common questions
Why don't my ad platform conversion numbers match my actual sales?
Each platform reports conversions independently, and as browser tracking degrades, platforms fill gaps with modeled estimates. Reported conversions are partly measured and partly inferred by the party being measured.
What is server-side tracking?
The company's own server records events and forwards what is appropriate to each platform through their conversion APIs, instead of the visitor's browser reporting to each platform.
What is first-party data in marketing?
Information a company collects directly from its own customers and visitors, on its own properties, with consent, such as emails, account activity, purchases and product usage.
What parts of marketing measurement should a company own if an agency runs its ads?
The analytics account, tag manager, server-side tracking configuration, consent platform, first-party data, tagged-link naming convention, and a document describing what is tracked.