Send subscription events to Adjust
Connect subscription lifecycle data from your iOS and Android apps to Adjust so campaign reporting can be tied to trials, purchases, renewals, and cancellations.
The integration is designed for teams that want attribution data to reflect what subscribers actually do after install, not only the first app open.
What the integration does
A prebuilt connection can move subscription activity from mobile apps into Adjust in minutes. That makes it easier to compare campaign performance against real subscription outcomes across iOS and Android, including the moments when a trial begins, a subscription starts, or a subscriber cancels.
Why teams connect the two systems
Three reporting improvements are central to the setup. First, subscriptions attributed to Branch campaigns can be tracked more precisely. Second, trial conversion and renewal signals can be captured even when the app is closed, reducing dependence on an active session. Third, campaign performance can be followed across the full life of a cohort, which is useful when value develops long after the initial click.
A practical setup checklist
Before enabling the integration, confirm these items: the iOS and Android apps are sending subscription events correctly; Adjust is ready to receive those events; the attribution fields you care about are mapped consistently; and reports will distinguish install-time campaign data from later trial, renewal, and cancellation activity. This check helps prevent a common mismatch where campaign reporting looks complete but subscription outcomes are missing or delayed.
Bring campaign data back for analysis
Campaign information can also flow back for analysis. Subscriber Attributes provide a place to attach attribution values to a user, after which those values can appear in Charts, move to downstream analytics tools, or be retrieved through APIs and webhooks. The five fields below cover the main levels of campaign detail.
Attribution fields to store
Media Source ($mediaSource) identifies which media source served the campaign. Campaign ($campaign) records the campaign the user came from. Ad Group ($adGroup) identifies the ad group. Keyword ($keyword) captures paid keywords. Creative ($creative) helps differentiate individual ads. Together, these fields let reporting move from broad channel performance down to the specific ad and keyword that produced a subscriber.
Example use case
PhotoRoom is presented as an example of a team using the Adjust connection to get a fuller view of advertising investment and to look for acquisition opportunities in South Asia. Use that example as a starting point for questions about your own markets: which campaigns produce trials, which produce paying subscribers, and which cohorts retain value over time.
Related integrations
Adjust sits alongside other attribution and analytics tools such as Apple Search Ads, Singular, Branch, SplitMetrics Acquire, Meta Ads, Tenjin, and AppsFlyer. The right choice depends on which attribution platform already receives your campaign data and which downstream reports your team uses for subscription performance.
| Field | What it identifies | Use it to check |
|---|---|---|
| $mediaSource | Media source that served the campaign | Whether channel-level reporting matches the intended source |
| $campaign | Campaign the user came from | Which campaign produced trials and subscriptions |
| $adGroup | Ad group the user came from | Which ad group drives subscriber quality |
| $keyword | Paid keyword | Which search terms convert to paid subscriptions |
| $creative | Individual ad creative | Which ad variation performs best |
Field names are shown exactly as supplied in the source units.
Frequently asked questions
What subscription activity is forwarded to Adjust?
The prebuilt connection forwards subscription lifecycle activity from iOS and Android apps to Adjust, including trial starts, new subscriptions, and cancellations, so attribution platforms can reflect revenue events without waiting for an app session.
Can Adjust campaign details be stored for later analysis?
Campaign context can travel in the opposite direction. Subscriber Attributes let you store media source, campaign, ad group, keyword, and creative values on a user, then use those values in Charts, downstream analytics integrations, APIs, and webhooks.
Why send server-side events instead of relying only on in-app tracking?
Server-side subscription data can capture trial conversion and renewal information even when the app is not open, which helps keep cohort and campaign reporting closer to actual subscription outcomes.