7 months ago


Transact XML Engage

Transact XML Engage Database Maintenance by Transact Transact maintains its databases in Engage. Because of the large amount of data, databases can become unwieldy, so Transact removes some contact detail after a period of time, as shown in the list below. • Recipient-level detail: Transact deletes database data on a rolling 60-day period. Recipientlevel detail will not be available after 60 days. • Aggregate-level detail: Campaign detail will remain available from the reports. • Saving recipient-level detail: If you want to keep recipient-level detail after 60 days, you must export this data and save it on your computer. 104 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.

Transact XML Troubleshooting About Transact XML Troubleshooting We cover the following common troubleshooting issues in this section: Technical Issues, Automated Messages and Mailings, Hyperlinks and Tracking, and IP Address issues. Note: You can resolve most problems by first checking the error codes in the XML Response Document. These codes will provide you with a strong indication of what is causing a problem, and the following questions and answers offer common solutions. If you need further assistance beyond the information shown below, contact Silverpop Technical Support. Technical Issues HTTP Time-Outs 1. Verify the size of the request. Large requests might time out (we recommend no more than 10 contacts). 2. Look for internal and external network problems. 3. If you do not receive a response envelope, do not resend the submission; contact Silverpop Support. Bad Campaign ID Notification Error 1. Campaign was not properly set up in Engage. Campaign must be set to the correct type. 2. Mailing is not automated and assigned to the campaign. 3. If campaign was recently set up, Transact may not have fully synchronized with Engage (can take up to 10 minutes). Emails Not Sent 1. Verify you have received an XML Response Document. 2. If not, verify your system is sending. 3. Contact Client Support. Parsing Errors 1. Input request is not a properly formatted XML or fails to conform to schema. 2. Embedded characters should be surrounded by CDATA tags. 105 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.