Skip to main content
Data teams make the migration measurable. Recurr needs enough signal to select cohorts, compare outcomes, and keep Kairos learning from what happens.

​
Key data questions

  • What subscriber identifier is canonical?
  • Which events define active, paying, cancelled, churned, and recovered states?
  • How are app-store and web subscribers represented today?
  • What engagement signals are useful for cohort selection?
  • Which payment events should feed reporting?
  • Which downstream systems need exports or webhooks?

​
During migration

Recurr measures:
  • Cohort selection
  • Message and checkout funnel
  • Successful web payments
  • Churn signal against comparison context
  • Support signal
  • Refund and dispute patterns

​
After migration

Oikos and Kairos use the connected web-book signal to decide and measure lifecycle motions — acquire, retain, and grow — and to decide when each newer store cohort is ready to migrate. Ascension events belong to the migration family, not the lifecycle-motion family, so migration reporting stays complete as new cohorts move. The public API reference describes event and export contracts where technical teams need them.