Personalisation folders

In Taxi you can include ESP personalisation tags in your emails without having to manually type in the code. Read more info here

A simple example of this would be something like:

#{{first_name}}

This will be different for each ESP.

Sometime however depending on how your data is structured you may have something like this as your personalisation field:

#{{hotel.booking.firstname}}

But then you could also have something like:

#{{holiday.activities.firstname}}

Or

#{{holiday.booking.flight.firstname}}

Depending on the data you are using there could be multiple instances where you would use a first name variable. These could be part of different data structures which may be used for different types of emails.

This could cause your list of personalisation fields to grow really quickly and potentially become difficult to manage. This is where personalisation folders can help.

In the examples above, holiday, booking and hotel would be the different folders that a user can search through.

On the personalisation page you will see this option in the top right of the screen, next to personalisation groups.

When you click on this, you can enable folders and choose how a nested personalisation structure is defined in your variables.

The separating characters you can choose from are:

. / > - _

When clicking enable you will get an extra field at the top of the page to search through these different folders.

If you have personalisation fields with these labels: hotel.booking.firstname and holiday.activities.firstname then you will see hotel and holiday as the first options in the folders field.

Depending on which one you select it will show you the next relevant part of the personalisation field.

Then you will see all the personalisation fields that live in this folder below, as opposed to a list of all personalisation fields.

This behaviour is mirrored in the editor. In the personalisation dropdown on rich text fields there is the same field to look for personalisation fields in specific folders.

So instead of having a long list of all fields, they can filter personalisation fields that are part of different folders to easily view and select the right fields.

When this is added to the email, Taxi will display the last part of the field e.g. firstname.

If you hover over the field in the rich text field you can see the full label to know what folder this is part of.

When you export, these personalisation will behave the same as they do without folders. Whatever value has been entered in the dynamic content page will be added to the exported HTML.