Home
Administrator Guides
Transactional Message Administrator Guide
About Deliver and transactional message
A transactional message is a single message sent in response to a specific, predetermined transaction detected in your business systems. Unica provides the Deliver Transactional messaging Service (TMS) as a hosted web service to process transactional messages. Digital marketers work with application developers to integrate corporate transaction management systems with the Deliver TMS.
Using Deliver to send transactional message
Implementing transactional message requires collaboration between digital marketers and application developers. All parties must have a general understanding of the required systems and workflow. Everyone involved must be familiar with the various roles that each contributor plays in the transactional message implementation.
Recipient information for transactional message
To personalize transactional message, you must provide recipient information in the web service request that you send to the Transactional messaging Service (TMS). Unlike other forms of personalized marketing message that you can send through HCL Unica, transactional messages do not retrieve recipient information from an Output List Table (OLT).
Personalization fields used in a transactional message
The local transactional message client identifies each personalization field as a separate name-value pair in the web service request that it submits to the hosted transactional messaging service. The client application must specify the name of each personalization field that is contained in the message. The client must also access the business systems and databases that provide the required personalization values.

Administrator Guides
- Startup and Administrator Guide
- Transactional Message Administrator Guide
  - About Deliver and transactional message
    A transactional message is a single message sent in response to a specific, predetermined transaction detected in your business systems. Unica provides the Deliver Transactional messaging Service (TMS) as a hosted web service to process transactional messages. Digital marketers work with application developers to integrate corporate transaction management systems with the Deliver TMS.
    - Using Deliver to send transactional message
      Implementing transactional message requires collaboration between digital marketers and application developers. All parties must have a general understanding of the required systems and workflow. Everyone involved must be familiar with the various roles that each contributor plays in the transactional message implementation.
      - How transactional message works in Deliver
        Digital marketers use Campaign and Deliver to configure messages and enable messagings for transactional message. Application developers create a transactional message client and integrate it with other business systems.
      - Transactional messaging and standard messaging compared
        Deliver constructs and sends transactional messages differently than it does standard personalized message. During a standard messaging run, the system processes potentially large volumes of individually personalized messages. However, for transactional message, Deliver performs the same personalization operations for multiple web service requests, but each request processes only one message at a time.
      - Message design for transactional message
      - Recipient information for transactional message
        To personalize transactional message, you must provide recipient information in the web service request that you send to the Transactional messaging Service (TMS). Unlike other forms of personalized marketing message that you can send through HCL Unica, transactional messages do not retrieve recipient information from an Output List Table (OLT).
        Personalization fields used in a transactional message
        The local transactional message client identifies each personalization field as a separate name-value pair in the web service request that it submits to the hosted transactional messaging service. The client application must specify the name of each personalization field that is contained in the message. The client must also access the business systems and databases that provide the required personalization values.
        Personalization fields for additional link or contact tracking in transactional message
        If you request that Unica perform additional link or contact tracking, every transactional message request must include the name and value of personalization fields that are used for additional tracking.
      - Global message suppression and transactional message
        Unica Deliver does not apply global email suppressions to transactional message requests.
      - Attachments to transactional email
        The Deliver TMS SOAP service supports attaching files to transactional email messages. TMS REST API does not support attachments to be transmitted as part of request.
    - What digital marketers do for transactional messages
      Using Deliver to send transactional message requires advance preparation and coordination between the digital marketing team and application developers responsible for your corporate transactional systems.
    - What application developers do for transactional message
      Application developers create the local transactional message client that submits transactional message requests to the Unica Deliver Transactional messaging Service (TMS). The local transactional message client application processes each transactional message message by making a REST or a SOAP request to the Deliver TMS over an HTTPS connection.
    - Choosing between REST API and SOAP API
      Unica provides both options of interacting with TMS service using REST or SOAP API.
  - Integration with the Deliver transactional message service
    The Deliver Transactional messaging System (TMS) is a web service hosted as part of HCL Unica hosted services. Application developers must work with digital marketers in your organization to create the client applications required to integrate your corporate transactional systems with the Deliver TMS. These client applications initiate each transactional message by making a SOAP request to the Deliver TMS over an HTTPS connection.
  - Deliver sample TMS client
  - The Deliver Transactional Mailing Service API
    The Deliver Transactional Mailing Service is a web service hosted in HCL Unica. It provides an API that contains one method calledsendMailing.
  - Sample client
    Unica provides sample transactional message clients to guide application developers that create client applications that make web service calls to the Deliver Transactional Messaging Service (TMS). This sample client is based on the second-generation WSDL.
  - About Dynamic Transactional Images
    Dynamic transactional images are images specific to a particular individual that you can include with transactional email messages. Dynamic transactional images are sent as attachments to transactional email but they display as images embedded in the body of the message.
  - Deliver sample TMS client

Personalization fields used in a transactional message

The local transactional message client identifies each personalization field as a separate name-value pair in the web service request that it submits to the hosted transactional messaging service. The client application must specify the name of each personalization field that is contained in the message. The client must also access the business systems and databases that provide the required personalization values.

The messaging that you enable for transactional message must reference a corresponding document. The document provides the structure and content of the transactional message. The document also includes the names of the personalization fields that are included in the message. The personalization fields are added to the document as placeholders that accept specific information about the recipient when the messaging service assembles and transmits the message.

The Summary Mailing tab provides a field that is labeled Complete field list for this mailing to identify the personalization fields that are included in the document that is referenced by the messaging. The web service request must contain information for each of the fields on the list. The names of the personalization fields in the web service request must exactly match the names that appear in the document.

The web service request must also provide the data that is required to complete the message, including values for each personalization field that is included in the message. The digital marketing team must consult with application developers to identify and locate all of the information that the transactional message client must provide.

The transactional messaging service evaluates each web service request to determine if the request provides all of the name-value pairs that are required by the transactional message. The request fails if the personalization field names, values, or data types do not match the requirements for the message.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.