Bento's analytics fundamentally serve to help you make better decisions around:
How to iterate on your guide content
Where to invest in the core product experience to reduce friction
Empowering CS and Sales teams to have more effective conversations
Example questions
What do my users want to do in my product?
Feature to use:
Use CYOA and branching questions to offer users paths that go beyond: "what is your role".
Analytics to look at:
Distribution of users who picked each path
The step completion rate of the paths they picked
So what:
If one path is rarely picked, or has really low completion rates, consider offering a different choice, or wording the option differently
Am I using the right form factor for my users?
Feature to use:
Bento offers a wide range of embedded components like checklists, or you can try a traditional tour.
Run a split test to see high level engagement rates
Analytics to look at:
The "Engagement" stat tells you how many users are completing at least one step of the guide.
It gives you a sense of what portion of your customers are even engaging and how effective the form factor is
So what:
Keep investing in the form factor that gets higher engagement and from there, tweak length and content to get stronger completion rates.
Is the content in my guide effective?
Feature to use:
Content can include text, rich media like screenshots, GIFs and videos, as well as interactive content like branching choices or input fields
The Bento editor has a word count that will dynamically change colors as you approach thresholds.
These thresholds are determined per guide type based on step completion rates we see across our customers' guides
Analytics to look at:
For multistep guides, look at drop-offs in step completion
For announcements, embedded guides, tooltips, CTA clicks also help you understand if people are interested in what you are sharing
So what:
Guides that are too long (>6 steps) are rarely completed so you will see drop-off in the later steps, or steps that are verbose.
Use our GPT-powered editor to make steps more concise and action oriented
If you see users completing steps out of order (bottom of the funnel is larger than the top) this means the important information is at the bottom
Move those steps earlier and you can even push those changes live to users who currently have the guide
Required input steps also often block guide completion
You can make steps optional instead of required
Is this guide making my users take the right actions?
Feature to use:
For any checklist guide, we recommend adding auto-completion to a step. This way when a step is completed you know it is because they actually did the action.
Our split testing functionality allows you to create a hold-out group that doesn't get any guide experiences.
Analytics to look at:
Step completion rate for auto complete steps
Integrate Bento into your product analytics tool (i.e. Amplitude) to tie to feature usage
So what:
Every growth experience should be driving user behavior over time, so if it's not, go ahead and sunset it, or try targeting a specific persona instead of "all users"