To ensure the search displays according to user selections, the airTRFX deeplink must communicate with the airline’s booking engine.

This section is usually reviewed and completed by: Web Product Owner and/or Technical Liaison of Booking Engine

Deeplink documentation is usually provided by the reservation system provider (ie. Amadeus, Sabre, Navitaire, etc) and is the same information airlines share with their Meta Search Engine Partners (ie. Google Flights, Kayak, Skyscanner, etc.) to send users to the airline’s booking flow. Good documentation typically includes sample deep-links and parameters definition.

It is important to inform EveryMundo and share the proper documentation if there are different deep-link rules and variables for mobile, in case the airline has different booking flow by device.

Example of airTRFX page connecting to the airline’s booking flow via Deeplinks:

What you’ll need for Deeplinking

Languages and Markets

A deep link will correspond to each language and market covered. If a customer has multiple IBE providers, it is critical to understand which languages and/or markets use which deep-link.

Point of Sale / Currency

To ensure the deep-links are directing users to the proper currency, EveryMundo needs to understand the currency logic. Most customers have either Site Edition/Point of Sale-based pricing or the currency is based on Point of Origin.

URL Parameters

The language/market and the description of the parameters used inside the URL provides a definition of each possible URL parameter along with the preferred input format and any limitations.


EveryMundo needs documentation for any required deep-link parameters that may be used for tracking purposes.

Anatomy of a Deeplink:


Implementation Sections: