Brief Overview

This article covers best practices for building multi-language WalkMe content, from choosing a primary language through translation and QA. Follow this process in order to reduce rework and lower the risk of content breaking after it's translated.

How It Works

Setup and pre-build

• Primary language: Select one primary (source) language for your build
• Capture strategy: Capture all current and future flows using this primary language only, even if a step only fails when tested in another language

Building

Create your content in the primary language and test it using Preview mode and Publish mode.

Troubleshooting element detection

Always use the Flow Tracker to test and evaluate your WalkMe items.

If elements aren't found during testing, check the following first:

• Conditions: Confirm display conditions and segmentations match your testing scenario
• Splits: Confirm splits are functioning as expected
• Rule logic: Avoid "Text is" conditions, since they can prevent future multi-language compatibility.

Rule Engine

Content QA

After the primary language build is complete and works correctly in Preview mode and Publish mode, begin quality assurance (QA). Don't just test the "happy path" — perform a full QA round that includes:

• Flow and functional integrity: Confirm all content plays from beginning to end without breaking, including "crash testing" — checking how the content responds to user errors, like skipped fields, or to site error notifications
• Balloon logic and positioning: Confirm balloons point to the correct elements and don't cut off on smaller screens or overlap with critical site buttons
• Flow Tracker: Confirm that goals and milestones are triggered at the right time
• Contextual accuracy and segmentation: Confirm segmentation rules and display logic work across different pages and environments, so users only see what's relevant to them

Quality Assurance Testing

Post-QA fixes

Adjust and rebuild your content based on the feedback raised during QA. Repeat phases 3 and 4 until the content is fully finalized in the primary language

Multi-language testing and element recognition

After your content is 100% ready in the default language, prepare it to support additional languages. Use one of the following options to help WalkMe correctly identify translated elements

Option 1: Lexicon import (recommended)

Upload exact text translations to the Admin Center. This option works best for complex phrases (for example, "Contract Workspace") where automated translation might be unpredictable.

Lexicon Translation Upload

Option 2: Auto-learning

Let WalkMe "learn" your site's translations by previewing the content in the target language

Repeat these steps for each supported language:

• Change the site to the secondary language
• Run 1: The learning run. Open Preview mode and play the flow
  Note

  If content breaks or a step fails, skip that step and continue. Try to complete as much of the process as possible — WalkMe uses this feedback to learn the site's translations for the whole flow.

• Run 2: The validation run. Restart the flow in Preview mode. The content should now work smoothly

Multi-language sanity QA

After you import translations or finish the learning run, test the content again in a published environment or in Preview mode

Technical Notes

• The Lexicon import option isn't available for SAP builders
• After uploading translations via Lexicon import, wait a few minutes for them to process, then refresh the editor and the page