Skip to content
AppDues
Log in
Contact salesSign up

Integrate In-App Purchases and Revenue Data with Branch

Attribution identifies the campaign that brought a user in; subscription data shows whether that user converted from a trial, renewed, or cancelled.

A Branch integration pairs these two views so campaign performance can be evaluated against actual subscription outcomes on iOS and Android. The documented setup is a prebuilt connector, meaning the work is configuration rather than custom event plumbing. Campaign values can also travel back as Subscriber Attributes, which the platform documentation describes as usable in charts, downstream analytics, APIs, and webhooks.

Why joining attribution and subscription data matters

Install counts alone do not show whether a campaign produced paying subscribers. Three practical outcomes follow from linking the two datasets:

  1. Campaign-level subscription tracking. Subscriptions generated from Branch campaigns can be tracked accurately, so spend can be judged against subscription outcomes rather than installs alone.
  2. Conversion and renewal visibility without an app open. Trial conversion and renewal data can be captured even when the app is not open, which matters because renewals often happen days or weeks after the last session.
  3. Long-tail cohort analysis. Campaign performance can be followed across the entire lifetime of a cohort, not just the first days after install.

Campaign fields that become Subscriber Attributes

Branch supplies campaign context as a set of named values. Each value corresponds to a Subscriber Attribute, which gives you a repeatable way to segment subscription records by acquisition source. The table below sets out every field, its identifier, and the meaning it carries.

Setup checklist

The following sequence can serve as a planning outline, separating app-side work from dashboard configuration. Treat each item as a verification step rather than a guaranteed outcome, and confirm current requirements in the official documentation before relying on any of them in production. First, check that the Branch SDK is present and that campaign values resolve correctly in both iOS and Android builds. Next, enable the Branch integration in the subscription dashboard and connect the two accounts. Then verify that trial starts, subscriptions, and cancellations reach Branch. Confirm that campaign values arrive as Subscriber Attributes on user records, and check that those attributes appear where you expect them — in charts, in downstream analytics, or through APIs and webhooks. Finally, run a test cohort through a known campaign and compare the recorded attribute values with the campaign you targeted. For exact configuration steps and any account-level prerequisites, consult the official Branch integration documentation linked from this page.

Worked example: reading a cohort through campaign fields

Consider a paid campaign served from a media source recorded as $mediaSource, under a campaign identified by $campaign, within an ad group identified by $adGroup, targeting a paid keyword $keyword, and using a specific creative $creative. A user installs from that ad, begins a trial, and later converts. Because the campaign values were attached as Subscriber Attributes, subscribers can be grouped by $campaign and trial conversion compared across ad groups. If one ad group converts strongly in week one but renewals trail by month two, a cohort view spanning the campaign's lifetime exposes that gap. Without the attribute link, the installs would sit in Branch and the renewals in the subscription platform, with no straightforward way to join them. This scenario illustrates how the fields combine; real results depend on your campaign structure and subscription behavior.

ConfigureTargetTest
Branch campaign fields and their Subscriber Attribute identifiers
Campaign fieldIdentifierWhat it describes
Media Source$mediaSourceWhich media source the campaign was served from
Campaign$campaignThe campaign the user came from
Ad Group$adGroupThe ad group the user came from
Keyword$keywordIdentify the paid keywords
Creative$creativeUse to differentiate ads

Field names and identifiers are reproduced exactly as supplied; confirm current naming in the official documentation before configuring.

Frequently asked questions

Which platforms does the Branch integration support?

Subscription events sync from both iOS and Android.

Which subscription events are sent to Branch?

Trial starts, subscriptions, and cancellations are the event types described for this integration.

Do renewals require the app to be open?

No. Trial conversion and renewal data can be captured even without an app open, which is important because renewals frequently occur outside an active session.

How can the campaign data sent to the subscription platform be used?

Campaign values arrive as Subscriber Attributes. They can be used in Charts, sent to other downstream analytics integrations, and are available via APIs and webhooks.

How long does setup take?

The integration is prebuilt, so the work is configuration rather than custom development. Actual time depends on your app's existing Branch setup and how many platforms you support. Follow the official documentation for the exact steps.