Skip to main content

The Multilingual Visitor Experience

Learn how visitors interact with different languages and how the Pladia Empower PWA handles content when translations are or are not available.

Gabrielle Fanning avatar
Written by Gabrielle Fanning
Updated over 3 weeks ago

Overview

The PWA automatically supports 14 languages for all standard interface elements (buttons, menus, and system prompts). Beyond the interface, you can provide localized experiences by entering translated text and audio for your specific content directly within the Console.

This article explains how visitors interact with different languages and how the PWA handles content when translations are or are not available.

Read How to add translated content in the Empower Console.

Language Detection and Manual Selection

The PWA is designed to be intuitive, reducing the friction for visitors to find content in their preferred language.

Automatic Detection

When a visitor first opens the PWA, the system automatically detects the language settings of their device or browser. If that language is one of the 14 supported languages, the PWA interface will automatically display in that language.

Manual Selection

Visitors can change their language preference at any time during their journey. To do this, they should:

  1. Navigate to the My Visit tab.

  2. Click the Settings icon.

  3. Select their preferred language from the available list.

How Content is Displayed

While Pladia handles the interface "out of the box," the visitor's experience of your specific tour content depends on what has been entered in the Console.

Translated Content

If you have provided translations for configurable text fields, content blocks, audio or image files, the visitor will see and hear that content immediately upon selecting their language.

Non-Translated Fields

If a specific field—such as an Object description or a Space name—has not been translated into the visitor's selected language, the PWA will default to showing the English version. This ensures the visitor is never met with empty screens or missing information.

Videos

While video files themselves cannot be swapped based on language, the Caption fields for these assets can be translated. This allows you to provide context for visual media in the visitor's selected language.

For questions about configuring your languages, reach out to the Pladia Customer Success team—we’re happy to help.

Did this answer your question?