�۶���Ƶ

Personalization syntax personalization-syntax

Personalization in Journey Optimizer is based on the templating syntax called Handlebars.
For a complete description of the Handlebars syntax, refer to .

It uses a template and an input object to generate HTML or other text formats. Handlebars templates look like regular text with embedded Handlebars expressions.

Simple expression sample:

{{profile.person.name}}

where:

Syntax general rules general-rules

Identifiers may be any unicode character except for the following:

Whitespace ! " # % & ' ( ) * + , . / ; < = > @ [ \ ] ^ ` { | } ~

The syntax is case sensitive.

The words true, false, null and undefined are only allowed in the first part of a path expression.

In Handlebars, the values returned by the {{expression}} are HTML-escaped. If the expression contains &, then the returned HTML-escaped output is generated as &. If you don’t want Handlebars to escape a value, use the “triple-stash”.

Regarding literal functions arguments, the templating language parser does not support single unescaped backslash (\) symbol. This character must be escaped with an additionnal backslash (\) symbol. Example :

{%= regexGroup("abc@xyz.com","@(\\w+)", 1)%}

Profile

This namespace allows you to reference all the attributes defined in the profile schema described in �۶���Ƶ Experience Platform Data Model (XDM) documentation.

The attributes need to be defined in the schema before being referenced in a Journey Optimizer personalization block.

Sample references:

{{profile.person.name.fullName}}

{{profile.person.name.firstName}}

{{profile.person.gender}}

{{profile.personalEmail.address}}

{{profile.mobilePhone.number}}

{{profile.homeAddress.city}}

{{profile.faxPhone.number}}

Audiences perso-segments

Learn how to leverage profile attributes in conditions in this section.

Offers offers-syntax

This namespace allows you to reference existing offers decisions.
To reference an offer you need to declare a path with the different information that define an offer.

This path has the following structure:

offers.Type.[Placement Id].[Activity Id].Attribute

where:

For more information on Decisions API and on Offers Representation, refer to this page

All the references are validated against Offers Schema with a validation mechanism described in this page

Sample references:

Helpers helpers-all

A Handlebars helper is a simple identifier that may be followed by parameters.
Each parameter is a Handlebars expression. These helpers can be accessed from any context in a template.

These block helpers are identified by a # preceding the helper name and require a matching closing /, of the same name.
Blocks are expressions that have a block opening ({{# }}) and closing ({{/}}).

Literal types literal-types

�۶���Ƶ Journey Optimizer supports the following literal types:

URL Personalization perso-urls

Personalized URLs take recipients to specific pages of a website, or to a personalized microsite, depending on the profile attributes. In �۶���Ƶ Journey Optimizer, you can add personalization to URLs in your message content. URL personalization can be applied to text and images, and use profile data or contextual data.

Journey Optimizer allows you to personalize one or several URLs in your message by adding personalization fields to them. To personalize a URL, follow the steps below:

Sample personalized URLs