AdAttributionKit

What AdAttributionKit is

AdAttributionKit (AAK) is Apple's attribution framework for privacy-preserving measurement of iOS app advertising campaigns. Announced at WWDC 2024, it replaces SKAdNetwork (SKAN) as the primary mechanism for measuring app install and re-engagement campaign performance on iOS without accessing individual device identifiers.

Like its predecessor SKAN, AdAttributionKit is a system-level framework: it operates in Apple's operating system, not in the advertiser's app or the ad network's SDK. When a user sees an ad and installs an app, AdAttributionKit cryptographically records the attribution event and, after a delay window, reports aggregated performance data to the ad network — without revealing which specific user performed which action.

AdAttributionKit addresses several limitations of SKAdNetwork that had frustrated advertisers and mobile measurement partners (MMPs) for three years:

• Higher conversion value capacity: SKAN's 6-bit conversion value (0-63) constrained the granularity of post-install behavioral measurement. AAK expands this to a much higher capacity, allowing more detailed measurement of post-install events.
• Re-engagement measurement: SKAN measured only app installs. AAK supports measuring re-engagement campaigns (deep-linked ads that bring existing users back into the app) — a major gap that had made iOS retargeting measurement unreliable.
• Web-to-app attribution: AAK supports attributing conversions from mobile web to app installs, covering a measurement gap for advertisers running web-based acquisition alongside app campaigns.
• Developer-facing API: AAK provides a more direct API for developers, reducing intermediary complexity compared to SKAN's Apple-mediated architecture.

The timeline: SKAN to AdAttributionKit

SKAdNetwork history. Apple introduced SKAdNetwork in 2018, but it only became practically important in April 2021 when App Tracking Transparency (ATT) required opt-in for IDFA access. IDFA opt-in rates fell to 20-30% industry-wide, making device-level attribution unreliable for most campaigns. SKAN became the primary privacy-preserving alternative.

SKAN 4 limitations. Apple iterated SKAN through versions 1-4, with SKAN 4 adding hierarchical conversion values and crowdAnonymityLevel. Despite improvements, SKAN 4 had significant measurement gaps: limited post-install event granularity, no re-engagement measurement, delayed reporting windows of up to 35+ days, and complex MMP integration requirements.

AdAttributionKit (2024). Announced at WWDC 2024 for iOS 17.4+. AAK is not an incremental SKAN update — it is a new framework with new APIs, designed to address the structural limitations that SKAN accumulated over multiple versions.

Migration timeline. SKAN support continues in iOS alongside AAK. Apple has not announced a formal SKAN deprecation date as of mid-2025. The practical migration timeline depends on MMP support, ad network integration, and iOS version adoption — advertisers can run AAK and SKAN campaigns in parallel during the transition.

Key concepts and mechanics

Signed impression. When a user sees an ad on iOS, the ad network generates a signed impression — a cryptographically authenticated record that associates the ad impression with a specific ad campaign (without identifying the user). This signature is what enables attribution after an install.

Conversion value. After install, the app updates the conversion value — a numerical representation of post-install user behavior (purchase events, ARPDAU thresholds, revenue buckets) — during the measurement window. AAK's expanded conversion value capacity allows more granular behavioral segmentation than SKAN's 6-bit value.

Measurement window. There are multiple measurement windows for post-install activity. Early windows (activity in the first 24-48 hours) provide faster feedback; later windows (activity in days 3-35) provide more complete behavioral data. Reports are sent after each window closes.

Re-engagement tokens. New in AAK: the framework supports attribution of re-engagement events, not just installs. A user who was previously inactive clicks a deep-linked ad, re-opens the app, and performs an action — AAK can attribute this sequence without identifying the specific user.

Privacy threshold. Like SKAN, AAK applies a privacy threshold: attribution data is only reported if enough installs from a given campaign cleared the threshold (i.e., the campaign reached sufficient scale to protect individual users from identification). Below-threshold campaigns receive null reports.

What this means for iOS campaign measurement

Better post-install event measurement. The expanded conversion value capacity means advertisers can map more purchase events, revenue buckets, and behavioral milestones onto the conversion value schema. This produces more actionable optimization signals for ad networks and bidding algorithms.

iOS retargeting becomes measurable. Before AAK, re-engagement campaigns on iOS had no privacy-preserving measurement path — advertisers relied on SKAdNetwork for installs but had no equivalent for re-engagement. AAK's re-engagement support makes iOS retargeting campaigns measurable within the privacy framework.

MMPs need to re-integrate. AdAttributionKit is not backward-compatible with SKAN at the integration level. MMPs (AppsFlyer, Adjust, Branch, Singular, etc.) each need to release AAK SDKs and documentation, and advertisers need to update their app SDK integrations. Check your MMP's documentation for AAK support status before migrating.

Ad network adoption varies. Major ad networks (Meta, Google UAC, TikTok, Apple Ads) are at different stages of AAK support. Verify that the networks you use support AAK before running AAK-only campaigns. SKAN fallback is available for networks that haven't adopted AAK yet.

Setting up AdAttributionKit

The integration process involves three parties: the advertiser's app, the ad network, and the MMP.

App side. The app must be updated to include the AAK API calls that initialize re-engagement measurement, update conversion values as user events occur, and handle the deeper callback structures that AAK supports. This typically requires an update to the MMP SDK version that supports AAK.

MMP side. The MMP SDK update handles the AAK integration for standard events. Work with your MMP's migration guide — the conversion value schema mapping is a critical configuration step that determines how post-install events are encoded and reported.

Ad network side. The ad network registers with Apple as an AAK-compatible network and provides its network ID for use in signed impressions. Networks that are not yet AAK-registered cannot serve AAK-measured campaigns.

Testing. Apple provides a testing environment for AAK that allows verification of the integration without waiting for real attribution windows. Use this before launching live campaigns with AAK measurement.

Common mistakes

• Conflating AAK and SKAN integrations. The APIs are different; AAK cannot be set up by simply updating a SKAN schema. Treat it as a new integration project with its own SDK updates, conversion value mapping, and QA process.
• Not verifying MMP and ad network support before migration. AAK only works when both the MMP and the ad networks you use support it. Running AAK campaigns to an unsupported ad network results in no attribution data.
• Ignoring conversion value schema planning. The expanded conversion value capacity in AAK is only useful if the mapping is planned correctly. Work with your MMP to define which post-install events and revenue buckets map to which values before going live.
• Expecting immediate data completeness. Like SKAN, AAK has measurement windows and privacy thresholds that mean attribution data arrives delayed and may be incomplete for low-volume campaigns. Plan reporting cadences around these delays, not against real-time expectations.

FAQ

Does AAK replace SKAN completely? Not immediately. Apple has not deprecated SKAN as of mid-2025. AAK runs in parallel with SKAN, and some ad networks and use cases will remain on SKAN during the transition period. The direction is clear — AAK is the forward-looking framework — but full industry migration will take time.

How does AAK interact with App Tracking Transparency (ATT)? AAK, like SKAN, operates without requiring ATT opt-in. It is Apple's privacy-preserving alternative for cases where ATT consent is not obtained. Users who do grant ATT consent can still be measured with more granular (non-aggregated) attribution methods; AAK is the fallback for the majority of iOS users who don't opt in.

Which ad networks currently support AdAttributionKit? Support is actively expanding. Apple Ads, Meta, and Google are the highest-priority networks given their iOS install volume. Check each network's developer documentation for current AAK support status — network adoption is moving faster in 2025 than SKAN adoption did in 2021.

How do AAK conversion values compare to SKAN? SKAN 4 used a 6-bit "coarse value" (low/medium/high) plus a 6-bit "fine value" (0-63), totaling 64 possible states with hierarchical reporting. AAK uses a higher-capacity value structure that allows more granular post-install behavioral mapping. The exact technical specification was detailed in Apple's WWDC 2024 session and MMP documentation; implementation details require reading the current AAK developer documentation.

Should I prioritize AAK migration or other iOS measurement improvements? Prioritize AAK migration if you have significant iOS ad spend and your primary MMPs and ad networks have released AAK support. The re-engagement measurement capability alone justifies migration for advertisers running iOS retargeting campaigns. For advertisers primarily running CPI install campaigns to already-integrated SKAN networks, migration can proceed on a less urgent timeline while waiting for full network adoption.