Recovering Lost iOS Conversions: A Practical Guide

If you’re running ads and not using server-side tracking, you’re likely losing 30-40% of your iOS conversion data. Apple’s privacy features—particularly Intelligent Tracking Prevention (ITP)—have fundamentally broken traditional pixel-based tracking.

The iOS Tracking Problem

Safari on iOS implements Intelligent Tracking Prevention (ITP), which:

• Limits first-party cookies to 7 days (or 24 hours for JavaScript-set cookies)
• Blocks third-party cookies entirely
• Removes tracking parameters from URLs in some cases
• Limits localStorage for cross-site tracking prevention

For advertisers, this means:

1. Users who click an ad but convert after 7 days appear as organic
2. Users who research on desktop but purchase on mobile lose attribution
3. Campaign data becomes increasingly unreliable

How Much Data Are You Losing?

Let’s do some quick math:

• iOS users represent ~55% of mobile traffic in the US
• Safari has ~18% of total browser market share
• Average consideration time for purchases: 14-30 days

If your average customer takes 10 days to convert, you’re losing attribution on most of your iOS Safari users.

The Server-Side Solution

Server-side tracking solves the ITP problem by:

1. Storing click IDs server-side - Not affected by cookie limits
2. Matching conversions via user identity - Email, phone, or user ID
3. Maintaining longer attribution windows - 30, 60, or 90 days
4. Sending data via API - Bypasses browser restrictions

Here’s how the flow works:

User Journey (with server-side tracking)
────────────────────────────────────────
Day 1: User clicks Meta ad (fbclid captured server-side)
Day 3: User returns via Google search
Day 7: Safari deletes cookies ← Traditional tracking breaks here
Day 12: User converts on iOS Safari
Day 12: Server matches conversion to original click ✓

Implementation Steps

Step 1: Add Server-Side Tracking

Install the Convultra tracking snippet:

<script src="https://cdn.convultra.com/ultra.js"></script>
<script>
  Convultra.init('your_project_id');
</script>

This automatically captures and stores click IDs server-side.

Step 2: Configure Identity Resolution

For best results, pass user identifiers when available:

// When user logs in or provides email
Convultra.identify({
  email: 'user@example.com',
  // or phone: '+1234567890'
});

Step 3: Track Conversions

Send conversion events from your server:

Convultra.trackPurchase({
  value: 149.99,
  currency: 'USD',
  orderId: 'ORD-12345'
});

Measuring Recovery

After implementing server-side tracking, you’ll see a “Recovery” metric in your dashboard showing exactly how many conversions were previously being lost.

Typical recovery rates:

Metric	Before	After	Recovery
Total Conversions	1,000	1,340	+34%
iOS Conversions	320	480	+50%
Attribution Accuracy	~70%	~95%	+36%

Best Practices

1. Run Parallel Tracking

Keep your existing pixels running alongside server-side tracking. This lets you measure exactly how much data you were missing.

2. Use Enhanced Conversions

Combine server-side tracking with Google’s Enhanced Conversions and Meta’s Advanced Matching for even better attribution.

3. Extend Attribution Windows

Since server-side tracking isn’t limited by cookies, consider extending your attribution windows to capture longer customer journeys.

4. Monitor Both Platforms

Compare iOS vs Android conversion rates. If there’s a significant gap, you likely have tracking issues.

The Bottom Line

iOS tracking recovery isn’t optional—it’s essential for accurate marketing measurement. With over half of mobile users on iOS, and Apple continuing to tighten privacy restrictions, server-side tracking is the only reliable solution.

Start your free trial and see exactly how much iOS data you’re currently losing.