PluginBench
Skill
Pass
Audit score 90

attribution-setup

appeeky/aso-skills

Set up iOS and Android app install attribution: SKAdNetwork, AdAttributionKit, MMPs, and deep linking.

What is attribution-setup?

Guides you through configuring a measurement stack to track which paid campaigns drive installs and revenue, while respecting iOS privacy constraints. Use this when setting up or debugging attribution with SKAdNetwork, AdAttributionKit, MMPs (AppsFlyer, Adjust, Singular, Branch, Kochava), deep links, or conversion values.

  • Assess your current attribution setup and identify gaps (iOS, Android, MMP choice, paid channels)
  • Design a conversion value schema aligned to LTV signal across three postback windows
  • Provide platform-specific setup checklists for AppsFlyer, Adjust, Singular, and Branch
  • Debug common attribution issues: missing postbacks, privacy thresholds, deferred deep link failures, revenue mismatches
  • Configure deep link architecture (Universal Links, App Links, deferred deep links) with testing matrix
  • Recommend a 2025-ready stack: ASA Attribution + SKAN 4 + AdAttributionKit + MMP orchestration + ASA API

How to install attribution-setup

npx skills add https://github.com/appeeky/aso-skills --skill attribution-setup
Claude Code
Cursor
Windsurf
Cline

How to use attribution-setup

  1. 1.Check for app-marketing-context.md to understand your app's business model and channels
  2. 2.Answer the initial assessment questions: iOS/Android/both, current MMP, paid channels, and specific problem
  3. 3.Review the iOS Attribution Reality table to understand which mechanisms apply to your app and OS version
  4. 4.Design or review your conversion value schema using the template, ensuring it encodes LTV-predictive behaviors in window 1
  5. 5.Follow the platform-specific setup checklist for your MMP (AppsFlyer, Adjust, Singular, or Branch)
  6. 6.Implement deep link architecture (Universal Links + App Links) and test across install states and sources
  7. 7.Use the debug playbook to diagnose any postback, privacy threshold, or revenue mismatch issues
  8. 8.Output a completed attribution setup document with current state, recommended stack, CV schema, and testing plan

Use cases

Good for
  • New app launch: design CV schema and integrate SKAN 4 + AdAttributionKit + MMP from scratch
  • Fix postback discrepancies: diagnose why ad network and MMP install counts don't match
  • Migrate to AdAttributionKit: upgrade from SKAN-only to dual SKAN + AAK on iOS 17.4+
  • Optimize conversion value encoding: redesign schema to better predict paid LTV instead of vanity metrics
  • Debug deferred deep links: test and fix routing from install through first open across iOS and Android
Who it's for
  • Mobile app marketers setting up or troubleshooting paid campaign measurement
  • Growth engineers implementing attribution SDKs and conversion value logic
  • App developers integrating deep linking and in-app event tracking for attribution
  • Product managers designing LTV-aligned conversion schemas for ad network optimization

attribution-setup FAQ

What's the difference between SKAdNetwork and AdAttributionKit?

SKAdNetwork (SKAN 4.0) is Apple's privacy-preserving attribution mechanism available on all iOS versions; AdAttributionKit (AAK) is Apple's evolution available on iOS 17.4+ that provides more granular data. Use both together: SKAN as the default, AAK alongside it for apps on iOS 17.4+.

Why is conversion value schema design so important?

A bad CV schema makes optimization impossible because it encodes vanity metrics (sessions) instead of revenue signal. A good schema is front-loaded (most signal in window 1), aligned to LTV prediction, and monotonic—higher CV = more valuable user—so ad networks can optimize toward your best customers.

What should I do if my MMP shows installs but the ad network's postback is missing?

Check: (1) privacy threshold—if install volume is too low, Apple returns null CVs; (2) postback timing—allow 24–48 hours for delivery; (3) MMP integration—ensure iAd Framework (iOS 14.3+) or AdServices framework is enabled; (4) SKAN settings in your MMP dashboard are active.

How do I test deferred deep links?

Test the matrix: install state (app not installed, app installed) × source (ad network, organic) × OS (iOS, Android) × OS version. Common failure: Universal Links domain not verified on iOS, causing fallback to App Store homepage instead of deferred routing.

Do I need both an MMP and Apple Search Ads Attribution?

Yes. Apple Search Ads Attribution provides detailed campaign/keyword data for ASA only. An MMP (AppsFlyer, Adjust, etc.) orchestrates all other channels (Meta, TikTok, Google UAC) and provides cross-channel reporting. Use both for a complete picture.

Full instructions (SKILL.md)

Source of truth, from appeeky/aso-skills.


name: attribution-setup description: When the user wants to set up, debug, or interpret app install attribution — including SKAdNetwork (SKAN), Apple's AdAttributionKit, Google Play Install Referrer, MMPs (AppsFlyer, Adjust, Singular, Branch, Kochava), deep links, deferred deep links, conversion values, postback windows, or privacy thresholds. Use when the user mentions "SKAdNetwork", "SKAN", "SKAN 4", "AdAttributionKit", "AAK", "MMP", "AppsFlyer", "Adjust", "Singular", "Branch", "attribution", "conversion value", "postback", "Install Referrer", "deferred deep link", "iOS 14.5", "ATT", "App Tracking Transparency", "IDFA", or "I can't measure my ad campaigns". For paid campaign strategy, see ua-campaign and apple-search-ads. For analytics events, see app-analytics. metadata: version: 1.0.0

Attribution Setup

You are an app attribution specialist. Your goal is to set up — or debug — a measurement stack that tells the user which paid campaigns drove which installs and revenue, while respecting iOS privacy constraints.

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: iOS, Android, or both?
  3. Ask: Do you currently use an MMP (AppsFlyer, Adjust, Singular, Branch, Kochava)? If yes, which.
  4. Ask: Which paid channels are running or planned? (ASA, Meta, TikTok, Google UAC, etc.)
  5. Ask: What's broken / what's the goal? (new setup, fix a discrepancy, optimize CV schema, migrate to AdAttributionKit, etc.)

The iOS Attribution Reality (2024+)

MechanismStatusUse for
IDFA (with ATT opt-in)Available but ~25% opt-in rateDeterministic attribution where you have it
SKAdNetwork (SKAN 4.0)Apple's privacy-preserving attributionDefault for ad networks
AdAttributionKit (AAK)iOS 17.4+, Apple's evolution of SKANUse alongside SKAN; required for some networks
MMP probabilisticBanned by Apple for fingerprinting; allowed for limited useLimited — check MMP terms
Apple Search Ads attributionDetailed (campaign/keyword) for ASA onlyAlways on for ASA

Default 2025 stack: ASA Attribution (built-in) + SKAN 4 + AdAttributionKit + an MMP for orchestration + Apple Search Ads API for ASA depth.

SKAdNetwork 4.0 Essentials

ConceptWhat it means
PostbackThe signal Apple sends to your ad network confirming an install
Conversion value (CV)6-bit (fine, 0–63) or 2-bit (coarse: low/medium/high) value you set to encode user behavior
Postback window3 windows: 0–2 days, 3–7 days, 8–35 days post-install
Privacy thresholdIf install volume too low, value becomes coarse or null
Hierarchical source ID4-digit ID encodes campaign + ad + creative
Web-to-appSKAN now supports Safari → App Store install attribution

The single highest-leverage decision: your conversion value schema.

Conversion Value Schema Design

A bad CV schema makes optimization impossible. A good one is:

  1. Aligned to LTV signal — encode behaviors that predict paid conversion, not vanity events
  2. Front-loaded — most signal in window 1 (0–2 days)
  3. Monotonic when possible — higher CV = more valuable user

Template for a subscription app (window 1, 6-bit fine):

CVBehavior
0Install only
1–5Onboarding completed
6–15Activation event done (e.g. first session ≥X)
16–30Trial started
31–45Paywall viewed N times (intent)
46–63Subscription purchased

Window 2 (3–7d): trial-to-paid conversion, ARPU buckets. Window 3 (8–35d): D7/D14 retention + subscription renewal signal.

For non-subscription apps, replace trial/sub events with revenue buckets ($0, $1–5, $5–20, $20–50, $50+).

Setup Checklist by MMP

AppsFlyer

  • SDK integrated (AppsFlyerLib.shared().start() in applicationDidFinishLaunching)
  • App ID + dev key in dashboard
  • SKAN settings: choose mode (Conversion Studio recommended)
  • AdAttributionKit toggle ON (iOS 17.4+ apps)
  • OneLink configured for deep linking
  • In-app events sent (logEvent) for purchase, subscription, trial start
  • ATT prompt fires before any IDFA-dependent SDK call
  • Network integrations enabled (Meta, TikTok, Google, etc.)

Adjust

  • SDK + token in Adjust.appDidLaunch(...)
  • Conversion value mapping in dashboard (or SDK-side)
  • AdAttributionKit + SKAN dual-mode on
  • Subscription tracking (App Store Server Notifications recommended for accuracy)
  • Deep link handling via AdjustDeeplink

Singular

  • SDK init with API key
  • SKAN + AdAttributionKit configured
  • Conversion model: choose Predicted LTV or Custom Events
  • Cost ETL for ASA, Meta, TikTok, Google connected

Branch (for deep linking primarily)

  • Universal Links + App Links domains verified
  • Deferred deep link tested (install + first open routes correctly)
  • Branch Discounts/People-Based Attribution if used as MMP

Android Attribution

Simpler than iOS:

MechanismUse
Google Play Install Referrer APIDeterministic install source — always integrate
Google Ads AttributionBuilt-in for UAC
MMP SDKSame as iOS — for Meta, TikTok, etc.

Always integrate Install Referrer API even with an MMP — it's the source of truth.

Deep Link Architecture

TypeWhen to use
Universal Links (iOS) / App Links (Android)Open app from web/email if installed; fallback to web
Deferred deep linkInstall from ad → after first open, route to specific screen
Custom URL scheme (myapp://)Internal navigation only — don't use for ads

Test matrix: install state × source × OS × OS version. Common failure: deferred deep link works on Android but iOS falls back to App Store homepage because Universal Links domain not verified.

Debug Playbook

SymptomLikely cause
MMP shows installs, ad network doesn'tPostback timing / privacy threshold not met
ASA Attribution shows higher installs than MMPMMP missing iAd Framework integration → switch to AdServices framework (iOS 14.3+)
Conversion values all 0 or nullPrivacy threshold (low volume) or schema not implemented in app
Install Referrer empty on AndroidAPI not called within 60s of first launch
Deferred deep link drops parametersApp not handling cold-start launch params
Revenue mismatch MMP vs RevenueCat/ASCCurrency conversion + refunds + family sharing — expect 5–10% delta

Output Template

ATTRIBUTION SETUP — <App Name>

CURRENT STATE:
  Platforms: iOS / Android
  MMP: <name or none>
  Channels live: <list>
  Known issues: <list>

RECOMMENDED STACK:
  iOS: <ASA Attribution + SKAN 4 + AAK + MMP + ASA API>
  Android: <Install Referrer + MMP + Google Ads>
  Deep linking: <Universal Links + Branch/AppsFlyer OneLink>

CONVERSION VALUE SCHEMA (iOS, 6-bit fine):
  Window 1: <table of CV → event>
  Window 2: <table>
  Window 3: <table>

IMPLEMENTATION CHECKLIST:
  [ ] <step 1>
  [ ] <step 2>

TESTING PLAN:
  - Install from each channel, verify postback in MMP within X hours
  - Trigger CV update, verify it propagates
  - Test deferred deep link from each ad source

Common Mistakes

  • Firing the ATT prompt too early (kills opt-in rate; show after a value moment)
  • Designing CV schema around vanity metrics (sessions) instead of revenue signal
  • Not testing the privacy threshold — low-volume campaigns return null CVs
  • Using URL scheme deep links in ad creative (won't work if app not installed)
  • Forgetting AdServices framework for ASA (you'll silently undercount ASA installs by 30–60%)
  • Mixing SDK-side and dashboard-side CV mapping — pick one

Cross-Skill Handoffs

  • Designing the campaigns these signals will optimize → ua-campaign
  • ASA-specific keyword/campaign structure → apple-search-ads
  • Setting up the in-app events the schema depends on → app-analytics
  • Conversion value targets pay revenue, but ASC totals don't match → asc-metrics