Apple’s rebrand from Search Ads to Apple Ads came with more than a name change: the network now supports view-through attribution, crediting an install that happens within 24 hours of a user seeing an ad — even if they never tapped it. Paired with AdAttributionKit’s privacy-preserving design, this means Apple Ads can now report conversions with no App Tracking Transparency prompt and no SKAdNetwork postback required for the attribution itself, tracking deep events like subscription activation and renewal alongside the initial install.
The problem it creates is a familiar one in attribution: a metric got more generous without a corresponding change in what actually drove the install. A user who saw an ad in the App Store and later found the app organically, or through an entirely different channel, can now be counted as an Apple Ads conversion purely because the view fell within the 24-hour window. Teams that don’t separate view-through installs from tap-through installs in their reporting will see Apple Ads’ apparent performance rise and, if budget follows that number uncritically, will overspend on a channel that didn’t actually cause the lift it’s being credited for.
Data Points to Track
- Attribution type per install (view-through vs. tap-through), pulled separately rather than as a combined Apple Ads total, since the two represent very different strength of causal evidence
- Time between ad impression and install, bucketed within the 24-hour window, so installs crediting the ad at 23 hours after a view (weak signal) are distinguishable from installs seconds after a tap (strong signal)
- Overlap with other channels’ attribution windows, checked for the same user or device where possible, since a view-through credit and another channel’s last-touch credit can both claim the same install
- Post-install behaviour split by attribution type, comparing retention, activation, and LTV for view-through-attributed users against tap-through-attributed users — if they don’t differ, that’s a reason to trust the view-through signal more
- Spend efficiency (CAC) recalculated with view-through installs excluded, kept as a standing comparison metric alongside the headline blended CAC, so budget decisions have both numbers available
Setup Steps
- Pull attribution type as a separate dimension in Apple Ads reporting or your MMP’s Apple Ads integration — don’t rely on a single blended conversion count from the dashboard’s default view.
- Set a standing comparison report showing spend and CAC calculated twice: once including view-through installs, once excluding them, refreshed on the same cadence as your regular acquisition reporting.
- Cross-check overlapping attribution against your other paid channels for the same reporting period, watching for a rise in one channel’s view-through credits coinciding with a drop in another channel’s last-touch credits for similar volumes.
- Instrument a post-install cohort tag capturing attribution type at the moment of first open, so downstream retention and LTV analysis can be split by it without re-querying the ad network later.
- Set a review trigger — if view-through installs exceed a set share of total Apple Ads conversions (start conservative, tighten as you gather data), flag the campaign for manual review before scaling spend further.
Actionable Insights
A campaign showing strong overall conversion growth that’s mostly made up of view-through installs, with tap-through volume flat, is a signal the ad’s creative or placement is building awareness rather than driving direct action — useful for brand campaigns, misleading if the budget is meant to be performance-driven. If view-through-attributed users show meaningfully lower retention or LTV than tap-through users, that’s evidence the 24-hour window is picking up organic or other-channel installs that happened to follow a view, and CAC calculated on the blended number is understating true acquisition cost. Conversely, if the two cohorts perform similarly post-install, that’s a reason to trust Apple’s view-through credit as a genuine causal signal rather than discount it by default — the data, not the mechanism, should decide how much weight it gets in a budget conversation.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert