This article includes the typical steps for the Acoustic Campaign user and your developer.

Set up Transact SMTP

1. Support must enable Transact as an Acoustic Campaign non-email key-enabled organization.
2. Coordinate with your developers on using an x-header in email messages.
3. Create a restricted database for Transact with no contacts. Save it in the Shared folder.
4. Create a transactional message group and select Transact as the event trigger.
5. Complete a Transact email template and automate it.
   1. Reply to: The email address will automatically fill in the field.
   2. To: Enter your contact's email address.
   3. Subject: Copy the subject line from your Transact's group of automated messages summary page.
   4. Add your HTML or text into the email body area.
6. Set the submission IP address.
7. Test the email in Acoustic Campaign using the seed list that you created. The email is sent from the SMTP server to Transact. From there, it is processed instantly and is sent to the intended email inbox.
   1. See Message submission and response process (or contact support) for address information.
   2. If you do not receive an email message, there may have been a system error. Contact your IT department or developer. You can find system errors from the WAP servers in the system error logs and these errors are not indicative of email construction problems.
8. You can also verify that the contact was added to the database in Transact.
   1. In Acoustic Campaign, go to Data > Database > View data.
   2. Select your Transact database.
   3. Click the Search tab to see the contact in the database.

Send an email using Transact SMTP

1. Set up Transact SMTP message sending. Make sure that your SMTP server settings match the settings in Transact.
   • Email address: Use the from address that is provided in the group of automated messages summary.
   • Outgoing server settings: Find your organization's pod by going to high-level settings on to Acoustic Campaign. For example, the organization belongs to pod 4, so the outgoing server settings could be transact-campaign-us-4.goacoustic.com.
2. 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.
3. The HTTP response address replies to the submitter IP address.
4. 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 you set up a transactional message group in Acoustic Campaign.