TourDash Open Widget settings →

Install and customize

Set interface and tour languages

Choose the interface language and restrict departures by spoken language.

Shareable guide · no sign-in required ↗

Before you start: copy your website snippet and confirm the spoken languages in your tour schedule.

Interface language and tour language

For a Spanish page, add data-locale="es" data-language="es". Use data-locale="en" data-language="en" on the English page. The language restriction applies to tours, dates and departure times, with no language switcher or fallback to another language. Omit both data-language and data-languages to offer all languages.

On a dedicated tour page, add data-product="YOUR_TOUR_PUBLIC_ID" to open directly on that tour’s date selection. Set data-mode="assistant" for the floating window and add data-tourdash-open to your existing Book now button.

Without data-locale, the widget uses your page’s HTML language, then the default in Widget settings. Interface text is available in English (en), Spanish (es), French (fr), Italian (it), German (de), Portuguese (pt), Dutch (nl) and Polish (pl). Unsupported languages fall back to English. In Tour Setup → Tour content, choose a content language to enter translated titles, descriptions, highlights and meeting details. Save and publish the tour. The widget uses that language’s saved text, falling back to the original for empty fields. Translations are entered by you; policies, ticket labels and custom questions retain their existing saved text.

For a French interface, use data-locale="fr"; add data-language="fr" to show only French-speaking departures. For Italian, use data-locale="it" and, if needed, data-language="it". Regional locales such as fr-FR and it-IT are also supported for the interface. Set your confirmation page separately.

For an English interface offering only Spanish and French departures, use data-locale="en" data-languages="es,fr". Travelers can select either language or both. The language list takes priority over data-language when both are supplied. Use comma-separated two- or three-letter codes. An invalid list shows no matching departures.

For example, a Spanish tour page can use these settings in its copied snippet:

Example code
data-mode="assistant"
data-show-launcher="false"
data-locale="es"
data-language="es"
data-product="YOUR_TOUR_PUBLIC_ID"
data-success-url="/es/gracias/"

Use en for both language settings on the English page. The interface language and the language spoken on the tour are separate settings: changing only the interface language does not hide departures in other languages. To get the correct tour identifier, open the tour in Tour Setup → Online booking. Choose the widget language and the allowed departure languages separately, then select Copy tour booking code. Paste those attributes inside your widget's opening script tag, replacing existing attributes with the same names.

The confirmation paths in this guide are examples. Replace them with your real pages or leave data-success-url empty to keep the widget confirmation.

Check your result: open each website page and confirm both the interface text and the offered departure languages. Confirm that your published tour translations appear in the widget language.

Choose a confirmation destination for each page.

Help us improve this guide

Found an unclear step or an outdated screenshot? Tell us what you were trying to do. Your message opens in WhatsApp for you to review and send.

Send documentation feedback ↗

Need help with your setup or a booking? Get widget support ↗ Include the page URL, approximate time and public booking reference if available. Do not include card details or passwords.