Integration
Connect paywall journeys to paid outcomes.
DATALYR supports Superwall as a revenue source for subscription measurement. Bring supported lifecycle events into your acquisition workflow, then evaluate how users progress from their initial visit or app activity toward a payment rather than treating paywall exposure as revenue.
Compare plans and usage
A paywall interaction is an intermediate step.
A persuasive paywall can increase interaction without producing retained subscribers. Acquisition teams need to separate exposure, trial behavior and actual payment. They also need consistent user identity across the relevant app and billing events before interpreting differences between campaigns as differences in customer quality. Document the outcome definition with the growth team so paywall changes do not silently change what a conversion represents.
In DATALYR
Superwall Attribution
Paid outcome visibility
Review the subscription events that actually arrive from your Superwall configuration. Choose a payment milestone deliberately rather than treating every paywall or lifecycle event as an interchangeable conversion.
Journey context
Connect supported app activity to the relevant person using the documented identity setup. Investigate where the handoff breaks before assuming a missing campaign means the subscriber arrived organically.
Comparable acquisition cohorts
Use consistent trial windows and reporting dates when comparing campaigns. Keep customer lifecycle behavior separate from acquisition cost so each measure answers a clear business question.
The workflow
From setup to a useful answer.
Connect the source
Follow the Superwall source documentation and confirm the target workspace. Start with a small verification sequence so authentication, incoming events and the expected environment can each be checked independently.
Review identity and events
Inspect the identifiers carried by the integration and the app. Record which supported events represent trials, paid subscriptions or other lifecycle changes before defining marketing conversion rules.
Trace one paid outcome
Compare one subscriber’s sequence against the source records. Validate the payment amount and currency, then inspect the available attribution context before generalizing from individual records to campaign-level performance.
Verify the result
Know what good looks like.
- Superwall activity arrives in the intended workspace and environment.
- The paid outcome is distinguishable from a trial or paywall interaction.
- Subscriber identity connects the expected app and revenue records.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Does this replace paywall experimentation?
No. DATALYR adds acquisition and revenue context to the measurement workflow. Continue using the appropriate experiment system and interpret test results with its assignment rules and statistical limitations.
Can every subscriber be linked to an ad?
No. Attribution depends on available identifiers, permission and recorded touchpoints. Missing evidence should remain visible instead of being filled with an unsupported campaign assignment.
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.
- RevenueCat Attribution ↗
Connect RevenueCat trials, purchases and renewals to acquisition context with DATALYR. Verify subscriber identity and measure app subscription outcomes.
- Subscription revenue attribution ↗
Connect supported subscription revenue sources to DATALYR and distinguish first payments, renewals and refunds in your acquisition analysis.