attribution-sanity-checklisted
Install: claude install-skill ua5er/user-acquisition-skills
# Attribution sanity check
Finds out which number to believe before money is moved on it.
## When to use
- Platform ROAS and backend revenue disagree.
- After an iOS, SDK, funnel or checkout change.
- Before building dashboards or automation on top of attribution data.
- When moving from app-install buying to a web funnel with server-side events.
## Inputs
1. Four views of the same period if they exist: ad platform report, MMP report (AppsFlyer, Adjust, AppMetrica or similar), SKAN postbacks or the MMP's SKAN view, and backend payments (Stripe, RevenueCat, Adapty, store reports).
2. The event map: which events fire where, with names, and which one the platform optimises for.
3. Funnel type: app install, web to app, or web only.
4. Recent changes: SDK versions, pixel or Conversions API changes, checkout changes, consent flow changes.
## Method
### Step 1. Anchor on the backend
Backend payments are the source of truth for money. Everything else is a model of it. Write the backend totals first: payers, revenue, refunds.
### Step 2. Reconcile, layer by layer
Build one table with a row per layer and columns: count, revenue, difference to backend, difference explained, difference unexplained.
1. Platform vs backend (payments).
2. MMP vs backend.
3. SKAN vs MMP for iOS install campaigns (expect gaps, conversion value and privacy thresholds hide some data).
4. Pixel vs Conversions API vs backend for web funnels (look for double counting and missing deduplication keys).
##