Everything up to this point is authoring. This is what actually happens when a translated experience is delivered.

When a host sets up a session, they'll see a language picker on the setup form listing the languages the experience has been given. Whichever they pick becomes the language of that session.

The picker only appears when there's a genuine choice — an experience with English alone doesn't show one.

Participants don't choose their own language. Everyone in a session sees it in the language the host picked, so a mixed-language group needs more than one session.

If you're running the same experience for several regions, run a session per language. Each session's report, and each session's post-experience emails, follow that session's language.

Nothing is ever blank. Any field that hasn't been translated shows the English text instead, and any media without a version for that language plays the English file. This happens per field, so a session can be almost entirely in German with two untranslated questions in English.

Before you deliver, use Show: Untranslated in the Translation tab to see exactly what would fall back. See Working in the Translation tab.

Subtitles aren't tied to the session language. Where a video has subtitle tracks, the host can pick which one is showing from the host controls, independently of the language the session is running in. See Subtitles.

You can add ?language= followed by the language code to a host link to pre-select the language on the setup form. It's a starting point, not a lock — the host can still change it before starting.