Workflow
Keep renewals connected to acquisition.
Connect supported subscription revenue sources to DATALYR and distinguish first payments, renewals and refunds in your acquisition analysis. Evaluate customer value over time without treating every rebill as a newly acquired customer.
Compare plans and usage
Recurring revenue changes the measurement question.
A campaign may acquire a customer once while that customer pays over several months. Counting every payment as a new customer distorts acquisition cost; ignoring later payments understates observed value. DATALYR supports a subscription measurement workflow that separates acquisition from the subsequent revenue events associated with a customer, using the data available from each connected source.
In DATALYR
Subscription revenue attribution
Separate acquisition from billing
Define the first paid outcome independently from recurring charges. This keeps customer counts and transaction counts useful for different business questions.
Review observed cohort value
Compare customer revenue over an explicit observation period. Younger cohorts have had less time to pay, so they should not be compared as if their full lifetime value were known.
Account for revenue adjustments
Include a clear treatment for refunds and other supported adjustments. Gross collected payments and net retained revenue are different bases for a campaign decision.
The workflow
From setup to a useful answer.
Connect the billing source
Use the documented Stripe, RevenueCat, Superwall or Whop path appropriate to the business. Check which events and customer identifiers the integration supplies.
Agree the revenue definition
Document first purchase, renewal and refund treatment. Choose whether the report measures cash received, recurring state or another supported metric.
Review acquisition cohorts
Compare customers acquired in a defined period with a matched age window. Investigate differences with enough history before using them to set acquisition targets.
Verify the result
Know what good looks like.
- A first payment is distinguishable from a renewal.
- Refund treatment is explicit in the analysis.
- Cohorts use comparable observation windows.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Is observed LTV a prediction of all future revenue?
No. Observed value is based on the history available so far. A forecast introduces assumptions about future retention and payment behavior that should be stated separately.
Are all billing sources identical?
No. Available events, identity fields and revenue semantics differ. Validate the specific source contract instead of treating every integration as an interchangeable ledger.
Explore related workflows.
- Stripe Revenue Attribution ↗
Connect Stripe payments and subscriptions to marketing visits with DATALYR. Preserve checkout identity and separate collected revenue from subscription state.
- RevenueCat Attribution ↗
Connect RevenueCat trials, purchases and renewals to acquisition context with DATALYR. Verify subscriber identity and measure app subscription outcomes.
- Whop Membership Attribution ↗
Connect Whop membership payments with marketing context in DATALYR. Separate new customer acquisition, recurring payments and refunds in your reporting.