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.
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.

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).
      - 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.
        Virus scanning for attachments
        The Deliver Transactional Mailing Service does not scan attachments for computer viruses or other types of malware.
    - 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

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.

By attaching files to transactional email, you can provide the email recipient with extra personalized information. For example, you can send a transactional email to confirm a concert ticket purchase and use attachments to provide a printable ticket and seating map. You cannot specify attachments for standard mailings.

When you enable a mailing for transactional email, you must specify how many attachments you want to send with the email message. Deliver places limits on the size of individual attachments and the total size of all attachments.

The transactional email request that is submitted to the Deliver TMS must contain the document content and information about each attached document. The email marketing team must work with application developers to provide the following information about each attachment.

The file name of the attachment
MIME content type of the file
Contents of the file

The method that is used to include attachments depends on the programming language and development tools that application developers use. For more information about how to provide attached content, see Attachments in transactional email requests.

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.