Menu
Sign inGet started
Onboard

Help customers discover their next useful feature.

When your app reports a milestone to Kirora, send the tip your team wrote for the next useful step. Your journey rules decide who gets which suggestion, and a conversion goal tracks who takes the step.

Product adoption
  1. 1Event: “Lesson Completed”
  2. 2Wait 1 day
  3. 3Email a suggestion for the next lesson
  4. 4Conversion goal: “Lesson Started” within 7 days
What’s included

What you’ll use.

  • Triggered by milestones

    Start a journey on any event your app sends, such as Lesson Completed or Report Created, and filter by its details.

  • Segments by behaviour

    Find people who used one feature but never another, how often and how recently.

  • Only when it’s useful

    Skip people who already did it, and take them out as soon as your app reports that they have.

  • Use push or email

    Send push to registered devices with permission, with email as a fallback for eligible contacts.

  • See whether it helps

    Hold some people out at random and compare how many take the next step.

  • Count the next action

    A conversion goal counts the event that follows, such as Lesson Started within 7 days. The ready-made goal Activate new users follows the share of new sign-ups who take your key action.

How it works

How the workflow fits together.

  1. Send the events

    Have your app track the milestones that matter, with the SDK or the API.

  2. Build the journey

    Trigger on the milestone, wait a day, then suggest the next step.

  3. Measure it

    Add a conversion goal for the next action, and a random split with a holdout.

Step by step: Journey results. More use cases: Solutions.

Build your next customer campaign with Kirora.

Create a free workspace, verify your sending domain and import your contacts. Build a campaign or automate a welcome journey, then review it before sending.

See our Acceptable Use Policy, Terms and Privacy Policy.