Communications that are used with transactional message

You compose a communication for transactional message just as you would to create a communication for standard messagings. Like communication that are used with standard messagings, a communication that is used with transactional message defines the content of the email message.

Important: After you enable a messaging for transactional message, you cannot delete or change the communication that is referenced by the messaging. To edit the communication, you must disable the messaging for transactional message. You can re-enable the messaging for transactional messaging after you complete the changes.

Communications that are used for transactional message require the following.

  • The communication must contain personalization fields for the email address or phone number or WhatsApp number, and usually contains fields that provide the name of the recipient.

    You can incorporate other personalization fields in the message as necessary to suit the transaction.

  • Provide application developers with a list of the personalization fields contained in the message and the type of values expected for each field.

    The mailing tab provides a link to generate a list of the personalization fields contained in the communication that is referenced by the messaging.

  • The communication must contain a From address or that is displayed to the recipient.

    If you use a personalization field to specify the From address, the email domain of the address must match the email domain registered with Unica for your Deliver account.

As a best practice, preview the communication that defines the message and fully test the messaging configuration.