Use case
Measure app acquisition through the paid outcome.
DATALYR supports mobile event collection and subscription revenue connections for app teams. Build a measurement path from available acquisition evidence through product activity and payment, with clear boundaries around permission, missing identifiers and what the recorded journey can establish.
Compare plans and usage
An install alone cannot explain subscriber value.
Mobile acquisition crosses several systems: the campaign, installation, app experience and subscription provider. A high install count may not translate into paying users. Identity and permissions also limit what can be joined, so trustworthy reporting must show incomplete evidence rather than pretending every device journey is fully known.
In DATALYR
Mobile App Attribution
App-event visibility
Collect supported app activity that describes the funnel you want to improve. Keep the event plan focused on meaningful transitions such as onboarding completion and activation instead of counting every interaction equally.
Subscription outcomes
Connect the relevant revenue provider and distinguish trial starts, first payments and renewals. These milestones describe different stages of customer quality and should not be collapsed into a single acquisition conversion.
Honest acquisition coverage
Inspect the identifiers and touchpoints available for each journey. Attribution gaps remain part of the analysis; permission-sensitive or aggregate signals should not be represented as a complete person-level click history.
The workflow
From setup to a useful answer.
Install the supported SDK
Follow the iOS or React Native setup appropriate to the app. Verify initialization and a small set of meaningful events before adding subscription joins or complex marketing rules to the integration.
Connect subscription identity
Use the documented RevenueCat or Superwall setup for your stack. Confirm the same supported identity reaches app and revenue records, including behavior after login or tracking-permission changes.
Verify the complete sequence
Trace onboarding, trial and payment for a controlled journey. Separate test environments from production and compare cohorts only after allowing enough time for the relevant trial and renewal periods.
Verify the result
Know what good looks like.
- Supported app events arrive with the intended environment and identity.
- Revenue records connect to the expected user when evidence permits.
- Trial and paid outcomes remain separate in campaign analysis.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Will this identify every mobile acquisition journey?
No. Available identifiers, permissions and platform reporting limits affect the evidence. Use the documented mobile setup and preserve unattributed activity instead of promising complete cross-device visibility.
Can web-to-app journeys be measured?
Supported identity handoffs can connect recorded web and app activity. Test the precise path your customers use, including login and installation transitions, rather than assuming every anonymous visit can be matched.
Explore related workflows.
- RevenueCat Attribution ↗
Connect RevenueCat trials, purchases and renewals to acquisition context with DATALYR. Verify subscriber identity and measure app subscription outcomes.
- 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.