Use case

Lifecycle email without Loops

AscendKit's journey engine sends lifecycle email based on event and timer triggers from your product. Because auth, events, and email share one user record, an onboarding sequence reads real product signals directly instead of syncing them into a separate Loops account.

How it works

  1. 1. Emit events
    Send product events for the moments that matter (signed up, activated, went quiet) through the SDK.
  2. 2. Design the journey
    Build nodes and transitions in the journey graph with event and timer triggers — for example, wait 3 days after signup, then send if not activated.
  3. 3. Measure
    Use journey analytics to see conversion and drop-off per node and iterate on the sequence.

FAQ

How is this different from Loops or Customer.io?

Those tools sit beside your auth provider and need your events synced in. AscendKit owns the user record and events natively, so journeys react to product activity without an integration layer.

What can trigger a journey transition?

Both product events and timers. You can branch on whether an event occurred within a time window, which covers most onboarding and re-engagement flows.

Start with one API key

Auth, email, surveys, and journeys share one user record, so you ship this without stitching vendors together.

Start free