Why your ROAS looks wrong — and how server-side tracking fixes it

If your ad platforms and your actual sales never agree, you're not alone. Browser-side tracking now misses a meaningful share of conversions because of ad blockers, cookie limits and iOS privacy changes. What goes wrong - Pixels blocked or cookies cleared → conversions never reported - Platforms optimise on incomplete data → budgets shift to the wrong campaigns - Every platform claims the same sale → totals don't add up What server-side tracking changes Your server sends conversion events (with hashed customer identifiers, after consent) directly to Google and Meta through their conversion APIs. Fewer events are lost, and the algorithms get better signals to optimise on. Getting started 1. Map your key events: lead, add to cart, purchase, qualified lead. 2. Set up the Conversions API (Meta) and enhanced conversions (Google). 3. Send offline conversions from your CRM, so the platforms learn which leads actually closed. 4. Compare platform numbers against your backend weekly. The goal isn't perfect attribution — it's data good enough to make confident budget decisions.