Skip to main content
Events are facts emitted by Recurr. The exact payloads are scoped during onboarding, but the categories are stable.

​
Event categories

Ascension events belong to the Migration category, not Lifecycle motion. Ascension is migration — the ongoing movement of new store cohorts onto web billing — so its events carry the migration.* prefix and land in the migration funnel alongside the first waves. A destination that buckets them as lifecycle motions will understate migration volume and misattribute the revenue they generate.

​
Event design principles

  • Events should describe what happened, not what a downstream system should do
  • Events should include stable identifiers
  • PII should be minimized to what the destination needs
  • Payment events should reference the payment rail record where possible
  • Access events should reference the customer’s canonical access identifier where possible

​
Migration confirmation

The most important commercial event is migration confirmation. A subscriber is commercially counted once they move to web billing through a Recurr-operated migration and are paying there — read from the web-attribution stamp on the subscription, not from a fixed payment count.