Persona mapping
Last updated on 03/04/2024
Persona mapping
Overview
Digital marketers put significant effort into creating "personas," which are fictional, generalized profiles of ideal customers. These personas are crafted based on target audience demographics, behaviors, motivations, and goals. However, a common challenge marketers face is the lack of sufficient data to accurately match a visitor to a persona.
Visuel.ly addresses this challenge by transforming every visual story interaction into an opportunity to progressively gather more information about the user, allowing for precise persona mapping. By explicitly asking users for details—such as their roles, goals, concerns, top priorities, and content preferences—at the end of the story, marketers can collect the data needed to accurately assign visitors to the appropriate personas.
Gather Persona Data
To create an Ask for visitor feedback follow the process outlined below.
Define the question and answers: Start by deciding on the question you want to ask visitors and persona data you want to collect.
Create question: Add the question at the top of the scene using a Text Layer. Optionally, add a subtitle to the main question using another Text Layer.
Add answers: Use Text Layers to create the response choices for each of data fields you need to map a persona. Style these choices according to your preferences.
Add Select Actions: Attach a Select Action to each of the answers. Configure each Select Action as follows
Is Required: Check the box to make the field mandatory, ensuring users provide the necessary information.
Selection type: Decide whether you want the response to be Single Choice or Multiple Choice.
Selection name: Use selection names to group selections; these can be anything you choose.
Selection value: Ensure each response has a unique value that corresponds to answer choices.
Conversion: Decide if you want to tag it as partial or final conversion
Add a Submit Layer: Below the last Select Action, add a layer with a Submit Action.
Then you are done!
Notes:
You can end the story with "asks" spread across multiple scenes, so there's no need to request too much information in a single scene. This approach helps increase the likelihood of users providing the information.
Learn more in: