User Profile Variables allow you to save any important piece of information into the User’s Profile in an encrypted way. Profile Variables can be used – like any other kind of variables – as part of the flow in order to personalize the users’ conversational experience.

📘

In addition: This information will be made available in our new Segmentation tool inside of Studio.

When to use?

When saving any piece of information that describes the end user (ie. name, age, gender), their preferences (ie. fav. Soccer team, the best time for delivery, etc.) or any other data point that can be used for better segmentation (ie. size of their store, is a store near a school or office, etc.).

Examples

A simple onboarding

Let’s imagine a simple onboarding process where the user is asked a few simple questions like their name, their age and their email address. Since each one of these answers contains important information about the user, we will save all of them as profile variables. Then, the onboarding process will request the user to accept or decline a notification opt in. We will also save their answer as profile variables.

Profiler

In this activity, stores are asked a couple of questions every time they place an order. As time goes by, we gather the answers to all these questions and can save them into profile variables that can then be used for segmentation.

Future

How does this fit into Segmentation?

Our new Segmentation Engine will allow Studio users to create audiences based on information we have about Stores. Today, this information mostly comes from data shared to us by the customer AND important events that happen inside of commerce.

However, the plan is to make sure, that any user attribute that is saved with Profile Variables, and any user event is that tagged via Event Tracking – both of them in Flow Builder – will also be available for Segmentation.

Take a look at the loom to understand this better.