iOS 14.5 Signal Loss Simulator

Estimate how many Meta conversions you are losing to ATT opt-outs — and what a server-side CAPI rebuild is realistically worth to you per month.

Inputs

Your Meta numbers

Industry defaults are pre-filled. Adjust the sliders to match your account.

$

Whatever Meta Ads Manager is showing you today.

60%

Most US/EU eComm sites land between 50% and 70%. Check GA4 → Tech → Operating system.

25%

Industry average is ~25%. Higher if your audience is younger / power-user; lower for finance & privacy-conscious verticals.

Hidden by ATT

$17,245/ month

Real revenue your Meta account is driving but cannot see today. That is $14,658 recoverable per month with a server-side CAPI rebuild — $175,894 a year.

Effective attribution

69%

Share of true conversions Meta is currently seeing.

Signal loss

31%

Conversions invisible to bidding right now.

True revenue / mo

$54,745

What ads are actually driving.

ROAS after CAPI

3.48×+0.98

Restored ROAS once iOS conversions return.

How this is modeled. Opt-in users are tracked normally. Opt-outs lose deterministic attribution; SKAN aggregated reporting recovers about 30% of those signals at most. Non-iOS traffic is unaffected.

CAPI + first-party event matching typically claws back 70–90% of the iOS signal that ATT removes, by sending hashed user data server-to-server with a high event-match-quality.

INTERACTIVE DEMO Want to test how this tool works?
Save these results as a PDF report A clean, branded copy to share with your team or client.
Free PDF report

Where should we put your name on the report?

Your PDF downloads straight away. Your tool data never leaves your browser.

Jobair Mahmud, Web Analytics & Tracking Architect
Tool Creator

Jobair Mahmud

Founder & Tracking Architect

100% Top Rated
★★★★★
5.0 / 5.0

Need to recover lost iOS conversions?

I configure full-funnel Meta CAPI with Event Match Quality scores above 8.5/10 to maximize conversion delivery on iOS.

Deploy Meta CAPI →

How to use the iOS 14.5+ ATT Signal Loss Simulator

Apple App Tracking Transparency (ATT) framework requires users to opt in to cross-site tracking, with opt-in rates hovering around 20%–25%. This simulator estimates the extent of unmeasured conversions on iOS devices and shows how server-side Conversions API (CAPI) bridges the attribution gap.

Step by step

  1. Enter your average monthly website conversion count.
  2. Input the estimated percentage of your visitors using iOS / Safari devices.
  3. Review the predicted attribution drop under client-side only tracking.
  4. Compare standard results against modeled and server-side signal recovery projections.

How to read your result

Low Impact (<15% signal loss)

B2B or desktop-heavy audience where iOS tracking restrictions have minimal effect on reporting.

High Impact (>30% signal loss)

Consumer eCommerce or mobile brand heavily affected by ATT. Meta CAPI and first-party cookies are essential to preserve ROAS.

Common mistakes

  • Assuming in-app browser traffic on Instagram and Facebook is exempt from ATT restrictions.
  • Failing to verify your domain in Meta Business Manager and configure Aggregated Event Measurement (AEM).
  • Not passing customer data (email, phone, fbp, fbc) to server events to compensate for lost device IDs.

Questions

How does Meta CAPI help with iOS ATT?

CAPI sends conversion events directly from your web server to Meta servers using first-party data (hashed email, phone, IP), bypassing browser-level blocking entirely.

Does ATT block server-side tracking?

ATT regulates third-party app tracking across unrelated companies. First-party server data sent directly from your own domain to match conversions is fully compliant under platform guidelines.

Need to recover lost iOS conversions?

I configure full-funnel Meta CAPI with Event Match Quality scores above 8.5/10 to maximize conversion delivery on iOS.