Documentation
Help CenterCommunityDevelopersAcademyStatus

XML Recipient and Content Element Definitions

Detailed information about Recipient and Content Elements

Suggest Edits

Recipient and content elements

  • RECIPIENT
  • EMAIL
  • BODY_TYPE
  • PERSONALIZATION
  • TAG_NAME
  • VALUE

RECIPIENT - This is a required top-level element for defining a mail recipient. At least one Recipient block is required per submission; however, Transact can accept more than one Recipient block per submission that maps to the same Campaign ID.
Use this element when sending in groups of ten or less for best performance by using HTTP Requests.

  • Element type: Complex, Elements
  • Data type: N/A
  • Default Value: N/A
  • Limit: N/A
  • Values: N/A
  • Occurrence indicators: maxOccurs="unbounded" - Values: unbounded= no limit
  • Attributes: None
<RECIPIENT>
	<EMAIL></EMAIL>
	<BODY_TYPE></BODY_TYPE>
	<PERSONALIZATION></PERSONALIZATION>
</RECIPIENT>

EMAIL - This required element contains the email address to which the transactional email is sent (recipient). The sequence for this element is after the RECIPIENT element.

  • Element type: Complex
  • Data type: string
  • Default Value: N/A
  • Limit: 255 characters
  • Values: Text - email address of the recipient.
  • Occurrence indicators: None
  • Attributes: None
    Example:[email protected]

BODY_TYPE - This element is an optional parameter that is used to define if the email is an HTML only or TEXT only email. The sequence for this element is after the EMAIL element.

  • Element type: Complex
  • Data type: string
  • Default Value: HTML
  • Limit: 255 characters
  • Values: HTML and TEXT
  • Occurrence indicators: None
  • Attributes: None

Example: <BODY_TYPE>HMTL</BODY_TYPE>

PERSONALIZATION - At least one personalization block is required for providing the content for the email to be sent. Each Personalization element contains one name-value pair. The sequence for this element is after the BODY_TYPE element.

  • Element type: Complex
  • Data type: N/A
  • Default Value: N/A
  • Limit: N/A
  • Values: N/A
  • Occurrence indicators:
  • minOccurs="1" - Values: 1 = at least one of them is required.
  • maxOccurs="unbounded" - Values: unbounded= (no limit)
  • Attributes: None
<PERSONALIZATION>
	<TAG_NAME>TEXT</TAG_NAME>
	<VALUE>text</VALUE>
</PERSONALIZATION>

TAG_NAME - This required element specifies the name of the personalization string that is used in the body of the mailing template for the mailing. The sequence for this element is after the PERSONALIZATION element.
TAG_NAME elements can appear in any order; they are not sequenced. The order does not have to match the order that is presented in SAVE_COLUMNS in the database.
The XML formatting must be exact. XML tags and fields in can be in lowercase, uppercase, or mixed case, but tags must exactly match the fields that are used in the database. Booleans (true, false) must be in lowercase.

  • Element type: Complex
  • Data type: string
  • Default Value: N/A
  • Limit: 255 characters
  • Values: Tag name of the corresponding field (tag) in the
  • Occurrence indicators: None
  • Attributes: None

Example: <TAG_NAME>FLT_1_TRIP_TITLE</TAG_NAME>

VALUE - This required element specifies the value of the corresponding TAG_NAME element. The sequence for this element is after the TAG_NAME element.
The Transact server does not process any code (logic or transformation) placed in text or CDATA content, including anything inserted by Template fields. If the text contains angle brackets (< or >), you must enclose it within a CDATA section.

  • Element type: Complex

  • Datatype: string

  • Default Value: N/A

  • Limit: 255 characters

  • Values: Any text or CDATA-wrapped HTML, XML, XSL, XHTML, and styles.

  • Occurrence indicators: None

  • Attributes: None

    Example: Atlanta Hartsfield-Jackson ATL (ATL) to Salt Lake City International (SLC)

Updated about 4 years ago