Content personalization and placeholders

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 user 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. 

What user properties can you use?

There are two ways to figure out which properties you can use. It's worth noting that at the moment only properties sent through the user information object that it sent to us from your application when Product Fruits is initalized can be used.

Tracked Users section

The best 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.

Debugger

The other way is by using the debugger. Once launched, consult the User information tab. 

Using placeholders

Once you know which value to use, implementing it is easy. You can use these placeholders in various places in Product Fruits.

Syntax

It’s just a matter of encapsulating the property name in double curly brackets.

For example, firstname becomes {{firstname}}. For custom properties, start with props. For example, yourCustomProp becomes {{props.yourCustomProp}}.

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:

Where you can use it

Placeholders don't have to be used just in tours or hints cards but also in other Product Fruits tools. A few examples:

  • dynamic URLs in Life Ring Button or Checklist items
  • dynamic salutation in the Checklist title
  • personalized announcements, URLs in action buttons included