Skip to content
AppDues
Log in
Contact salesSign up

Connecting Appstack attribution to subscription events

Paid acquisition and subscription revenue usually live in separate dashboards. This integration closes that gap: Appstack supplies campaign attribution, the subscription platform supplies lifecycle events, and the two are joined per subscriber so you can see which campaigns produce paying subscribers rather than just installs.

What the integration connects

Appstack is an ad attribution platform used by subscription app developers to see which campaigns drive lifetime value. The subscription platform handles subscription state. The integration has two halves that can be adopted independently:

  • SDK attribution mapping — one call pulls attribution data from the Appstack SDK into the subscription platform and refreshes offerings before your paywall renders.
  • Subscription lifecycle forwarding — an optional webhook sends subscription events back to Appstack so campaign reporting reflects revenue, not only installs.

You can use the SDK mapping alone to tag subscribers with campaign data. Enable the webhook when you want Appstack to report subscription revenue and LTV per campaign.

Before you start

The Appstack SDK must already be installed in your app; follow Appstack's own developer documentation for the current installation steps. On the subscription platform side, configure the Purchases SDK first, then set attribution attributes before the first purchase occurs. For webhook forwarding you also need your Appstack webhook URL and an authorization header, entered in the platform dashboard under Integrations → Attribution → Appstack.

Step 1: Map attribution with one SDK call

setAppstackAttributionParams() reads attribution parameters from the Appstack SDK and forwards them to the subscription platform. It sets the $appstackId subscriber attribute, campaign attributes ($mediaSource, $campaign, $adGroup, $ad, $keyword), click IDs, and device identifiers. Because device identifiers are included, you do not need a separate collectDeviceIdentifiers() call.

The call also syncs attributes to the subscription platform backend and fetches fresh offerings before it returns. By the time your callback runs, the offerings reflect the user's Appstack targeting data, so you can present the matching paywall immediately.

A minimal Swift flow looks like this: import AdSupport, configure Purchases with your public SDK key, read AppstackAttributionSdk.shared.getAttributionParams(), then await Purchases.shared.attribution.setAppstackAttributionParams(attributionParams) and use the returned offerings. Handle the thrown error path. After this, the platform begins storing attributed subscription revenue information from Appstack.

iOS caveat: App Tracking Transparency

On iOS 14.5 and later, if you request App Tracking Transparency permission to access the IDFA, call setAppstackAttributionParams() a second time after the customer grants permission, passing the latest parameters from AppstackAttributionSdk.shared.getAttributionParams(). The AdSupport framework is required to collect the IDFA. Skipping the second call means the post-consent identifiers never reach the subscription platform.

Step 2: Forward subscription lifecycle events

When event forwarding is configured, the subscription platform uses a reserved subscriber attribute to associate its events with the matching Appstack user. The forwarding contract, as documented at the time of the original announcement, is summarized in the capability table below. Configure the webhook in the platform dashboard under Integrations → Attribution → Appstack using your Appstack webhook URL and authorization header.

Once active, the platform forwards the full event suite: Initial Purchase, Renewal, Cancellation, Uncancellation, Non-Renewing Purchase, Subscription Paused, Expiration, Billing Issue, Product Change, Transfer, and Subscriber Alias. That lets Appstack report subscription revenue and LTV per acquisition campaign instead of stopping at top-of-funnel installs.

Decision checklist

  • Only need campaign tags on subscribers? SDK mapping alone is enough.
  • Need revenue and LTV per campaign in Appstack? Enable webhook forwarding.
  • Using IDFA on iOS 14.5+? Plan the second setAppstackAttributionParams() call after ATT consent.
  • Seeing missing device identifiers? Check that AdSupport is linked and the post-consent re-call happens.
  • Seeing no events in Appstack? Verify the webhook URL and authorization header in the dashboard's Attribution section.
  • Seeing duplicate device-identifier work? Drop the separate collectDeviceIdentifiers() call; the mapping call covers it.

What the mapping call sets and fetches

ItemTypeSet or fetched by setAppstackAttributionParams()
$appstackIdsubscriber attributeset
$mediaSourcecampaign attributeset
$campaigncampaign attributeset
$adGroupcampaign attributeset
$adcampaign attributeset
$keywordcampaign attributeset
Click IDsidentifiersset
Device identifiersidentifiersset (no separate collectDeviceIdentifiers())
Offeringspaywall configfetched fresh before return
Backend attributessubscription management platform backendsynced

Availability

At the time of the original announcement, the integration was described as live on the iOS and Android SDKs and available to all apps from the Attribution section of the platform dashboard. Confirm current platform support and dashboard placement in the platform documentation before relying on it for a release plan.

Event forwarding capabilities
Includes RevenueSupports Negative RevenueSends Sandbox EventsIncludes Customer AttributesSends Transfer EventsOptional Event Types
✅✅❌❌✅❌

Capabilities as documented at the time of the original announcement. Verify against current subscription platform documentation before relying on any cell for a production decision.

Frequently asked questions

What is Appstack?

Appstack is an ad attribution platform used by subscription app developers to get clearer visibility into which campaigns actually drive lifetime value.

Do I need to call collectDeviceIdentifiers() as well?

No. setAppstackAttributionParams() already sets device identifiers, so a separate collectDeviceIdentifiers() call is redundant.

Why call setAppstackAttributionParams() twice on iOS?

If you request ATT permission to access the IDFA, the first call runs before consent. Call it again after the customer grants permission with the latest parameters from AppstackAttributionSdk.shared.getAttributionParams() so the post-consent identifiers reach the subscription platform.

Is webhook forwarding required?

No. SDK attribution mapping works on its own. Enable webhook forwarding when you want Appstack to report subscription revenue and LTV per campaign, not just installs.