Integration
Connect RevenueCat subscriptions to acquisition.
DATALYR receives RevenueCat subscription activity and connects it with the identity your app supplies. Follow the progression from a trial to a first payment and later renewal, while keeping missing campaign evidence visible rather than forcing an attribution answer.
Compare plans and usage
Trial volume can hide subscription quality.
A campaign that starts many trials may produce few paying subscribers. Revenue events alone also cannot reconstruct a missing acquisition handoff. Mobile teams need both lifecycle detail and consistent identity to distinguish promising trial cohorts from traffic that never turns into sustained payment. Keep trial length visible beside each cohort comparison.
In DATALYR
RevenueCat Attribution
Lifecycle separation
Analyze trial starts, conversions and renewals as different milestones. This makes acquisition quality easier to evaluate than a single conversion total that mixes free trials with paying subscribers.
Subscriber context
Pass DATALYR attributes through the documented RevenueCat integration. Check the resulting subscriber record so a purchase can connect to recorded activity rather than remaining an isolated billing notification.
Cohort interpretation
Compare subscription outcomes over equal observation periods. A newer campaign’s customers have had less time to renew, so early revenue should not be compared casually with a mature cohort’s total.
The workflow
From setup to a useful answer.
Connect the webhook
Configure RevenueCat in Sources and supply the webhook secret in both systems. Confirm an authentic event reaches the correct workspace before attempting to explain acquisition performance.
Pass current SDK attributes
Use the documented SDK helper after initialization and follow the guidance for tracking-permission changes. Verify the supported SDK version because older attribute behavior can prevent the intended identity from reaching the server.
Review a subscriber journey
Trace one trial and subsequent paid event with their identifiers. Keep sandbox activity separate, check renewal timing, and compare the revenue definition with the source before building a campaign report.
Verify the result
Know what good looks like.
- The configured webhook authenticates and reaches the intended workspace.
- The subscriber carries a valid DATALYR identity attribute.
- Trial, first payment and renewal are distinguishable in the event history.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Does revenue ingestion guarantee campaign attribution?
No. Revenue can arrive even when the app did not provide the necessary identity connection. Inspect the subscriber attributes and recorded acquisition evidence when payments appear without a campaign.
Can I compare trial campaigns immediately?
You can inspect early funnel behavior, but a fair paid-conversion comparison requires enough time for trials to finish. Use the same conversion window and account for different trial lengths.
Explore related workflows.
- Mobile App Attribution ↗
Connect supported app events and subscription revenue with DATALYR. Verify mobile identity, distinguish trials from payments and inspect acquisition gaps.
- Superwall Attribution ↗
Connect Superwall subscription events with acquisition context in DATALYR. Evaluate paywall journeys, paid outcomes and identity handoffs across your app.
- Subscription revenue attribution ↗
Connect supported subscription revenue sources to DATALYR and distinguish first payments, renewals and refunds in your acquisition analysis.