Free answer · verified July 2026
What match rate can server-side tracking really get?
Vendor decks promise 95–99% match rates. The credible, independently-consistent range is roughly 85–90% — and the recovery claims beyond that come from the companies selling the recovery. Plan on 85–90%, and treat anything above as a bonus you verify, not a baseline you budget on.
Why the vendor number and the real number differ
A match rate is how many of your conversions the platform can tie back to a real person. The companies quoting 95–99% are the ones selling the tracking — their number comes from ideal conditions: every consent granted, every identifier present, every browser cooperative. Real traffic isn’t like that. Once you account for declined consent, missing identifiers, and blocked signals, the numbers that hold up across independent accounts sit around 85–90%.
The step that silently breaks everything
If you have European (or other consent-regulated) traffic, the consent signal is not optional plumbing. Skip or misconfigure it and your server-side setup doesn’t error — it just quietly drops those users from measurement, and sometimes from legal safety. Set up consent handling first, then measure your match rate, in that order.
What to actually do
Budget your expectations at 85–90%. When a vendor claims more, ask for the measurement conditions in writing. And test it yourself: fire a known set of test conversions and count what arrives. Twenty minutes of testing beats any deck.
Where this comes from
This is from the free chapter of The Modern Marketing Map — data, measurement and analytics, free in full, no signup. The correction from the vendor number to the credible range is logged in the evidence ledger,excerpt public here.