AdAttributionKit

AdAttributionKit (AAK) is Apple's privacy-preserving attribution framework for iOS apps, introduced in iOS 17.4 (March 2024) as the eventual successor to SKAdNetwork. Like SKAN, it allows ad networks to measure campaign effectiveness — installs and re-engagements — without exposing user- or device-level identifiers, operating outside Apple App Tracking Transparency (ATT) consent entirely.

Origin and relationship to SKAdNetwork

Apple introduced AdAttributionKit in iOS 17.4 initially as a SKAN equivalent for alternative app marketplaces mandated by the EU Digital Markets Act; at WWDC24 (June 2024) it was expanded to cover the App Store and positioned as the future replacement for SKAdNetwork, per Adjust (adjust.com/blog/adattributionkit). Apple abandoned a planned SKAdNetwork 5 in favour of AdAttributionKit; SKAN 5 had been previewed at WWDC23 with re-engagement capabilities that were then carried forward into AAK, according to AppsFlyer (appsflyer.com/blog/mobile-marketing/ad-attribution-kit-wwdc24).

Apple stated AdAttributionKit "builds on the functionality of SKAdNetwork" — retaining SKAN 4 mechanics including three cryptographically signed postbacks, 64 conversion values, fine and coarse conversion values, crowd anonymity, lockWindow, and random postback delays (Adjust, 2024-06-13). AAK and SKAN are interoperable: if an SKAdNetwork impression is triggered, AAK uses the SKAN format as fallback, preventing data duplication. Both can coexist in the same app simultaneously (Adjust, 2024-06-13; Apple Developer WWDC24 session, 2024-06-11).

Core differentiators from SKAdNetwork

AdAttributionKit introduced four capabilities that SKAdNetwork never supported (as of WWDC24):

Cross-store attribution — unlike SKAN which only covers the Apple App Store, AAK includes a "marketplace identifier" in postbacks indicating which app marketplace an install came from, enabling attribution across both App Store and third-party EU alternative marketplaces (Segwise, 2025-06-17).

Re-engagement attribution — ad networks mark ads eligible for re-engagement via eligible-for-re-engagement: true in the impression JSON; if the app is already installed a Universal Link opens it directly rather than routing to the App Store (Adjust, 2024-06-13). Runner-up postbacks are not generated for re-engagements, only for installs (Apple Developer WWDC24 session, 2024-06-11).

View-through attribution — AAK supports three ad display methods: custom-click ads, view-through ads including video, and banner/full-screen listing overlays (SKOverlay and SKStoreProductViewController equivalents). View-through re-engagement is not supported; only click re-engagement (Adjust, 2024-06-13).

Stronger anti-fraud measures — Apple requires ads to be displayed in the foreground and limits the use of timers to end impressions prematurely. Developer mode removes time randomisation from conversion windows, making testing substantially faster than under SKAN (AppsFlyer, 2024-06-13).

AAK postbacks are cryptographically signed by Apple and do not include user- or device-specific data. Apps do not need App Tracking Transparency permission to call AAK APIs (Apple Developer WWDC24 session, 2024-06-11).

WWDC 2025 updates — iOS 18.4 (as-of 2025-06-10)

At WWDC 2025 (9–13 June 2025, session 221), Apple announced five new capabilities addressing longstanding SKAN limitations (Singular, singular.net/blog/wwdc-2025-aak):

1. Overlapping re-engagement windows with conversion tags — before iOS 18.4, only one active re-engagement conversion window was possible at a time. iOS 18.4 allows multiple concurrent re-engagement campaigns to run in parallel, each identified by a "conversion tag" embedded in the reengagementOpen URL parameter of the Universal Link. Enabled by setting EligibleForAdAttributionKitOverlappingConversions: YES in the app's Info.plist. Conversion value updates for a tagged re-engagement use updatePostback(with: PostbackUpdate(conversionTag: tag)) (AppsFlyer, 2025-06-12; Adjust, 2025-06-10).

Branch.io frames conversion tags and cooldowns as partial steps toward multi-touch attribution (MTA) logic within Apple's privacy sandbox — they do not expose multiple touchpoints or enable fractional credit, but allow advertisers to apply MTA-like intent by passing internal context into updateConversionValue() (Apple Developer WWDC25 session via Branch.io, 2025-06-11).

2. Configurable attribution windows — replaces the previously fixed 30-day click-through and 1-day view-through defaults. Advertisers can now set attribution windows per ad network, per interaction type (click or view), or globally via Info.plist; specific interaction types can also be ignored per network. Applies to install conversions only, not re-engagements — Apple's stated reason is that re-engagement ad interactions and conversions happen right after each other with no time gap (Adjust, 2025-06-10; Singular, 2025-06-10). InMobi recommends a 7-day click-through and 1-day view-through as a global benchmark (as-of 2025-06-24).

3. Configurable attribution cooldowns — defines a waiting period per conversion type (install or re-engagement) after a conversion fires, blocking subsequent ad interactions from claiming attribution credit during that period. Example: 6-hour cooldown for installs, 1-hour for re-engagements (Singular, 2025-06-10).

4. Country codes in postbacks — an optional field in AAK postbacks derived from the user's App Store storefront (for App Store installs) or from the signed installVerificationToken (for alternative marketplace installs). Subject to a "super high" crowd anonymity tier — above the existing Tier 3 — meaning only very high-volume campaigns will receive geo data (AppsFlyer, 2025-06-12; Adjust, 2025-06-10).

5. Developer testing tool — iOS 18.4 adds Settings → Developer → Ad Attribution Testing → Development Postbacks, enabling developers to generate postbacks without a live publisher app or ad flow. Test postbacks use the special ad network identifier development.adattributionkit and a zero advertised item ID for Xcode-distributed apps; production attribution data is not affected (DEV Community/ArshTechPro, 2025-06-22; AppsFlyer, 2025-06-12).

WWDC 2026 — no further updates (as-of 2026-06-26)

WWDC 2026 (June 2026) passed without meaningful updates to AdAttributionKit or the ATT framework; Apple Intelligence and AI dominated the agenda. Industry analyst Eric Seufert noted the absence of new disruptive privacy features (Kochava, kochava.com/blog/your-ios-attribution-strategy-2026-reality-check, 2026-06-26).

Ecosystem adoption (as-of 2026-06-26)

AdAttributionKit registers as "negligible" in Kochava's mid-2026 attribution platform data. SKAN 4.0 has only recently reached majority adoption despite being released in October 2022; SKAN 1 and 2 are effectively gone (Kochava, 2026-06-26).

A 2026 Kochava Foundry survey of iOS app marketers found: 27% had not heard of AdAttributionKit at all; only 7% had an active plan and were actively testing its features; 33% had not implemented SKAdNetwork at all; 67% had experienced reporting gaps attributable to SKAN privacy thresholds; only 21% described their iOS attribution understanding as "comprehensive and confident" (as-of 2026-06-26).

The bottleneck for AAK adoption is the publisher side, not advertiser or MMP readiness. Publishers are historically the last to migrate across SKAN version transitions (SKAN 2→3, 3→4, 4→AAK), and until publishers implement a framework version advertisers cannot benefit regardless of SDK support (Kochava, 2026-06-26).

Major ad networks are also building proprietary attribution alternatives outside AAK: Google released Integrated Conversion Measurement; Meta operates AEM and Advanced AEM (see Meta AEM (Aggregated Event Measurement)); TikTok releases more data via Advanced SAN; Snap has an Advanced SAN product. These alternatives may be suppressing ecosystem demand for AAK migration (Singular, 2025-06-10).

All major MMP (Mobile Measurement Partner) platforms — Adjust, AppsFlyer, Branch, Singular, and Kochava — support AAK alongside SKAN 4 as of 2026, with parallel AAK + SKAN 4 reporting available from at least Singular and AppsFlyer (as-of 2025-06-12).

iOS attribution landscape context (as-of 2026-06-26)

Kochava's mid-2026 platform data shows iOS attribution breakdown as: Apple Ads 36%, device-level consented (IDFA) 10%, SKAN 11%, with the remainder via aggregate and modelled approaches. Apple Ads has grown substantially because it remains the only channel where deterministic keyword-to-device association is possible without ATT opt-in (Kochava, 2026-06-26).

ATT consent acceptance has risen substantially: as of 2026, 69.7% of iOS users who are shown an ATT prompt accept it — up from approximately 37% at ATT's 2021 launch; acceptance crossed 50% for the first time in September 2024. However, only 2% of iOS installs are prompted for ATT at all, and 36% of surveyed marketers use only Apple's default system prompt with no custom pre-prompt (Kochava, 2026-06-26).

47% of surveyed iOS app marketers increased their iOS media budgets over the past 12 months; 57% describe iOS as their primary platform driving the majority of high-value users (Kochava, 2026-06-26).

Practitioner experience

Apple Developer Forums (13 posts, 2024-10 through 2026-04) document a recurring failure mode: "Found 0 postbacks eligible for transmission for environments" — the canonical failure when AAK publisher-to-advertiser linking does not connect. Developers consistently report completing every documented step (Info.plist keys, ATS, .well-known endpoints returning 200 OK, Developer Mode enabled) and still receiving nothing. No Apple staff resolution was recorded in any of the 13 threads, suggesting either edge-case environment issues or undocumented requirements (Apple Developer Forums, 2024–2026).

One developer noted in December 2024: "Apple is pushing to use AdAttributionKit, but when I look at various ad networks, their sample code isn't using it" — with zero replies and 467 views (Apple Developer Forums, 2024-12).

A structural technical barrier: existing SKAdNetwork certificates (prime192v1 algorithm) are incompatible with AAK's JWS signing requirement (ES256). Developers must re-register and re-generate keys — old SKAN certs cannot simply be updated (Apple Developer Forums, 2024-10).

AdAttributionKit is not directly compatible with Objective-C as of October 2024; Swift is required. No official Apple documentation acknowledged this limitation as of that date (Apple Developer Forums, 2024-10).

Key terms

Term	Meaning
Postback	Cryptographically signed signal Apple sends to the ad network after a conversion, containing aggregated (non-user-level) attribution data
Conversion tag	Identifier embedded in a re-engagement Universal Link, enabling multiple concurrent re-engagement campaigns to be tracked separately (iOS 18.4+)
Crowd anonymity tier	Apple's privacy threshold system; data fields are suppressed until sufficient install volume is reached for a given combination; AAK adds a "super high" tier for country codes
LockWindow	API call that ends the conversion value update period early, allowing faster postback transmission at the cost of forgoing later in-window conversion signals
Fine/coarse conversion value	SKAN 4 / AAK mechanism: fine = 6-bit value (0–63); coarse = 3-tier (low/medium/high); higher-tier postback windows receive coarser data as privacy protection
Publisher	The app that displays an ad (supply side)
Advertiser	The app being promoted (demand side)
Re-engagement	Attribution for users who already have the app installed, brought back via a deep link ad
Alternative marketplace	Third-party iOS app distribution channel enabled by EU DMA; AAK supports attribution across these in addition to the App Store
MMP	MMP (Mobile Measurement Partner) — measurement platform (AppsFlyer, Adjust, Singular, Branch, Kochava) that sits between ad networks and advertisers to aggregate postback data

Benchmarks (as-of 2026-06-26)

Metric	Value	Source
AAK's share of iOS attributions in Kochava platform	Negligible	Kochava, 2026-06-26
SKAN 4 adoption status	Recently reached majority	Kochava, 2026-06-26
Marketers unaware of AAK	27%	Kochava Foundry survey, 2026
Marketers actively testing AAK	7%	Kochava Foundry survey, 2026
Marketers with no SKAN implementation	33%	Kochava Foundry survey, 2026
ATT opt-in rate (when prompted)	69.7%	Kochava, 2026-06-26
iOS installs receiving ATT prompt	~2%	Kochava, 2026-06-26
Apple Ads share of iOS attributions	36%	Kochava, 2026-06-26
Consented device-level (IDFA)	10%	Kochava, 2026-06-26
SKAN share of iOS attributions	11%	Kochava, 2026-06-26

What practitioners report

From Apple Developer Forums (13 posts, 2024–2026): the dominant practitioner experience is "zero postbacks" despite correct implementation — unclear whether this reflects undocumented requirements, environment-specific issues, or publisher-side absence of AAK support. Reddit signal is near-zero: only 4 posts found across all subreddits, with no discussion in r/ecommerce, r/PPC, r/FacebookAds, or r/GoogleAds. AAK has not yet entered the vocabulary of ecommerce PMs or retail mobile marketers on Reddit; it remains a mobile UA / developer-only topic as of July 2026.