Bookings traceability

Amadeus Discover API includes tracking capabilities to ensure any booking generated by your traffic is ultimately assigned to your account.

In Redirection Flow, the Booking URLs include an organization identifier that is tracked until booking reports, ensuring you will get the commissions for the bookings you generated. It is also possible to complement the URL dynamically with an additional identifier “ExternalClientID” to track accounts or campaigns on your side.

In Booking Flow, all bookings are tracked on Amadeus Discover side including your organization identifier. It is also possible to complement the booking with an additional parameter “ExternalClientID” to track accounts or campaigns on your side.

Tracking ID

Amadeus Discover API also includes the possibility to fully track a flow to better understand what is driving conversion. The tracking id feature can be enabled at organization level and provides a way to identify a complete flow from product retrieval to booking confirmation. Enabling this feature will slightly change the output of the product endpoints so that the id provided will be unique. It will then be used in the rest of the flow until the booking creation and will give api user the possibility to get a better understanding of products that are driving conversion. When the feature is enabled, the tracking id will be available in all endpoints allowing product retrieval.

|Output changes

When the tracking id feature is enabled, the id returned in the response body will be a unique tracking id instead of the product id. This tracking id must be used instead of the product id in the rest of the flow until the booking creation.

To enable the tracking id feature, please contact your Amadeus Discover implementation manager.

Once enabled, the tracking id will be generated and returned in all responses allowing product retrieval. It will then be used in the rest of the flow until the booking creation.

Warning

Use of tracking id is the responsibility of the API user. If the feature is activated, it is the responsibility of the API user to use the tracking id instead of the bare product id in the flow. Failure to do so may result in loss of tracking.