Use case

Re-engage inactive users automatically

Model win-back as a journey: a timer transition detects users who have gone quiet, then sends a re-engagement email or survey. Because AscendKit owns the user record and product events, the journey reads real inactivity directly rather than syncing it from a separate automation tool.

How it works

  1. 1. Define inactivity
    Decide what 'went quiet' means for your product and rely on the events you already emit to AscendKit.
  2. 2. Add a timer branch
    In the journey graph, add a timer transition that fires when a user has not produced an activation event within a window.
  3. 3. Send and measure
    Send a re-engagement email or survey at that node and track win-back rate in journey analytics.

FAQ

How does AscendKit know a user is inactive?

It reads the product events you send and uses timer transitions to branch on whether an activation event happened within a window — no external sync required.

Can re-engagement include a survey?

Yes. A journey node can trigger a survey to ask why a user disengaged, with the response attached to their record.

Start with one API key

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

Start free