Are we able to define email headers using the XML transact interface?
Yes. You can possibly use regular personalization and include the ‘ID’ somewhere in the message body itself. There should be no difference searching for it there as in a header field. You need a unique search string to go with the ‘ID’. The search string would not have to be visible within the HTML body.
How does Acoustic Campaign Automation handle Transact Message delivery failures?
For more information on delivery failures, go to Bounce handling.
Can a canceled Transact Campaign ID be reused?
No. You will have to create and activate a new campaign and enter the new campaign ID in your XML code. This will replace the canceled campaign ID.
Can I use more than one Campaign ID in a Transact XML submission?
No. You can only use one Campaign ID in an HTTP submission file or an FTP batch file. Transact can only send one transactional mailing per session, therefore only one campaign can be used per XML submission.
Does Acoustic Campaign Automation automatically update Transact when changes are made?
Information edited on either Acoustic Campaign Automation or Transact, has to be synchronized between the two programs.
Changes in Acoustic Campaign Automation
If you make a change within Acoustic Campaign Automation, such as adding a List, changing a Template, creating a Campaign, or adding an IP Address for submitting XML documents, allow up to 10 minutes for Transact to become aware of these changes.
Submitting information through XML
Information that is submitted through XML Submit Document synchronizes with Acoustic Campaign Automation after a short time. Information is added to the List, and hyperlinks are tracked through this mechanism. After submitting information through the XML Submit Document, allow up to 1 minute for the information to be synchronized.
Note: If a recipient receives an email and clicks on a hyperlink before synchronization has occurred, the link will work, but it may not be tracked.
Does Transact XML support CSS style sheets?
Transact does support CSS style sheets within a CDATA tag inside any HTML you provide in your transactional request.
The CSS styles can be in the following formats:
- Inline styles
- Internal style sheet
- Externally linked style sheet
For additional information, please refer to the Transact XML User and Developer Guide.
Appending a query string value to a URL link
If you have a link in your Transact mailing template and you want to append a value as a parameter within the URL, you’ll need to use personalization.
An example of a parameter added to a URL: <a href=”http://www.example.com?value=%%VALUE%%”>
In order to append personalization values from Transact XML to a URL link declared in a mailing one must remember to save and personalize that value in the xml. Here is an example in xml:
For further information, reference the Transact XML User and Developer Guide.
Which type of suppression lists does Transact XML support?
Transact XML supports FCC, domain, prefix, and global- level suppression. You’ll find the FCC, Domain, and prefixes that are not allowed for your particular organization within the Email Blocking section. Go To Settings > Org Admin > Email Blocking.
Transact XML does not support organization level suppression
Transact XML only supports global suppression as the design of Transact is to send an email based on some sort of recipient action.
It is up to you to handle your opt outs and undeliverables by exporting these metrics from your reports or you can export the Master Suppression List manually or by using the Export List API.
Note: The Suppression list is built based on opt-outs and undeliverables. If a contact’s email address is undeliverable (or if they mark your email as abuse via their email service provider), Transact adds their email address to a dedicated list of undeliverable and suppressed email addresses (also referred to as an Org Master Suppression List).
What does STATUS and SEND STATUS mean in Transact XML Responses?
When you are sending Transact mailings, you might receive an XML response from Acoustic Campaign Automation with both <STATUS> and <SEND_STATUS> tags. Sometimes they are returning different values.
For example, you might see <STATUS>1</STATUS> along with <SEND_STATUS>0</SEND_STATUS> within your response. What do they mean?
Transact allows for including one or more recipients to be sent in one <XTMAILING> request. Through the XML response, Transact sends<STATUS>, which is a description of errors that are generated when processing the submission.
0 – Did not encounter any errors during the send; all recipients sent.
1 – Encountered errors during the send; some or all recipients were not sent.
2 – Encountered errors with the XML submission; no recipients were sent; no recipient error details that are provided, only the request-level error.
That means the <STATUS> value does not display any details about individual recipients. It indicates that the Transact recipients in this request are all sent, partially sent, or none is sent.
For <SEND_STATUS>, it is a recipient-level error code. It signifies the status of the send to the recipient.
0 – No errors were encountered during the send.
1 – Encountered an error during the send, will not retry the send.
2 – Request received; send cached for later send.
When <SEND_STATUS>=1, it means that recipient is not sent and is not going to be retried. For example, you are sending to firstname.lastname@example.org“, where “admin” is a prohibited email prefix on the Acoustic Campaign Automation Email Blocking list. That email address is always suppressed no matter how many times you retry your request from your end. In this case, we recommend your system capture and read <ERROR_CODE> for details on why this recipient is not sent a mailing.
When <SEND_STATUS>=2 is displayed, it means that recipient is not sent currently because the mail server is not available (normally happens under maintenance a window, or other mail server issues). However, the recipient is sent as soon as the mail server is online and available.
What happens to OAuth authentication during downtime?
OAuth authentication during downtime depends on whether the access tokens are new or if they currently exist and have been validated.
Note: IP authentication will always work in downtime.
Existing Access Tokens
If Transact XML (HTTP) is in downtime, such as during a release, valid OAuth access tokens will authenticate as they should.
New Access Tokens
New access tokens cannot be generated during downtime. This is true for both completely new access tokens, as well as tokens generated due to expiration during the downtime window.
What version of the HTTP protocol does XML API and Transact XML speak?
In order to have the most widespread compatibility, XML API and XML Transact speak HTTP 1.1.
If you notice that responses returned by Acoustic Campaign Automation / Transact has broken XML or out of place characters, you should check that you are not using HTTP 1.0 to make your requests.
Will Transact work with my company’s existing IT system?
Transact allows for easy, seamless integration with existing IT systems using our XML API set. Messages can be sent immediately or batched for bulk processing at a scheduled time. Whether you’re sending a few messages at a time or millions, Acoustic Campaign Automation can handle the load of high-volume sends.
Messages are created in real time and personalized based on your company’s unique business rules. Acoustic Campaign Automation helps ensure messages reach your customers’ inboxes and provides detailed tracking reports to monitor opens and clicks.
Are hyperlinks submitted within Transact XML code tracked?
Yes. Transact can track hyperlinks that are submitted within the XML CDATA, using Dynamic Link Leader (DLL) URL encoding. When encoded links are submitted within the XML document, Acoustic Campaign Automation tracks clicked URLs and the tracked data is available in reports within Acoustic Campaign Automation.
Note: This information is used to create trackable links within the XML submission. This information does not apply to links created within the mailing body.
To configure an XML Submission with tracked links, follow the steps below:
- Convert the URLs in the submission to DLL encoded links.
- If URLs contain personalization, add elements for each field to the SAVE_COLUMNS section and to the PERSONALIZATION section with the correct value for the recipient.
- Make sure that the recipient list contains the fields corresponding to the personalization elements defined in the XML submission i.e. custom fields.
- Perform a test send, click links and make sure that the redirected URL contains the correct URL and personalization substitutions.
- Check reporting after allowing enough time for the tracking to roll up and display.
Note: The Support team specifies the server for the URL
Links that are dynamically generated on the sending system are included in the XML using the CDATA tag, in the Personalization section, within a CDATA section.
Clickable links and Transact
It is advised to not use Click to View links in Transact. Additionally, Transact is meant to allow for a new record to be uploaded each time which can be just the email address. Be aware that because the Transact database is usually a flexible database, which is a record of transactional email history, the same email address can appear multiple times in the Transact database.
You do have the option to save other data to the database, but you must specify which fields in the API call. Transact only keeps records in the database for 60 days.
Does Transact have a searchable history?
The best way to have a searchable history of the transactional messages sent, is to use the BulkExport (BeX) or the RawRecipientDataExport (RRDE) API call to export the metrics and store them elsewhere for lookup.
Does Acoustic store Transact email messages which might include PII data? How do we manage this?
When you send a Transact XML payload, that payload contains special personalization tags. If you choose not to include the tags “Save_Columns”, then no PII data is saved to the Transact database EXCEPT the email address which is needed for reporting purposes.
Is it possible to set custom headers with Acoustic Campaign or Transact?
Currently, it is not possible to set custom email headers for either Acoustic Campaign or Transact.
What is the size (in bytes) of my Transact email?
Transactional message groups do not display the size of templates. However, you can perform a test send of an existing template and view its size afterward by navigating to Content > Sent.
How can I prevent duplicate contacts within a Transact list?
Trying to prevent duplicate contacts is somewhat counterproductive to the purpose of a Transact database. Transact is not intended to be used for non-transactional based communication. As such, each entry in your database is a receipt of that particular transaction not a contact. If a contact makes multiple transactions, you'll want the records for each instance saved within your Transact database.
Why are the recipient details disappearing from my Transact list?
Transact removes some recipient detail after a period of time because the databases can become so large and difficult to manage.
The following list shows the timeline for removal of data:
- Recipient level detail: List data is deleted on a rolling 60 day period. This means that recipient level detail is not available after 60 days.
- Aggregate level detail: Campaign detail remains available from the reports.
- Saving recipient level detail: To keep recipient level detail after 60 days, this data must be exported to another system.
Can I track password reset emails?
When you send a transactional email for a password reset, it is recommended that you do not track the links.
There is a delay of a few seconds from when the message is sent to contacts to when the table that is used for tracked links is updated. If a contact clicks too soon, the link goes to the redirect page instead of the designated URL on the first attempt.
Typically, contacts of transactional messages are not waiting for messages, such as invoices, to reach their inboxes. However, for password reset messages, recipients are waiting for that message to arrive so they can complete the password reset process. We recommend that you do not track the link so that contacts don't experience problems.
Can I use click to view in Transact XML emails?
For Transact XML, yes. But you must make sure that all personalization values are saved to the Acoustic Campaign database using <SAVE_COLUMNS> tags. Otherwise, the Click to View web page displays blank content for all personalization data in the email. This is because the Click to View feature works by pulling personalization information from the Transact database.
There is a delay of a few minutes until the personalization data is available in the Transact database. This is because Transact sends the message first, and then adds the recipient's email address and all personalization data (within <SAVE_COLUMNS> tag) to the Transact database.
To disable Click to View, deselect the check box in the Email settings.
Note: Click to View is not supported for Transact SMTP. You must disable Click to View in Browser for Transact SMTP.