Although Transact and Acoustic Campaign are independent operating programs and use different servers, Transact uses some features from Acoustic Campaign:
- Email templates
The information must be synchronized between the two programs. This means that if you make a change in Acoustic Campaign, such as adding a list, changing a template, creating a campaign, or adding an IP address for submitting XML documents, you'll need to allow up to 10 to 20 minutes for Transact to become aware of these changes.
Here's a list of Campaign features that may or may not work with Transact:
|Campaign feature||Transact XML||Transact SMTP|
|Link opened tracking||Yes||Yes|
|Unique key identifier||Non-email keyed||Non-email keyed|
|Personalization added at send time||Yes||No|
|Click-to-view Message||Yes, with limitations||No|
|Forward to a friend||No||No|
|Suppression||FCC, Domain system||FCC, Domain system|
|Dynamic Content Rulesets||No||No|
|Send time optimization||No||No|
|Custom domain required||Yes||Yes|
Submitting information through XML
Information that is submitted through XML Submit Document synchronizes with Acoustic Campaign after a short time. Information is added to the list, and hyperlinks are tracked through this mechanism. After you submit information through the XML Submit Document, allow up to 1 minute for the information to be synchronized with Acoustic Campaign.
Note: If a contact receives an email and clicks on a link before synchronization has occurred, the link works but might not be tracked by Acoustic Campaign.
Are you working with APIs?
Ensure that you apply robust and well thought out retry logic where applicable in your API process to correctly identify and filter out potential transient network disruptions.