Before users can send Transact emails, an Organization Administrator and a Acoustic Campaign System Administrator must complete the set-up steps.

Before you begin

The system administrator, Acoustic Campaign Support, completes the following tasks during setup:

• Enables Transact for your account.
• Configures FTP/SFTP settings, if applicable (such as the submit-to IP address and response directory).
• Configures the HTTP and HTTPS settings, if applicable (such as the response address).

After the system administrator completes the initial setup for the account, your organization administrator needs to perform a series of tasks.

Procedure

1. Set the error notification email address.
   1. Go to Settings > Organization Settings > General Settings.
   2. Click Edit.
   3. In the Notification Email Address for System Issues field, enter the email address where you want to receive error notifications.
2. Set the time zone for the users.
   1. Go to Settings > User Profile.
   2. Under Localization, select the Time Zone from the drop-down menu.
3. To allow emails from Transact, add one or more sending IP addresses or OAuth credentials to the security settings.
   1. Set up the Sending IP address that you use for testing and production. Go to Security Settings > Access Restrictions. The Transact server responds to XML Submit Documents that use HTTP by sending a Response Document back by using HTTP. (FTP responses are saved in the FTP status directory.) During testing, this document displays in the browser. Note: You can't add an IP range. You must enter a single IP address.
   2. Optional: Enable an OAuth application for Transact.
      Note: Users who don't have a dedicated IP address can use this security method.
4. Identify the dynamic link URLs.
5. Complete the organization's back-end integration (unless you are using a tool for testing).
6. Identify tags in XML (database and template fields).
7. Identify content for the template.

What to do next

After the initial setup is complete, you can create the email database, email template, and the group of automated messages. The initial contact database is empty. You must identify the personalization fields (tags) that are used in the XML for the database. Your system dynamically generates the contact name and information. Your system can also dynamically customize and send all content for the transactional email. It is not necessary to include this information manually in the template (except for fields).

• You can include URLs in the CDATA.
• Personalization fields that are used to identify contact information and URLs in the XML Submit Document must be set up in the database and template. These fields must also be identified in the XML elements in the Submit Document.
• You don't need to include a field in the template for data that is only stored in the database.