iOS 14+ Tracking: How to Recover Your Lost Conversion Data

When Apple introduced App Tracking Transparency (ATT) with iOS 14.5 in April 2021, it fundamentally changed digital advertising. Users had to explicitly opt in to tracking, and approximately 75-80% chose to opt out.

For advertisers, the impact was immediate and severe: conversion data from iOS users largely disappeared. Campaigns that relied on iPhone users saw their reported ROAS plummet, not because performance actually declined, but because the data was no longer visible.

Four years later, the iOS tracking problem hasn’t gone away, it’s become the new normal. But solutions have emerged. This guide covers everything you need to know about iOS 14+ tracking and how to recover the data you’re missing.

Understanding the iOS 14+ Tracking Problem

What Changed

Before iOS 14.5:

• Apps could access the IDFA (Identifier for Advertisers) by default
• Web tracking used third-party cookies and cross-site tracking freely
• Safari had some ITP protections, but overall tracking was robust

After iOS 14.5:

• Apps must ask permission to track via ATT prompt
• Only ~25% of users opt in
• Safari blocks all third-party cookies
• 7-day cap on first-party cookie duration in some cases
• SKAdNetwork limits attribution data granularity

Impact by Channel

Facebook/Meta Ads:

• 50-60% reported conversion underreporting
• Attribution window forced to 7-day click, 1-day view
• Conversion value optimization severely limited

Google Ads:

• Less impacted due to first-party data usage
• Still significant gaps for iOS Safari users
• App campaigns heavily affected

TikTok:

• Similar impact to Meta
• Attribution modeling requires more data

Programmatic Display:

• Cross-site tracking largely broken on iOS
• Retargeting effectiveness reduced

What’s Actually Happening

It’s important to understand: your conversions aren’t necessarily declining. What’s declining is your ability to see them.

An iOS user might:

1. See your Instagram ad
2. Click through to your site
3. Browse products
4. Return the next day via Safari
5. Complete a purchase

Before iOS 14, all of that was tracked and attributed to the ad. Now, steps 2-5 might be invisible, making the ad appear to have failed when it actually worked.

The Current iOS Tracking Landscape

What Still Works (Sort Of)

First-Party Cookies: Safari allows first-party cookies, though with limitations:

• 7-day expiration for JavaScript-set cookies in some scenarios
• 24-hour expiration for cookies with fingerprinting characteristics

SKAdNetwork: Apple’s privacy-preserving attribution framework:

• Provides some conversion data back to advertisers
• Delayed (24-48 hours)
• Limited to 64 conversion values
• No user-level data

Modeled Conversions: Ad platforms use machine learning to estimate conversions:

• Facebook’s Aggregated Event Measurement (AEM)
• Google’s conversion modeling
• Accuracy varies; directionally useful but not precise

What Doesn’t Work

• IDFA-based tracking (without opt-in)
• Cross-site third-party cookies
• Fine-grained attribution windows
• Real-time iOS conversion data
• User-level iOS attribution

Server-Side Tracking: The Primary Solution

Server-side tracking is the most effective way to recover iOS conversion data.

Why Server-Side Works for iOS

When you use server-side tracking:

1. User converts on your website
2. Your server captures the conversion
3. Server sends data directly to ad platform APIs
4. Transmission happens server-to-server, not browser-based

The key insight: iOS browser restrictions affect browser-based tracking. They don’t prevent your server from communicating with Meta or Google’s servers.

What Server-Side Can Recover

Data Type	Pixel-Only (iOS)	+ Server-Side
Purchase Events	~40-50%	~90-95%
Add to Cart	~50-60%	~90-95%
Lead Forms	~50-60%	~90-95%
User Matching	Poor	Good

Implementation Impact

Advertisers implementing server-side tracking for iOS typically see:

• 30-50% more reported conversions
• Improved Event Match Quality
• Better attribution data for optimization
• More accurate ROAS calculations

Recovering iOS Conversions: Step by Step

Step 1: Implement Server-Side Tracking

Option A: No-Code Platform

Platforms like Convultra handle iOS tracking automatically:

1. Install tracking script on your site
2. Connect your ad platform accounts
3. The platform captures iOS conversions server-side
4. Data flows to Meta, Google, etc. via APIs

Option B: DIY Implementation

For custom implementations:

1. Set up server infrastructure
2. Capture conversion events on your backend
3. Implement Meta Conversions API
4. Implement Google Enhanced Conversions
5. Handle user matching and deduplication

Step 2: Maximize Event Match Quality

Event Match Quality (EMQ) is crucial for iOS recovery. Send these parameters:

High-Impact Identifiers:

• Email (hashed): Most important for matching
• Phone (hashed): Highly effective
• First name + Last name (hashed): Improves match rates

Browser Identifiers:

• fbp cookie: First-party Facebook cookie
• fbc cookie: Click ID cookie
• Client IP address: Helps with matching
• User agent: Assists identification

Example CAPI payload for iOS recovery:

{
  "event_name": "Purchase",
  "event_time": 1706745600,
  "event_source_url": "https://yoursite.com/thank-you",
  "action_source": "website",
  "user_data": {
    "em": ["hashed_email"],
    "ph": ["hashed_phone"],
    "fn": ["hashed_firstname"],
    "ln": ["hashed_lastname"],
    "client_ip_address": "user_ip",
    "client_user_agent": "user_agent_string",
    "fbp": "fb.1.1706745600.1234567890",
    "fbc": "fb.1.1706745600.AbCdEf123"
  },
  "custom_data": {
    "value": 99.99,
    "currency": "USD"
  }
}

Step 3: Preserve First-Party Cookies

While Safari limits cookies, first-party cookies still work:

// Set first-party cookie with appropriate attributes
function setTrackingCookie(name, value, days) {
  const date = new Date();
  date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));
  const expires = "; expires=" + date.toUTCString();

  // First-party cookie settings
  document.cookie = name + "=" + value + expires +
    "; path=/; SameSite=Lax; Secure";
}

// Preserve Facebook click ID
const urlParams = new URLSearchParams(window.location.search);
const fbclid = urlParams.get('fbclid');
if (fbclid) {
  setTrackingCookie('_fbc', 'fb.1.' + Date.now() + '.' + fbclid, 90);
}

// Generate and preserve browser ID
if (!getCookie('_fpid')) {
  setTrackingCookie('_fpid', generateUUID(), 365);
}

Step 4: Configure Ad Platform Settings

Meta Ads:

1. Verify domain in Business Settings
2. Configure Aggregated Event Measurement
3. Prioritize your 8 events
4. Enable Conversions API

Google Ads:

1. Enable Enhanced Conversions
2. Configure consent mode (if applicable)
3. Link GA4 for modeled conversions
4. Enable conversion modeling

Step 5: Use Modeled Conversions Strategically

Ad platforms provide modeled (estimated) conversions:

How to use them:

• Understand they’re estimates, not exact data
• Use for directional optimization
• Don’t compare directly to pre-iOS14 numbers
• Focus on relative performance (campaign A vs B)

What to expect:

• Meta shows modeled conversions in reporting
• Google uses conversion modeling in Smart Bidding
• Actual conversions are likely higher than reported

Additional iOS Recovery Strategies

Strategy 1: Email-First Capture

Since email is the most effective matching identifier, capture it early:

• Email pop-ups on entry
• Account creation incentives
• Newsletter signup before checkout
• Wishlist/save features requiring email

Strategy 2: Native App Tracking (If Applicable)

If you have a native iOS app:

• SKAdNetwork for app install attribution
• App-based conversions aren’t subject to web restrictions
• Deep linking from ads to app

Strategy 3: Post-Purchase Attribution

Match conversions after they happen:

• Use order email to match to ad click
• Customer Data Platforms (CDPs) can help
• CRM integration for lifetime attribution

Strategy 4: Aggregate Analytics

Focus on aggregate trends rather than user-level:

• Compare week-over-week performance
• Use Marketing Mix Modeling (MMM)
• Incrementality testing
• Geo-based lift studies

Measuring Your iOS Recovery

Before/After Metrics

Track these metrics before and after implementing recovery solutions:

Metric	Before	After	Change
iOS Conversions (reported)
iOS Conversion Rate
Event Match Quality
Modeled vs Observed ratio

Platform-Specific Indicators

Meta:

• Event Match Quality score (aim for “Good” or “Great”)
• Server events percentage (should be near 100%)
• ATT impact indicator in Ads Manager

Google:

• Enhanced Conversions match rate
• Modeled conversions percentage
• Conversion action diagnostic status

Expected Improvements

With full server-side implementation:

• 30-50% increase in reported iOS conversions
• Event Match Quality improvement of 2-3 levels
• More stable campaign optimization
• Better ROAS visibility

Frequently Asked Questions

Will Apple ever reverse these changes?

Unlikely. Privacy is central to Apple’s brand positioning. Expect continued restrictions, not relaxation.

Can I still target iOS users effectively?

Yes, but strategies differ:

• Broad targeting works better than narrow
• Use lookalike/similar audiences based on server-side data
• Focus on creative quality over hyper-targeting

Is there any way to get IDFA access?

Only if users opt in via the ATT prompt. Some apps achieve 30-40% opt-in rates with good messaging, but most see 15-25%.

How does this affect my overall marketing strategy?

• Invest in first-party data collection
• Diversify beyond iOS-heavy channels
• Use server-side tracking as standard
• Accept that some data will remain modeled

What about future iOS versions?

iOS continues to add privacy features. Server-side tracking provides the most future-proof foundation.

Conclusion

iOS 14+ changed digital advertising permanently. The businesses that thrive are those that adapted: implementing server-side tracking, maximizing first-party data, and accepting that some uncertainty is the new normal.

The good news is that effective solutions exist. Server-side tracking recovers the majority of lost conversions. First-party data strategies provide sustainable targeting. Aggregate analytics give directional guidance.

Don’t accept the “iOS killed my tracking” narrative. Your conversions are still happening, you just need the right infrastructure to see them.

---

Convultra’s server-side tracking is specifically designed to recover iOS conversion data. See up to 95% of your iOS conversions with setup in under 5 minutes. Start your free trial

Related Reading

• The Complete Guide to Server-Side Tracking in 2026 — how server-side tracking works and why it’s essential
• What Is Server-Side Tracking? — a beginner-friendly explainer
• Cookieless Tracking in 2026 — future-proofing your data beyond iOS restrictions
• First-Party Data: What It Is and How to Collect It — building a privacy-first data foundation