If your conversions are off mainly for iPhones, it's no accident. iOS and Safari are the environment where client-side measurement loses most. Here's why — and how to recover much of your iOS conversions.
Why iOS is harder
- Safari ITP caps the lifetime of JavaScript-set cookies to 7 days (sometimes 24h).
- App Tracking Transparency limits cross-app tracking.
- iCloud Private Relay hides the IP address, reducing accuracy.
The result: for iOS/Safari traffic, client-side measurement sees far fewer conversions than actually happen. The mechanism is in ITP, iOS and ad-blockers.
How server-side recovers it
- Server-set first-party cookies aren't subject to ITP's 7-day cap — longer journeys stay connected.
- Server-to-server sending via official APIs (Measurement Protocol, Conversions API) works even without a reliable client-side environment.
- Hashed identifiers (email, phone) improve matching even where a cookie is missing — see Enhanced Conversions.
How to measure the loss yourself
Compare your iOS/Safari share in GA4 with the gap between ad conversions and store orders. The higher the iOS share, the bigger the impact — and the bigger the server-side benefit.
Summary
iOS conversions aren't lost forever — client-side measurement just doesn't capture them. Server-side tracking with first-party cookies and server-to-server sending recovers much of it. Start with the complete guide.