Skip to main content
A destination is a system that receives Recurr data. Destinations are configured during onboarding based on the customer’s stack.

Common destination types

Warehouse

Cohort, subscriber, payment, and lifecycle events for analysis.

Analytics

Migration funnel — including ongoing ascension — plus Oikos motion and cohort reporting events.

Access system

Events that support access continuity in RevenueCat, Adapty, Stripe, Paddle, Firebase, or a custom backend.

Support

Subscriber context for billing, cancellation, refund, and access questions.

Destination setup

For each destination, Recurr and the customer confirm:
  • Endpoint or integration type
  • Authentication
  • Event categories
  • PII handling
  • Retry behavior
  • Test-mode validation
  • Owner and escalation path

Not every customer needs every destination

The pilot should use the minimum destination set needed to run and measure the program safely.