Personalization Grammar Reference
Two personalization options are available in the Transactional Messaging API set when calling the APIs. Other possibilities are also available at message creation (Dynamic Content, conditional statements).
| Tag name | Purpose | Example |
|---|---|---|
Push Field[EMV DYN]PARAMETER_NAME[EMV /DYN] | Standard field personalization within Templates. The value/pair must be pushed within every API call request. The name of the parameter (either in the HTTP GET or in the XML file) must:
This field does not support any type of HTML tags. These tags can be filled with simple text, numbers, and special characters that are included in the variable. The encoding accepted by Actito is the following:
info The Transactional Messaging Template should have the same encoding as the DYN fields. |
|
Push Content[EMV CONTENT]ID [EMV /CONTENT] | Push blocks of pre-formatted HTML or text content within the API call to use as personalization within the Template. Each block of content can be different per request or recipient (even in the same XML file). A call can include several content blocks. Personalize your messages with pre-calculated matching profile pictures and text pulled from your HTTP GET or in the XML file. This field can also be filled in same way as the Dyn tag, but this tag also supports any type of HTML tags. (To insert HTML into a CONTENT field you need to enclose the HTML code in a |
|