Attribura iOS SDK

Paste this into Claude Code

It carries your own token and points at the full guide. One paste and the whole setup is done — the steps below are the same thing by hand.

Set up Attribura in this iOS app.

Read https://app.attribura.com/sdk/llms.txt first — it is the complete integration guide.

Then:
1. Add the Swift package https://github.com/martindochamp/attribura-ios
2. Configure it at launch with token "atb_ingest_xxx" and baseURL https://api.attribura.com
3. Declare my onboarding screens in order, and call Attribura.step("…") at the top of each one
4. Build a "How did you hear about us?" sheet and call Attribura.reportSource(…) when the user picks an answer
5. Call Attribura.observePurchases() once, right after configure, and buy through
   Attribura.purchase(product) instead of product.purchase(...)
6. Call Attribura.setUserId(…) as soon as we know who the user is, if the app has accounts

Match this project's existing style and architecture. Show me the diff before applying it.

1 — Install

In Xcode: File → Add Package Dependencies… and paste https://github.com/martindochamp/attribura-ios. Or add it to your Package.swift:

.package(url: "https://github.com/martindochamp/attribura-ios", from: "0.4.0")

2 — Get your token

Copy your ingest token from Settings → Integrations → Attribura SDK. It's the same per-org token the Superwall/Stripe webhooks use, and it's write-only— it can't read your data back.

3 — Configure once

import Attribura

// Once, as early as possible (App init / didFinishLaunching):
Attribura.configure(
    token: "atb_ingest_xxx",
    baseURL: URL(string: "https://api.attribura.com")!,
    // Optional — your onboarding screens, in order. Only needed for the funnel.
    onboarding: ["welcome", "goal", "source", "notifications", "paywall"]
)

Signed in? Your real ingest token is already filled in above — just copy.

That line is also your retention. From 0.4.0, configure reports one app open per install per day by itself, and Overview draws Day 1, Day 7 and Day 28 by install cohort, split by the channel each install came from. Apple has no such report. There is no call to add.

4 — Report the answer

// When the user taps an answer in YOUR sheet.
// No userId needed: the SDK's own anonymous id ties the answer to the purchase.
// Pass one anyway if your app has accounts, or if your paywall provider reports
// its own id (Superwall's app_user_id) and you want both to line up.
Attribura.reportSource(.instagram)

The SDK ships no UI. Here's a minimal SwiftUI sheet you own and wire up:

import SwiftUI
import Attribura

struct HeardAboutUsSheet: View {
    let userId: String
    var onDone: () -> Void

    private let options: [(String, AttributionSource)] = [
        ("Instagram", .instagram), ("TikTok", .tiktok), ("YouTube", .youtube),
        ("A friend", .friend), ("A podcast", .podcast), ("App Store search", .appStoreSearch),
    ]

    var body: some View {
        VStack(alignment: .leading, spacing: 12) {
            Text("How did you hear about us?").font(.title3.bold())
            ForEach(options, id: \.0) { label, source in
                Button(label) {
                    Attribura.reportSource(source, userId: userId,
                                           prompt: "How did you hear about us?")
                    onDone()
                }
                .buttonStyle(.bordered)
            }
        }
        .padding()
    }
}

// Randomize the order once per user so "always tap the first option"
// habits don't skew your data — .shuffled() gives a fresh order each init.
private let options: [(String, AttributionSource)] = [
    ("Instagram", .instagram), ("TikTok", .tiktok), ("YouTube", .youtube),
    ("A friend", .friend), ("A podcast", .podcast), ("App Store search", .appStoreSearch),
].shuffled()

5 — Track the onboarding funnel (optional)

Declare your screens once, in order, in configure(onboarding:) above. Then mark each one as it appears. Attribura records the drop-off, split by the channel each run said it came from — the part a general analytics tool cannot show you, because it never asked the question. Pull it with the get_onboarding_funnel MCP tool or the matching data API endpoint.

// At the top of each onboarding screen.
struct GoalScreen: View {
    var body: some View {
        content.onAppear { Attribura.step("goal") }
    }
}

// As soon as you know who the user is — this attaches the id to the WHOLE run,
// including the steps recorded before sign-in.
Attribura.setUserId(currentUserId)

A step name you did not declare comes back as undeclared, so a typo shows up here rather than as a funnel row that looks wrong weeks later. And if one session can onboard twice — a sign-out that returns to the start — call Attribura.newRun() so the second pass is counted.

6 — Report the money

An answer on its own tells you where people come from. Add this and it tells you what they paid, which is the number the answer was worth asking for. Two lines, and nothing to configure in App Store Connect.

import StoreKit

// 1. Once, right after configure:
Attribura.observePurchases()

// 2. Instead of product.purchase(...) — this is the line that credits the post:
let result = try await Attribura.purchase(product)

Attribura.purchase is the line that matters. It adds the id that answered the question, buys through StoreKit, and reports the sale the moment it succeeds — result is the same Product.PurchaseResult, so your switch over it doesn't change. A plain product.purchase() is not seen by the SDK: Apple hands a purchase made in the app back through its own result, not through observePurchases()'s stream.

Every transaction is forwarded exactly as Apple signed it and checked against Apple's own root certificate before it counts. The SDK never calls finish() on your transactions — only your app knows when it has delivered what was bought.

Two things worth knowing. A renewal or a refund that happens while the app is closed arrives at the next launch, not the moment Apple books it — a first purchase, the one that carries the attribution, is immediate. And if purchases also reach Attribura through Superwall or Stripe, you do not have to unplug anything: once an app reports Apple's own transactions, those become the ones that count, and the webhook stops crediting the same sale a second time.

Sources

Linkable channels — cross-checked against your recent posts:

Dark social — unlinkable, but the traffic every link misses:

How it resolves

A deterministic signal (the campaign token) always wins — a survey answer never overrides a certified link. Attribution stays confidence-scored and directional, never deterministic.