Tenjin In-App Purchases and Revenue Integration
Tenjin tells you which campaigns brought users in.
Subscription revenue tells you what those users are worth. This prebuilt connection passes subscription lifecycle events from iOS and Android into Tenjin, and lets campaign metadata travel the other way into subscriber records — so a trial start, renewal, or cancellation can be read alongside the media source and creative that produced it.
What the connection does
Two directions of data movement are involved, and it helps to keep them separate.
Outbound to Tenjin: subscription events — trial starts, subscriptions, and cancellations — are synced from both iOS and Android. That means Tenjin can attribute subscription activity to the campaigns that generated it, rather than only installs or opens.
Inbound to subscriber records: campaign details from Tenjin are attached to users as Subscriber Attributes. Those attributes can then be used in Charts, forwarded to other downstream analytics integrations, and read through APIs and webhooks.
Why teams pair the two
Three practical reasons come up when attribution and subscription data are joined:
- Precision. Subscriptions that originate from Tenjin campaigns can be tracked accurately instead of inferred.
- Coverage without an app open. Trial conversions and renewals are recorded even when the user has not opened the app, so the measurement window is not limited to active sessions.
- Cohort-level view. Campaign performance can be followed across the full lifetime of a cohort, not just the first days after install.
Before you connect: a short checklist
- Confirm the app is already reporting subscription events through the subscription platform, since the sync forwards those events rather than creating them.
- Decide which campaign dimensions you actually want on subscriber records — every attribute you attach becomes something to maintain, chart, and explain to downstream consumers.
- Check where the attributes will be consumed: in-app charts, a downstream analytics tool, or your own systems via API and webhooks. Each has its own naming expectations.
- Verify the field keys against the setup documentation rather than assuming casing or prefixes.
- Plan how you will distinguish attribution-driven subscriptions from organic ones in reporting, so campaign results are not overstated.
Event sync versus attribute attachment
These are easy to conflate, and the distinction matters when something looks wrong.
Event sync is about activity: a trial begins, a subscription renews, a subscription is cancelled. If those events are missing in Tenjin, the question is whether the event pipeline is delivering them.
Attribute attachment is about identity and context: which media source, campaign, ad group, keyword, and creative belong to a given user. If campaign breakdowns look empty while events arrive fine, the question is whether the attributes were set on the subscriber and whether the downstream tool reads those keys.
Diagnosing the two separately usually shortens the hunt considerably.
Where this fits in a wider stack
Attribution is one input among several. The same subscription event stream can feed other measurement and messaging tools through no-code integrations, so it is worth mapping the full set of destinations before configuring each one individually — otherwise the same event gets defined slightly differently in three places.
Getting started
Setup instructions live in the integration documentation, and the signup flow is the entry point for a new account. If you are comparing attribution providers, the integrations directory lists the alternatives alongside Tenjin.
| Field | What it identifies | Attribute key |
|---|---|---|
| Media Source | Which media source the campaign was served from | $mediaSource |
| Campaign | The campaign the user came from | $campaign |
| Ad Group | The ad group the user came from | $adGroup |
| Keyword | The paid keywords | $keyword |
| Creative | Differentiates ads | $creative |
Attribute keys are shown exactly as they appear in the integration's field descriptions. Confirm current key names and any prefix requirements in the setup documentation before configuring your app.
Frequently asked questions
Which subscription events get sent to Tenjin?
Trial starts, subscriptions, and cancellations, synced from both iOS and Android apps.
Do I need the app to be open for renewals to be recorded?
No. Trial conversion and renewal data is captured even without an app open, which is why cohort performance can be followed beyond active sessions.
Where does the campaign data go once it reaches the subscription platform?
It is stored as Subscriber Attributes on the user. From there it can be used in Charts, forwarded to other downstream analytics integrations, and accessed through APIs and webhooks.
What is the difference between a missing event and a missing campaign breakdown?
A missing event points at the event pipeline — trial starts or renewals not arriving. A missing breakdown points at attribute attachment or at how the downstream tool reads the attribute keys. Checking them separately narrows the cause.