Personalization fields in HTML templates, content, and links

You can manually define a personalization field in HTML email and landing page templates, and in HTML snippets. You can also define personalization fields in URL link parameters for links added to templates and snippets.

Defining a personalization field tag in a template, snippet, or link is referred to as embedding the personalization field. Embedding a personalization field in a template or snippet avoids the need to separately add the field to each message by using a zone. For URL link parameters, embedding personalization fields in link parameters provides the ability to personalize hyperlinks in email and landing pages. You can also embed personalization fields in text-only email because text-only templates for Deliver are HTML documents. To support embedding personalization fields, Deliver recognizes custom HTML tags and a custom link parameter syntax.

To embed a personalization field in a template or snippet, you must use the custom <UAEpf> tag. This tag is case-sensitive. When you run a mailing that references a document containing this tag, Deliver recognizes the tag as a personalization field and merges recipient or visitor-specific information into the email or landing page that it renders. Embedding personalization fields in link parameters also requires a custom parameter syntax (pf=#pf:PF_NAME#) that is recognized only in Deliver.

Personalization fields that are inserted into the template must be defined as part of a recipient list (an OLT) and the OLT must be referenced by the mailing that references the template where you embed the personalization field. Template designers must coordinate with the email marketing team to ensure that the personalization fields they add to the template are properly defined in Deliver. The name of a personalization field defined in the template is case-sensitive and must exactly match the name that the email marketer assigned to the personalization field in the recipient list.