Segment your user base in the rigth way.
The subject of user segmentation is vast. To show you why it's important and how you can use it to build better products, we've put together two cases. They are adapted from the experiences of other Vespucci users.
First, let me introduce you to Sam. Sam is product manager for a photo content creation app. He knows that his app is used by very different audiences. Amateur users use his product to enhance their vacation photos. More professional users use his product to highlight items on their drop-shipping sites, while professional photographers use the app as a mini-photo studio on the move.
Let me now tell you about Paul. Paul is in charge of growth for a rather unusual e-commerce platform. It sells and delivers semi-customized meals for pets. These are prepared on the basis of menus compiled from a questionnaire containing information such as the animal's breed, weight and age. Let's find out how Sam and Paul can use Vespucci to segment their user base, and how they can use this segmentation to build better products and extract more value.
Let's find out how Sam and Paul can use Vespucci to segment their user base, and how they can use this segmentation to build better products and extract more value.
Build a better tagging plan.
The first element to consider and possibly adapt is the tagging plan. Let's see how our two PMs went about it. Sam modified the application to quickly learn more from its users. To do this, he included in the onboarding process a succession of views inviting users to describe themselves.
This succession of questions can quickly become a source of friction for users. Some may perceive these questions as intrusive, while others may be bored by a lengthy onboarding process. So be sure to design an engaging interface (you might also consider including a few gamification elements), inviting precise but not personal answers. At the end of this questionnaire, Sam sends an Amplitude event (called "Onboarding Completed") to which he has associated the questions asked during the onboarding as properties. The value associated with each of these properties is, of course, the answer given by the user.
For Paul, the job was easier. In fact, his product already included a whole series of pet-related questions. All he had to do was add a Segment event (yes, Paul uses Segment while Sam uses Amplitude only) entitled "New Pet". This event takes as its properties all the characteristics of the registered pet (weight, breed, age...).