Incoming messages to the Transact server must have a mechanism established to match the message with the correct Automated Message ID. Transact SMTP provides great flexibility in recognizing different types of messages for various types of transactional message groups, while allowing all messages to be sent to the same Acoustic Campaign IP address.

The system typically recognizes messages by their x-header (best practice). If this isn't practical, the system can recognize messages even if your system does not make distinctions, so your message workflow remains the same.

Note: The elements chosen to identify the message must be unique to the transactional message group and not used with any other transactional message groups.

Best Practice: An organization should have one transactional message group set up to use the IP address for identification so if matching does not occur, Transact will still send the message.