Driving product adoption

Set up a Milestone on the Path: say what "done" means, optionally write a Nudge and a Celebration, turn it On, and read the lift.

See Adoption for the model.

Before you start

Events need to be flowing. A Milestone is defined over your own event or trait, from the snippet, the mobile SDK, or your backend.

1. Open the Path

Go to Engagement → Adoption. This is not under Settings. Settings → Workspace → Analytics is only Active users and activation events.

Click to add a Milestone, or open an existing one.

2. Say what "done" means

Pick the event (for example report_run) or trait that means the person finished. Give it a name a teammate will recognize.

You can stop here. A just-track Milestone still measures who finished.

3. Write letters (optional)

Open the Adaptive Journey on the Milestone.

• Nudge — they have not finished when the clock runs out
• Celebration — they finished

Publish the journey. Nudges are marketing-class, so they respect opt-out and frequency caps.

4. Turn it On

On the Path, turn the Milestone On for Production, Beta, or Dev. Off means you are not measuring that environment yet.

Drag to put it in sequence with the rest of the Path.

5. Read the lift

On Engagement → Adoption each Milestone shows who is not yet done, who finished, and lift versus the holdout. If lift sits at zero, the Nudge is not helping: rewrite the letter or turn the Milestone off.

Next steps

• Adoption — Path, just-track, Nudge, Celebration
• Building your first journey — author the letters
• B2B SaaS wiring — wire the events that power adoption