Honest Growth
← Back to Lulu Lemonade's audit

iOS users are mostly invisible to Meta

Apple's privacy blocks ~60% of your purchase data from reaching Meta. Your campaigns are optimizing on a partial picture.

Purchase event coverage · 60 days

Browser pixel804

iOS users mostly blocked by ATT

Conversions API (server-side)306

Should be ≥80% of browser. Currently at 38%.

Costing you

$1,500

per month · $18,000 per year

Time to fix

2h 30m

Estimated, in Meta Ads Manager

How sure are we

Medium confidence · 80%

Below 90% comes with a 'what would change our mind' note

What's happening

When someone buys from you, Meta should hear about it two ways: through the browser pixel (in their browser) and through the Conversions API (from your server). Right now the server-side path is only sending 38% of what the browser sees.

For a DTC beverage brand, iOS users are usually a big share of your buyers — and they're the ones Apple's privacy changes block hardest. Meta is optimizing your bids on roughly half your actual purchase data. The fix is a Shopify integration that takes about 90 minutes. After 14 days, expect reported ROAS to climb 5–15%.

Where we could be wrong

When this finding doesn't apply

If you implemented CAPI within the last 7 days, the ratio will look weak while server traffic catches up — wait 14 days post-implementation before acting. If you sell mostly through a marketplace where the browser pixel doesn't fire (rare in DTC), the comparison is invalid.

We show this on every finding below 90% confidence. Right now, we're at 80%.

How to fix it

Step-by-step, in Meta Ads Manager. No external tools needed.

  1. Open Meta Events Manager → your dataset → Settings → Conversions API.
  2. If you're on Shopify, use the first-party Shopify integration. It implements server-side Purchase, AddToCart, InitiateCheckout, and ViewContent with correct event_id deduplication.
  3. If you're on a custom stack, work with engineering to add CAPI via a partner (Stape, Segment) or directly to the Meta API.
  4. Verify deduplication: in Events Manager → Deduplication, the rate should be 70%+.
  5. Wait 14 days. Expect a 5–15% reported-ROAS uplift, then gradual delivery improvement over 30–60 days.

The exact numbers we fired on

Click to see the raw evidence. Useful if you want to verify our math before acting.

Browser-pixel Purchases (60d)
804
CAPI Purchases (60d)
306
CAPI / browser ratio
38%
Account spend (60d)
$60,240
Recovery share (5% of monthly)
$1,500/mo

Want the full methodology behind this rule? Read the methodology →

Want this audit on your real account?

Export your Meta CSV, drop it on us — free, no sign-up, no card.