DATALYR

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.

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.

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.

From setup to answer.

  1. 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.

  2. Agree the revenue definition

    Document first purchase, renewal and refund treatment. Choose whether the report measures cash received, recurring state or another supported metric.

  3. 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.

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.

Questions, answered.

Contact us
  • 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.

  • No. Available events, identity fields and revenue semantics differ. Validate the specific source contract instead of treating every integration as an interchangeable ledger.

Related workflows.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started