Parameters

Whether you embed the White Label widget or open the standalone experience, the same ideas apply: you pass parameters to describe the traveler context and we render the correct UI. This page gives you a quick reference for both integration models and links to the interactive builders.

Quick reference

Mode	How parameters are provided	When to use it
Standalone	Query parameters appended to the channel URL.	When you redirect users to the hosted Discover experience.
Widget	Attributes on the <traveler-widget> tag plus optional payload objects.	When you embed the experience inside your website or web app.

Standalone

Add the following query parameters directly to the channel URL. Keep paragraphs short so it’s easier to scan.

Key	Accepted values	Description
lang	en, fr, es, de, it, pl	Sets the UI language. English is used whenever a catalog item is missing the requested translation.
currency	EUR, USD, GBP, NZD, AUD, AED, CHF, CNY, CAD	Displays prices using the selected currency. The same value is sent to suppliers, but some suppliers may still return a fallback currency.
externalClientId	Any text string, 15 chars max	Optional tracking identifier that follows a user across the booking journey and is echoed in webhook payloads and booking exports.
travelerType	solo, family, group, couple	Personalizes recommendation carousels. For example, solo enables the Nightlife carousel.
iataCode	Any valid IATA city code	Opens the experience on a pre-selected destination.

Widget

When embedding the White Label widget, parameters map to HTML attributes on the <traveler-widget> tag. Views that need extra context (e.g. Recommendations) accept JSON payloads via recommendation-payload or recommendations-top-activities-params.

Tip

Use the interactive widget builder below to experiment with parameters. It now includes an environment selector so you can verify whether you are generating UAT or production snippets before copying them into your product code.

The widget preview uses the UAT environment unless you explicitly switch it in the builder. Update the generated snippet accordingly before deploying to production.