Transact XML Troubleshooting

How do you save personalized field values to the database in Transact XML?

Assuming that your personalized field values exist within an Watson Campaign Automation database. You would use the Save Columns XML Tag.

This also applies to personalized parameters appended to a URL within the HTML code of
an active mailing within a Transactional Message Group.

Below is an
example:

<SAVE_COLUMNS>
<COLUMN_NAME>Full Name</COLUMN_NAME>
<COLUMN_NAME>Title</COLUMN_NAME>
</SAVE_COLUMNS>

In Transact XML why is it necessary to place the XML batch file in the Temp folder before placing it into the Inbound folder?

If the batch is a large file, the Transact server may try to download the file before it has finished uploading to the Inbound folder, resulting in an incomplete (and often corrupted) file. Placing the batch file within the temp folder prevents sending to an incomplete list or a corrupted file.

What is the HTTP submit address (url) for my transact XML?

In order for Watson Campaign Automation to properly process your XML it must be submitted to the appropriate URL. The URL is based on your pod and is case sensitive.

For example if your Transact org is on Pod 3, you would submit your XML to:
http://transact3.ibmmarketingcloud.com/XTMail

Note: The only capital letters in the URL are X, T and M. The rest are all lower case.

Resolution

If your Transact org is on another Pod, replace the $ below with the number of the pod that your transact organization exists.

http://transact$.ibmmarketingcloud.com/XTMail

What is a Dynamic Link Leader encoded URL?

The Dynamic Link Leader encoded URL is the URL that is placed in the mailing. When the recipient of the Transact mail clicks the link, it resolves to the Watson Campaign Automation tracking servlet. The URL parameters are processed by the servlet, the tracking data is updated, personalization substitutions are made, and the recipients’ browser is redirected to the correct URL destination specified in the ‘&kd’ parameter.

Note: Static personalization information can also be provided through a Template, and use Watson Campaign Automation tracking.

Please note the following when using Dynamic hyperlinks in the XML document:

  1. The XML must specify that the columns containing the data be saved in the List. The Watson Campaign Automation server does the substitutions for personalized links using the data in the saved columns.
  2. When placing hyperlinks in CDATA, the corresponding personalization values must be placed in the XML Personalization section.
  3. The customer must completely compose XML embedded hyperlinks on their system.
  4. The customer must provide a default value in case the hyperlink personalization is incomplete either because it was not submitted in the XML, or the slight Watson Campaign Automation server delay has not yet synced the information.
  5. Personalization strings should be limited to 255 characters. Data and markup over 255 characters will not be stored.
  6. The number of links included in the XML submission is not limited.

Hyperlinks that are improperly formed in the XML will not be tracked, and should not be used. For example, personalization that is unique to the customer’s system cannot be used or tracked without following Personalization requirements in this section, and should be avoided to prevent tying up the Watson Campaign Automation server. No error codes will be returned for this condition.

What is the link server URL for DLL Links on Transact POD 6?

Overview

In order to create pre-built Tracked links for use with Transact, we are instructed in documentation to use the appropriate Host server URL for each POD, the document is currently being updated with information on Pod 6.

Resolution

When referring to the Transact XML Documentation and specifically the DLL Hyperlink Encoding section, please note that the appropriate Host Server URL for POD 6 is:

recp.mkt61.net

Transact Clicked Hyperlinks Go to the Wrong URL

Watson Campaign Automation uses the Link Name for the hyperlink for tracking purposes. If you do not change the Link Name, Watson Campaign Automation will substitute the hyperlink first associated with it (the Link Name in the XML is the “&k” parameter name that precedes the destination URL).

Transact Links No Longer Redirecting

Overview

When I originally sent my Transact XML mailing, the links worked as expected. But now, I’m taken to an anti-spam page. Why?

Resolution

The most common cause of Transact links that once worked and now do not work is due to a mailing that was once active within the Transactional Message Group being deleted. Simply moving the active mailing within the Transactional Message Group to canceled/competed area will ensure it will not continue to send that version. Completely deleting the canceled/completed mailing is usually unnecessary and can cause the links to no longer redirect as expected.

Transact No Tracking, No Query String Parameters

Symptoms

A contact clicks the hyperlink in the message and goes to the destination site, but tracking does not occur and the query string parameters are missing.

Resolution

It takes up to 10 minutes for Transact and Watson Campaign Automation to synch information. If the contact receives the email and clicks the link before 10 minutes elapses, tracking and parameter substitution may not occur.

Transact Doesn’t Recognize my Requests Using Tags

Issue

When I submit my Transact XML request with Tags, for example: <TAG_NAME>FirstName</TAG_NAME>

Transact doesn’t appear to recognize them.

Resolution

There are a number of possible reasons why Transact may not be recognizing the Tags within the XML:

  1. Allow at least 20 minutes for any changes to a Transactional Message Group to propagate through the system.
  2. Check that the Mailing is automated and that it is active against the correct Transactional Message Group. You must also ensure that your Transact XML Campaign ID references the correct Transactional Message Group ID (Campaign ID = Transactional Message Group ID within Transact Watson Campaign Automation user interface).
  3. Check that the syntax of the tag name is exactly identical to the field name in the Transact Watson Campaign Automation Database and Template. Note: If you receive the error message ‘one or more save columns not found in the list’ the message is still sent.

For more information, refer to:

  • Training: ENG500Transact XML (available inside the Watson Campaign Automation Training Tab or the Support Portal/Training Tab.)
  • Transact XML User Guide

Campaign/Group ID Does Not Display in Properties When the Campaign is Created

Resolution

Sometimes navigating to another screen will help refresh the properties. Go to another screen and then return and check the link properties again. You can also complete a CTRL + F5 (on a PC) to refresh the page and clear the cache.

Transact Does Not Recognize a New Campaign

Resolution

  1. Transact requires up to 10 minutes to synch with new Watson Campaign Automation information. Allow 10 minutes to elapse, and then try again.
  2. Ensure the new Campaign/Group ID number is accurate within your XML code.

Transact Does Not Recognize the Tags Used within the XML Code

Resolution

  1. Verify the active mailing is automated to the correct transactional message group and campaign ID.
  2. Confirm that the fields exist in the Watson Campaign Automation Transact database and Template.
  3. Ensure that character case (uppercase and lowercase) matches the Watson Campaign Automation fields within your Transact database.
Note: Your message is still sent even if you receive the error message ‘one or more columns not found.’

Transact Does Not Recognize My IP Address

Resolution

Transact recognizes only IP addresses that you specify in your User IP Restrictions area. These User IP Restrictions will override any organization IP restrictions. For security, Transact will not respond to any IP address not specifically designated by you.

If Transact does not return any error codes, but operation is not as expected (such as failing to deliver email or saved column items not appearing in a database after a significant wait), contact IBM Watson Campaign Automation Support.

Transact Does Not Recognize My IP Address

Resolution

Transact recognizes only IP addresses that you specify in your User IP Restrictions area. These User IP Restrictions will override any organization IP restrictions. For security, Transact will not respond to any IP address not specifically designated by you.

If Transact does not return any error codes, but operation is not as expected (such as failing to deliver email or saved column items not appearing in a database after a significant wait), contact IBM Watson Campaign Automation Org Admin.

Your Org Admin must set the IP address in IBM Watson Campaign Automation. Set the IP Address for Transact sends,

Join The Discussion

Your email address will not be published. Required fields are marked *