Tracking data can be sent with reservation requests to analyze sales conversions, booking trends, and traffic channels
Name Value Description
additionalData array
URL request parameter for including special tracking values, exclusive to the booking and itinerary requests. Container for the additionalData1 and additionalData2 tracking data key/value pairs.

Data included in these fields is available in both the itinerary response and as part of the Affiliate Center Stats Generator under the labels "Temp1" and "Temp2."

Tracking values must be sent within this additionalData container element – do not send additionalData1 or additionalData2 directly within your request string.

Example Correct Format:

Individual values have a maximum of 256 characters - data is truncated when viewing from the Affiliate Center stats browser

• Note that when testing bookings, affiliate stats are loaded into the Affiliate Center each night from 12am to 2am CST. You will not be able to use the Affiliate Center verify data sent via this array until the following day. Booking data submitted is available in the itinerary response, as it was recorded into the systems immediately.

Example XML/REST Booking Request Parameters with AdditionalData values:



When reviewing the Affiliate Center stats, the Temp1 and Temp2 columns will be populated with the values that were passed in the additionalData1 and additionalData2 parameters, respectively.

How to use additionalData as a Map Entry

For each map entry object, set a key and value.

• MapEntry Key 1 will be additionalData1 and the value is whatever data you set for it.
• MapEntry Key 2 will be additionalData2 and the value is whatever data you set for it.

Example in Java additionalData[] =
additionalData[0] = new;
additionalData[1] = new;

Create an array of MapEntry objects and then set the key and value.  The last line sets it into the reservation request object.