This section contains important information about how Transact operates, maintains Acoustic Campaign databases, and there is also some basic troubleshooting information.
- Acoustic Campaign Database maintenance by Transact
- Transact / Acoustic Campaign Synchronization Times
Transact and Acoustic Campaign are independently operating programs and servers. Transact uses Acoustic Campaign databases, Acoustic Campaign email templates, Acoustic Campaign Automated Messages, and Acoustic Campaign Tracking. To do so, you must synchronize the information between the two programs.
VMTAs are retrieved in the following order:
If you make a change in Acoustic Campaign, such as adding a database, changing a template, creating an automated message, or adding an IP address for submitting XML documents, allow up to 20 minutes for Transact to become aware of these changes.
Information that is submitted through the XML Submit document synchronizes with Acoustic Campaign after a short time. Acoustic Campaign then adds the data to the database, and tracks the hyperlinks through this mechanism. After the information is submitted through the XML Submit document, allow up to 1 minute for the information to synchronize with Acoustic Campaign.
If a contact receives an email and clicks a hyperlink before synchronization is complete, the link works, but Acoustic Campaign does not track it.
Transact maintains its databases in Acoustic Campaign. Because of the large amount of data, databases can become unwieldy, so Transact removes some contact detail after some time, as shown in the list below.
Transact deletes database data based on the organization's Data Retention settings and then it is archived like regular Acoustic Campaign data.
Campaign detail remains available from the reports.
If you want to keep recipient-level detail after the specified date for your organization, you must export this data and save it on your computer.
Updated almost 2 years ago