Skip to content
AppDues
Log in
Contact salesSign up

Send in-app purchase events to AppsFlyer

A prebuilt connection moves subscription activity from iOS and Android into AppsFlyer, so campaign reporting can include what happens after install - including trial starts, new subscriptions and cancellations - without building a custom event pipeline.

Decision checklist

Check these points before relying on the data in campaign reports:

  • Confirm trial starts, subscriptions and cancellations are all flowing, not only initial purchases.
  • Verify trial conversion and renewal events arrive even when the app is closed.
  • Check that revenue attributed to a campaign matches subscription revenue, not just install volume.
  • Review a full cohort over time to see long-term value, not only early conversion.
  • Confirm campaign attributes are attached to the correct user before using them in charts or downstream tools.

Sending campaign data back

Campaign information can travel in the opposite direction as well. Subscriber Attributes attach campaign context to a user profile, where it can be used in Charts, forwarded to other downstream analytics integrations, or retrieved through APIs and webhooks. The five fields below form a useful map for deciding how granular a report needs to be.

Campaign field map

Media Source ($mediaSource) - identifies which media source served the campaign. Campaign ($campaign) - identifies the campaign the user came from. Ad Group ($adGroup) - identifies the ad group the user came from. Keyword ($keyword) - identifies paid keywords associated with the user. Creative ($creative) - distinguishes individual ads. Use Media Source and Campaign for budget-level decisions, Ad Group and Keyword for targeting refinement, and Creative for comparing ad variants.

Related attribution tools

The same no-code approach connects real-time events and revenue data to other tools, including Adjust, Apple Search Ads, Singular, Branch, SplitMetrics Acquire, Meta Ads and Tenjin. That makes AppsFlyer one option within a wider attribution setup rather than a standalone reporting silo.

ConfigureTargetTest

Frequently asked questions

Which subscription events are covered?

Yes. Trial starts, subscriptions and cancellations from iOS and Android are included in the events that can be synced.

How is campaign context used after it is sent?

Campaign context can be attached to a user through Subscriber Attributes, then used in Charts, passed to other analytics integrations, or accessed through APIs and webhooks.

Does the integration only work while the app is open?

Trial conversion and renewal information can be captured even when the app is not open, which helps separate install-time activity from later subscription behaviour.