StoryEditor

What's a Data Story ?

If you develop a meal delivery app you could write the following story: users who placed an order after observing a positive customer review. You will then probably be interested in visualising the geographical areas in which such behaviour is most frequent. This is the role of dimensions. To learn more about dimensions, see the dedicated section.

Create a Story.

To start writing your story, simply click on "Create a Story". In the Lab subscription plan, you can create up to 10 different stories. It can be very handy to have different stories available. For example, you can assign a user behaviour of interest to a story so that you can present it later, for example at a meeting.

The StoryEditor.

The opening of a story initiates the story editor. The upper part of the story editor allows you to define your story as the active story, i.e. the one you will view through the dimensions. The lower part of the story editor allows you to configure your story itself.

A story is built around four functional blocks:

(i) User behaviour

The first two (the cyan blue) blocks invite you to specify the behaviour you would like to observe. This is a kind of description of what you would observe on a video recording.
You may be interested in a specific user experience. In this case, select the option "A Given Journey" in the first block. In the second block, Vespucci will then present you with a list of all the Views or Screens from Segment and invite you to describe the transition from one view to another.  
You may also be interested in a specific action. In this case, select the option "A Given Action" in the first block. In the second block, Vespucci will then present you with a list of all "Track" objects from Segment and invite you to select one of them.

(ii) Behaviour Determinant

The last two blocks are concerned with the determinant (the "driver") of the user behaviour that you have specified through the first two blocks. This involves specifying the content experienced by users adopting the target behaviour.
To do this, the third block lists all the content showed in the target view.

If you are a Segment or an API user, these content elements correspond to the properties of your views and screens. We therefore invite you to fill in and track as many elements as possible in the properties of your views. If you are using the Vespucci SDK, these content correspond to all the elements that make up the user interface and are automatically tracked by Vespucci.

If you are using the Vespucci SDK, these content correspond to all the elements that make up the user interface and are automatically tracked by Vespucci.

The fourth block allows you to specify the value taken by the contents you selected in block 3. When you watched video recordings, identifying content that was the source of a behaviour of interest was relatively easy: you could simply watch the films to identify behaviours that you might not have anticipated yourself. So the editor of our delivery app might be surprised to find that almost no user placed an order when the displayed price was less than 6€. Without videos, you have to rely again on your personal intuition to identify the content behind a certain action. This is a problem because you can't think of everything. That's why the story editor relies on the StoryFinder. The StoryFinder suggests stories you might not have anticipated.