Transact can match inbound messages with Acoustic Campaign transactional message groups in a number of ways.
An x-header is a unique sender-generated identifier (text and numbers), placed in the header of an email, which is recognized only by the system that is intended to recognize it. The two systems "agree" that an x-header has a specific meaning for these two systems. Relays, gateways, and the client system do not see or interpret the x-header, and Transact removes it from the outbound message. The use of an x-header is the best practice for identification.
Note: Using an x-header may require modifying your email system.
From Address plus Subject
This is an excellent method, which requires no changes of any kind to your email system. The From Address field will always be the same. The Subject is typically the same on most systems, even when using personalization. For international encoding, Transact supports subject-line encoding as 64-bit or Quoted Printable.
Important Important: If sending encoded subject lines for international mail, you can only use x-header or IP address methods.
Notes: The combination of the From Address and Subject line must be unique and always the same.
Carriage returns inserted into subject lines make identification impossible.
The Subject is case-sensitive. In addition, in some cases the subject may change; in other cases the international character encoding makes the subject difficult to match (if unable to use 64-bit or Quoted Printable). This might not be the best method when these situations arise.
IP address match
In most systems, the sending IP address will always be the same.
If you choose an IP address as the identifier, you cannot use it with other transactional message groups (but you can use other IP addresses within the organization).
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.