Skip to content
AppDues
Log in
Contact salesSign up

Subscription Data Integrations: Forwarding IAP Events Where You Need Them

Renewals are easy to overlook until they become the number that decides whether a subscription app is growing.

Getting a reliable feed of trial starts, purchases, renewals and cancellations into the tools a team already uses is the practical first step. This guide explains what subscription-data integrations do, which lifecycle events they can carry, and how attribution partners fit in.

Event map: what can be forwarded

The integration layer can emit near real-time events for the following subscription actions. Use this as a checklist when deciding which destinations need which signals.

Attribution integrations and campaign measurement

Attribution partners are one of the most useful destinations for subscription events. When revenue events are forwarded to an attribution partner, campaign reporting can reflect actual subscription revenue rather than installs alone. That closes the loop between acquisition spend and the revenue it produces, which is the difference between a cost-per-install number and a cost-effectiveness number.

The forwarding is set up through SDK-side attribution integrations, so the revenue events flow from the subscription layer to the partner without a separate export pipeline. The practical benefit is a more complete picture of which campaigns bring in subscribers who renew, not just users who install.

Decision checklist before you wire anything up

  1. List the questions you need answered — churn, revenue, or acquisition cost effectiveness — and map each to the event that answers it.
  2. Decide which destinations need raw events versus aggregated reports; warehouses usually want raw events, marketing tools often want specific actions.
  3. Confirm which lifecycle events your destinations can actually consume: trial start, trial cancellation, initial purchase, renewal, cancellation.
  4. For attribution, confirm the partner is supported through an SDK-side integration before planning the campaign reporting.
  5. Check how near real-time the destination needs to be; a webhook-driven feed is appropriate when same-day visibility matters.
  6. Assign an owner for each destination so a broken feed is noticed before a reporting cycle closes.

Worked example: one subscriber, five events

Consider a subscriber who starts a free trial, converts to a paid plan, renews once, then cancels. The integration layer would emit a trial start, an initial purchase, a renewal and a cancellation, plus a trial cancellation event if the trial itself is cancelled before conversion. Each event carries the subscription context needed to attribute it to a customer and a product.

If that subscriber arrived through a paid campaign, forwarding the purchase and renewal events to the attribution partner lets the campaign report show revenue rather than just the install. The same events sent to an analytics warehouse let the data team calculate churn and lifetime value from the same source of truth.

ConfigureTargetTest

Frequently asked questions

Are integrations the same thing as webhooks?

Integrations are built on top of the webhook mechanism. The webhook layer provides real-time events for subscription actions; the integration layer delivers those events to a specific destination such as an analytics tool or an attribution partner. In short, webhooks are the transport and integrations are the destination-specific connections.

Which subscription events can be forwarded?

The integration layer can provide near real-time events for trial starts, trial cancellations, initial purchases, renewals and cancellations.

Why forward revenue events to an attribution partner?

Forwarding revenue events lets the attribution partner report on subscription revenue rather than installs alone, which gives a more accurate view of campaign cost effectiveness.

How are attribution integrations set up?

Attribution integrations are configured on the SDK side, which enables the subscription layer to forward revenue events to the attribution partner.