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 includes a Tracking ID mechanism that allows a complete flow to be tracked end‑to‑end, from product retrieval to booking confirmation, in order to better understand what drives conversion.

The Tracking ID feature is enabled by default at organization level. When active, it provides a unique identifier that represents a full user journey across the API flow. This identifier replaces the standard product ID returned by product retrieval endpoints and must be used consistently throughout the flow until booking creation.

This approach enables API users to gain deeper insights into which products effectively convert into bookings.

If required, the Tracking ID feature can be disabled at organization level.

When the feature is active, the Tracking ID is available in all endpoints that allow 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.

If the Tracking ID feature is incompatible or irrelevant to your implementation, please contact your Amadeus Discover implementation manager to disable it.

Once disabled, product retrieval endpoints will return the standard product ID instead of a Tracking ID.

Warning

Use of the Tracking ID is the responsibility of the API user. When the feature is active (default), it is the responsibility of the API user to use the Tracking ID instead of the bare product ID throughout the flow. Failure to do so may result in loss of tracking and incomplete conversion analysis.

Tip

The Tracking ID feature does not impact endpoints exposing products for the purpose of Catalog Ingestion