Appy

Attribution

SKAdNetwork and AdAttributionKit

Receive copies of Apple's install postbacks for your iOS app, compare ad networks and campaigns in one place, and set conversion values from the Appy SDK.

How it works

  • When someone installs or re-opens your app after an ad in another app, Apple sends a signed postback to the ad network that showed the ad. With the keys below, Apple also sends a copy of every winning postback to Appy.
  • Appy checks Apple's signature on each postback, stores it once and shows installs, redownloads, re-engagements, conversion values and countries by ad network and campaign (source identifier) on the app page.
  • Postbacks carry no user or device identifier. They reach Appy 24 to 48 hours after the first conversion window closes, and later ones up to 35 days after the install.
  • This is part of the Enterprise plan, with the Appy SDK.

Set up

  1. 1

    Add the App Store ID and bundle ID

    In the dashboard, open your app and enter both in the iOS settings. Apple names the app in postbacks only by its App Store ID, and Appy asks the App Store whether that ID belongs to your bundle ID before it shows any postback.

  2. 2

    Add the Info.plist keys

    Add the three keys below to your app target. Apple uses only the domain, so the value is https://appy.to for every app.

  3. 3

    Update the conversion value

    Call updateConversionValue after the events that matter for your campaigns, for example a sign-up or a first purchase.

Info.plist
<key>NSAdvertisingAttributionReportEndpoint</key>
<string>https://appy.to</string>
<key>AttributionCopyEndpoint</key>
<string>https://appy.to</string>
<key>EligibleForAdAttributionKitReengagementPostbackCopies</key>
<true/>
Swift
Appy.shared.updateConversionValue(12, coarseValue: .medium)
Appy.shared.updateConversionValue(40, coarseValue: .high, lockWindow: true) { error in
    if let error { print("Conversion value not accepted: \(error)") }
}
RuleOtherwise
The fine value is 0-63Nothing is sent; the completion gets invalidFineValue.
iOS 16.1 or newer (AdAttributionKit from iOS 17.4)The completion gets unsupported.
Apple accepts the valueThe completion gets rejected with Apple's message, for example when no postback is waiting.

Only the first conversion window (days 0-2) carries the fine value. The windows for days 3-7 and 8-35 carry the coarse value: low, medium or high. Use lockWindow: true to end a window early and get its postback sooner.

Test

  • On an iPhone with iOS 18 or newer and Developer Mode on, open Settings > Developer > Ad Attribution Testing and send development postbacks for your bundle ID to your developer postback URL.
  • Development postbacks are signed with Apple's development keys. Appy accepts them and counts them separately as test postbacks on the app page.
  • Builds installed from Xcode report the App Store ID 0, so Appy cannot link their postbacks to your app. Use a TestFlight or App Store build.

Who sees the postbacks

  • Postbacks are shown on an app only when the App Store lists the app's bundle ID for its App Store ID.
  • If two Appy accounts register the same App Store ID and bundle ID, neither sees the postbacks until support confirms the owner.
  • Postbacks for an App Store ID are kept even before the app is set up, and appear once the checks pass.

What this does not do yet

  • Ad networks keep receiving their own postbacks and use them for their reporting and bidding; Appy receives copies and does not send postbacks to networks.
  • Conversion values are set from your app code. A conversion value schema managed from the dashboard is planned.
  • The Flutter and React Native SDKs do not expose updateConversionValue yet; call AdAttributionKit and SKAdNetwork from native code there.