Transact XML Click Reports on the navigation bar and select Automated Messages. A list of automated message groups display on the Active tab. You can also access the Canceled/Completed tab to view older groups. Click the name of the Automated Message group you want to view (Transact message groups are identified in the Event Trigger column). The Automated Message Report appears with a summary for specific mailings. You can select different time periods using the Detail by Date tab. You can also export the report details in CSV format using the Download Data button. View Specific Information Click the mailing name to access Summary statistics. Click links to view individual reports, such as Delivery Info (for example, Suppressed and Bounced), Tracking Metrics (Opened and Clicked), and Email Responses (Abuse complaints and Change of Address). To see specific results for a mailing, select one of the links, such as Clicks. A report appears from which you can change the scope of the report and create databases. View Clickthrough Results Select Clickthrough Performance Results. A report appears showing statistics and offering a selection of the individual links that appear in the mailing. Clickthrough links are listed by the tag name given to the link in the XML. Results are shown for all individuals who clicked the link. About Bounce Handling Transact messages can be: • Delivered • Hard bounce • Soft bounce Experiencing transient delivery failures Hard bounces do not typically auto-correct (for example, a user ID does not exist at an ISP) and Transact does not retry them. Once a hard bounce occurs, it follows Bounce Processing per the Undeliverable/Bounce settings for the organization. 32 www.silverpop.com 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.
Transact XML Some soft bounces are similar to hard bounces and Transact does not retry them (for example, a full contact's mailbox would cause a "bounce" and Transact would not try sending it again). For other soft bounces and transient delivery issues, Transact will retry the sending process for a period of time (examples of such issues include ISP throttling email rates or ISP connection failures). The default retry interval is currently set to five minutes. Transact will attempt to resend undelivered messages after the retry interval passes. A bounce-after, also related to soft bounces and transient failures (for example, an ISP not accepting mail due to limiting), has a retry interval of 24 hours. If the message still does not deliver after the retry, Transact flags the message as a "bounce" and processes it according to organization settings. Notes: Bounce-after retry interval for yahoo.com domains is set to 30 hours. Silverpop works with all ISPs to ensure maximum delivery based on their requirements. 33 www.silverpop.com 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.
Transact XML Element: ERROR_STRING
Transact XML Element: SEND_STATUS U
Transact XML Error Codes in XML Res
Transact XML 10. Exception:javax.xm
Transact XML 1 - encountered errors
Transact XML XML Submission Documen
Transact XML FLT_2_TRIP_TITLE Sal
Transact XML font-weight: bold; fon
Transact XML Thursday, February 23
Transact XML Transac
Transact XML Maintenance About Main
Transact XML Troubleshooting About
Transact XML Hyperlinks and Trackin