Back to blog
SKAN 4.0Apple Search AdsAttributionPrivacyMobile UA

SKAN 4.0 and Apple Search Ads Conversion Tracking: The New Rules of the Game

Learn how SKAN 4.0 changes conversion tracking in Apple Search Ads with multi postbacks, crowd anonymity, and smarter attribution models.

By Berk AydınJune 25, 20255 min read

In the post-IDFA era, privacy is the currency—and Apple's SKAdNetwork (SKAN) has been its gatekeeper. Since its launch, marketers and developers have struggled to maintain visibility on campaign performance without compromising user privacy. SKAN 4.0 — which has now been the production standard for nearly two years — reshaped how the entire industry measures iOS performance. And if you're running Apple Search Ads, understanding these rules is no longer optional. It's essential.

Let's dive into what SKAN 4.0 brings to the table, how it changes conversion tracking in Apple Search Ads, and what advertisers need to do to stay competitive in 2026.

From Limited to Layered: What SKAN 4.0 Changes

SKAN 4.0 introduces three major upgrades:

Multiple Conversion Windows

Instead of a single postback, SKAN 4.0 allows for up to three postbacks over time—covering 0-2 days, 3-7 days, and 8-35 days after the ad interaction. This longer conversion window is crucial for measuring events that don't happen immediately, such as subscriptions or in-app purchases (IAPs).

Crowd Anonymity Levels

Apple introduces privacy tiers (low, medium, high) based on how many installs your campaign gets. More installs = more data. At higher tiers, you receive more detailed postbacks. This incentivizes scale, making high-volume campaigns more valuable for insights.

Hierarchical Source IDs

Source identifiers now have a tiered structure—from 2 digits (low volume) to 4 digits (high volume)—allowing better segmentation of campaigns, ad groups, or even creatives. But again, the granularity you get depends on volume.

What This Means for Apple Search Ads

Apple Search Ads has always been one step ahead when it comes to attribution. Because it runs within Apple's ecosystem, it already provides full-funnel attribution. However, SKAN 4.0 now enables advertisers to gain deeper visibility even outside of Search Ads' built-in reporting—especially when using third-party MMPs like Adjust or AppsFlyer, or internal data pipelines.

Here's how it impacts your Apple Search Ads campaigns:

  • Better ROAS Attribution for Delayed Conversions: With up to 35 days of tracking, subscription apps and IAP-heavy games can finally attribute late events more accurately. The math behind this is covered in detail in our piece on ROAS in IAP games.
  • Increased Emphasis on Volume: To unlock granular postbacks and full Source ID range, campaigns need volume. This could push advertisers to consolidate budgets or optimize towards broader match types to scale up impressions and installs.
  • Enhanced Creative & Keyword Testing: The hierarchical Source ID system makes it possible to track performance at a more granular level—if you hit the volume threshold. Smart keyword grouping and creative testing become essential.

Practical Example: A Gaming App Using Apple Search Ads

Let's say you're promoting a PvP mobile game with IAP monetization. Under SKAN 3.0, your visibility on purchases made after the first day was blurry at best. Now, with SKAN 4.0, you can track a user who installs on Day 0, plays casually for a few days, and then makes their first purchase on Day 5. That purchase can now be attributed properly—assuming your campaign volume is sufficient.

This changes how you model your return on ad spend (ROAS). No longer do you have to settle for early proxy metrics like retention or tutorial completion. You get actual revenue events, spaced across three postbacks, allowing for more accurate LTV modeling.

35 days

Maximum SKAN 4.0 attribution window

Apple Developer Documentation

Challenges to Keep in Mind

Despite its improvements, SKAN 4.0 isn't perfect:

  • Data Delay: Postbacks still come with delays (up to 24-48 hours), making real-time optimization difficult.
  • Data Gaps for Low-Volume Campaigns: Smaller campaigns might still be stuck with limited visibility due to low crowd anonymity.
  • Complex Implementation: Taking full advantage of SKAN 4.0 often requires working closely with MMPs, using Apple's API updates, and adjusting data infrastructure.

Best Practices for Advertisers

  • Optimize for Early Signals + Late Events: Design user flows that encourage valuable actions early (within Day 0–2), but also track mid- to long-term conversion behavior.
  • Consolidate Where It Counts: Focus your budget on campaigns that can scale, unlocking richer data from SKAN's tiered structure.
  • Leverage ASA Insights + SKAN Data Together: Use Apple Search Ads' native reporting for short-term performance, and SKAN 4.0 data to model longer-term value.
  • Keep Your MMP Updated: Work with your Mobile Measurement Partner to ensure full SKAN 4.0 integration. Many offer tools to map postbacks and model LTV effectively.
Key takeaway
  • SKAN 4.0 added 3 postback windows (0-2d, 3-7d, 8-35d), enabling proper LTV attribution for delayed conversions.
  • Crowd anonymity tiers reward scale — small campaigns get less data, period.
  • Use ASA native reporting for short-term signal, SKAN data for long-term LTV modeling.
  • SKAN 5.0 is now rolling out — but the SKAN 4.0 principles still drive 95%+ of iOS attribution decisions.

Final Thoughts

SKAN 4.0 doesn't just add features—it fundamentally shifted how we measure and optimize performance in a privacy-first ecosystem. For Apple Search Ads, it unlocked long-awaited visibility into delayed conversions and deeper campaign segmentation.

But to benefit, advertisers must adapt their strategy: prioritize scale, update attribution models, and bridge first-party data with SKAN insights. Those who master this complexity will not only survive the post-IDFA era—they'll thrive in it. For broader UA economics in this new environment, see our analysis on whether paid marketing is getting too expensive.

Berk Aydın

Performance Marketing Lead at Roasy. Writes about ROAS, retention, and the messy economics of mobile UA.

Keep reading

All posts →