MEMORANDUM OF RULING · REF VRD-001
IN THE MATTER OF THE CLAIM:
“You don't need server-side tracking.”
BROUGHT BY — every vendor pitch and every sceptic, at once · HEARD — 12 JUN 2026 · CITES F-401 F-204
- FOR-1
For a smaller site with a clean consent banner and a solid first-party setup, browser-side collection still captures most of what matters. The signal you would recover is real, but small.
MEASURED - FOR-2
Server-side GTM adds hosting, cost and a new failure surface to monitor. At low volume, that complexity rarely pays for itself.
DOCUMENTED - AGT-1
Server-side is not magic, it is mechanism. Serve the endpoint as first-party on your own domain and you can set cookies that outlast ITP’s cap on script-set ones, so returning visitors and their attribution survive. And a server call is harder for ad and script blockers to drop than a browser pixel. Both are measurable, not theoretical.
MEASURED - AGT-2
At ecommerce scale, Enhanced Conversions and Meta’s CAPI are how attribution survives a cookieless browser. Both get more durable run server-side: harder to block, and able to send hashed first-party data the browser would otherwise lose. At that scale it is no longer optional.
RULING BASIS - AGT-3
Across our own case files, where match quality was bleeding, moving collection server-side closed a gap that no browser-only fix could touch.
MEASURED
On Shopify, the three checks to run first and how the tools compare are in Elevar vs Stape vs Littledata vs native.
RULING
Server-side is not a moral upgrade, it is a recovery tool. If nothing is eroding your signal, you are insuring against a fire that is not burning. If your match quality is bleeding, it is the hose.
— B. Asa · entered into the record 12 JUN 2026