← Back to all blogs← Previous article

How to improve your Meta ROAS with server-side tracking

Most Shopify stores lose 30 to 40% of Meta conversion data to ad blockers and iOS. Server-side CAPI fixes the measurement, and the algorithm follows.

Why your Meta ROAS looks worse than it is

Your Meta Ads Manager shows a ROAS of 2.4. Revenue looks flat. You cut budget. The problem was never the ads. It was tracking. Meta was only seeing about 60% of actual conversions, so every campaign looked underperforming.

The three things killing your Meta conversion data

About 30 to 40% of desktop users run an ad blocker. uBlock Origin, AdBlock Plus, and Brave all block the Meta Pixel by default. Every blocked pixel event is a conversion Meta never sees and never credits.

Since April 2021, iOS users must opt in to tracking. Most decline. The Meta Pixel on Safari is severely limited. Fashion, beauty, and lifestyle brands with iPhone-heavy audiences lose a disproportionate amount of data.

Safari limits first-party cookies set via JavaScript to 7 days. If a customer browses on day 1 and purchases on day 8, the pixel cannot connect those events. The attribution window is broken.

What server-side CAPI does differently

The Meta Conversions API sends events from your server to Meta, bypassing the browser. Ad blockers cannot intercept server-to-server requests. iOS restrictions do not apply. Cookie expiry is irrelevant because you send first-party data captured at checkout.

When you run the Meta Pixel and CAPI together (dual-dispatch), Meta deduplicates on event_id. You keep browser signals from the pixel and reliable first-party data from the server.

Dual-dispatch is the current best practice. Pixel alone misses 30 to 40% of events. Server-side alone misses browser-specific signals.

The EMQ connection

Meta scores every CAPI event with Event Match Quality from 0 to 10. Higher EMQ means better matching and better algorithm optimization. A low EMQ with CAPI active still leaves money on the table.

Identifiers that move Meta EMQ most are hashed email (+2.5), phone (+2.0), _fbp cookie (+1.5), and _fbc click ID (+1.5). Layer Insights sends these when available and shows live EMQ in the dashboard.

+2.5
Hashed email
+2.0
Hashed phone
+1.5
_fbp / _fbc each

What changes in your campaigns

With complete conversion data, the algorithm exits learning faster, CPA drops, lookalikes improve because they are built on complete purchase data, and reported ROAS rises because you are measuring correctly. Layer Insights starts dual-dispatch on install. Average EMQ improvement across customers is +2.8 points within 48 hours.

Layer Insights app

See the same decision in your own commerce data

Open Layer Insights →
Read next

GDPR-compliant tracking: run Shopify ads without breaking privacy law

Continue reading →