Content personalization

Properties are what your application sends to Product Fruits so that it can differentiate users from one another. However, properties can also be used in your content.

Product Fruits can use the information that is passed through to it in its content. This is used most often in segmentation but, it is useful in many other situations as well. For example: using a user’s first name in a card for personalization purposes, or even in more technical situations like filling in parts of a URL. 

There are two ways to figure out which properties you can use. The best way is by using the debugger. Once launched, consult the User information tab. 

The other way is by accessing the tracked users’ section of your workspace. Once there, the technical name of the property can be seen highlighted in blue.

 

Once you know which value you to use, implementing it is easy. It’s just a matter of encapsulating the property name in double curly brackets. For example, firstname becomes {{firstname}}. So, in the editor, it looks like this: 

Graphical user interface, text, application

Description automatically generated

And then in the tour, it will look like this:



A note for custom properties

The syntax for calling custom properties is slightly different. They’re all still enclosed in curly brackets but they must be prepended by props. For example, when calling the custom property IsVIP, it must be written as: 

{{props.IsVIP}}

This works differently in the rules/segmentation editor. Here don't prepend your custom properties with props.