This article includes the typical steps for the Acoustic Campaign user and your developer.
Acoustic Campaign User Setup
You need to add the Transact x-header. There are no changes required for the organization message composition or generation workflow. The content of the messages is not changed, unless you elect to make modifications, which you can set in Acoustic Campaign.
You need to change the x-header (for transactional message group recognition). There are no changes required for the organization message composition or generation workflow.
Note: If it is not practical to use an x-header, see Message and Transactional Message Group Recognition for other methods.
Set up Transact SMTP
- Support must enable Transact as an Acoustic Campaign non-email key-enabled organization.
- Coordinate with your developers on using an x-header in email messages. See Message and Transactional Message Group Recognition.
- Create a restricted database for Transact with no contacts. Save it in the Shared folder.
- Create a Transactional message group and select Transact as the event trigger.
- Create a Transact email template and automate it.
- Set the submission IP address.
- Test the email in Acoustic Campaign using the seed list that you created.
Send an email using Transact SMTP
- Set up Transact SMTP Message sending.
- Route your MTA server to the Acoustic Campaign MTA server: Transact SMTP can only accept messages in standard SMTP format. You can submit requests to the Transact SMTP MTA only. Documents cannot contain multiple contacts.
- The HTTP response address replies to the submitter IP address.
- If using an x-header for campaign recognition, you must provision x-header support in the original email header that you routed to Transact.
An organization can submit from several internal IP addresses. You can also use them to identify messages by campaign.
There is no Developer API for this application. Configuration occurs when the user sets up a transactional message group in the Acoustic Campaign interface.