Unblock your experimentation roadmap
What’s the right form factor for onboarding?
Table of contents
🔬 Hypothesis
Users need multiple sessions to get through onboarding.
- Therefore, ephemeral and pop-up experiences aren’t enough
Your product UI is relatively simple but the “path” to value is more complex.
- Therefore, it would be helpful to create different journeys based on JTBD or use-case
🎯 Metrics to track
Depending on the kind of product and go-to-market strategy, these could be useful metrics:
- Increase in conversion metric (paid, active, etc)
- # steps completed
- Engagement over 2 more more sessions
🔨 How to build with Bento
- Build an inline onboarding checklist. You can build it manually, or use our AI builder
- Build a multistep tour
- Create split test and add these two experiences
- Set test targeting criteria (e.g. only new customers). Bento will handle splitting experiences by account
- Launch
How to build with
Pendo
- Pendo only offers pop-up experiences, so you will need an engineer to build the inline checklist
- Pendo offers split testing at the user level, but we recommend onboarding tests to happen at the account level. You will need your engineers to run 50% of traffic to the native checklist, and 50% to Pendo.
How to build with
Appcues
- Appcues only offers pop-up experiences, product tours are the main onboarding form-factor. Inline checklists outperform by 7x so you will need an engineer to build one.
- Appcues deprecated their split testing functionality
How to build with
Chameleon
- Chameleon also only offers pop-up experiences like tours, so you will need an engineer to build the inline checklist
- Chameleon only allows you to A/B test announcements and banners, not tours
