Tracking

The basic aspects of the user activity on the Amadeus White Label are tracked out of the box. Without the need for any additional effort from the integrator, the Amadeus Discover platform tracks the following aspects.

Page views and user interactions

Through a codified system of events, the user clicks, navigation and other forms of interaction are tracked step by step by our White Label.

Our UX and Analytics teams leverage these data constantly to understand user’s behavior and improve our interface.

These data could be made available to you and your organization through a dedicated Kibana board in the context of the Customer Success process.

Ask your Customer Success Manager about it!

Booking activity

Every activity booking performed through the White Label is tracked in the Discover system, properly attributed to your organization and complemented with all the necessary information from the user and the activity supplier.

In case you need an additional level of granularity to track your bookings and properly attribute it to individual users, agents, or outlets in your system, you can leverage the externalClientId parameter (see Parameters for more info.)

This info can be retrieved through the Booking Reporting endpoints of the Amadeus Discover Quick Connect or exposed to you and your organization through a dedicated Kibana board in the context of the Customer Success process.

Ask your Customer Success Manager about it!

Advanced Tracking

While the basic tracking aspects do not require any development or configuration action, with only few additional steps you can greatly increase the insight capabilities of the White Label tracking features.

While generally optional, the following aspects are mandatory requirements for the Customer Success process to be activated on your implementation.

UTM parameters

Following a consolidated standard in online marketing, you can use UTM parameters to identify the source of the traffic that lead the user to interact with the White Label. This information will enrich every tracking event fired by the White Label and help us identify the traffic source with higher conversion and success rate.

These parameters can be specified as queryParameters in the Standalone Url or as attributes of the Widget html tag, as per any other White Label Parameter (see Parameters for more info.)

Standalone Parameter	Widget Parameter	Purpose	Possible values
utm_medium	utm-medium	the channel through which the implementation has been pushed to the user	‘email’, ‘whatsapp’, ‘website’, ecc.
utm_campaign	utm-campaign	the name of the marketing campaign that targets the implementation	‘Summer26’, ‘HolidayDeals’, etc
utm_source	utm-source	The name of the tool used for pushing the campaign	‘Yespo’, ‘Salesforce’, etc
utm_content	utm-content	The view of the white label targeted by the campaign	‘dsp’ (Destination Search Page), ‘dwp’ (Destination Welcome Page), ‘pdp’ (Product Detail Page)

Cookie Acceptance

Some aspects of the information the White Label tracking events can identify (session id, number of sessions, device, browser ecc…) are only legally collectable if the user legally agrees to be tracked. In White Label standalone a Cookie Acceptance banner prompts the user for consent when a channel is first visited, and persists the chosen information for future sessions. In White Label widget, it’s the implementer responsibility to collect user acceptance and pass it to the widget via a dedicated parameter.

Widget Parameter	Purpose	Possible values
cookiesPreferences	Indicates if the user has accepted tracking of his activity, refused it or we’re still pending the decision	‘ACCEPT_ALL’, ‘REFUSE_ALL’ or ‘PENDING’