Multi-language onboarding
Speak your users' language. Add per-step translations and Wakeline shows each user the right one automatically, based on their language — with a graceful fallback when a translation is missing.
Get started in minutes.
Empieza en minutos.
Per-step translations
Translate each step's copy for every market you serve.
Automatic detection
Wakeline shows each user their own language automatically.
Graceful fallback
Missing a translation? Users still see your default — never a blank.
Live in three steps.
Add translations
Provide copy for each language.
Wakeline detects language
Each user sees the right version.
Publish
One guide, every market.
One onboarding tour, five languages, one afternoon.
Expanding into Europe should not mean five parallel tours drifting apart. One flow with per-language content is the maintainable shape — here is the workflow.
Declare the languages
In Settings → Localization, set your authoring language and add the target languages from the catalog of 27 — say German, French, Spanish, Portuguese.
Send the user's locale
Your identify() call includes a locale trait ("de", "fr"...). That single trait is how each user gets the right language automatically — no separate flows, no URL tricks.
Translate, or delegate it
The coverage matrix shows percent-translated per guide per language. Fill the gaps by hand — or hit "Auto-translate missing" and have AI draft the lot, then review the German for length.
Trust the fallback
A user whose language has no translation sees your authoring language, never a blank. Ship at 80% coverage; the fallback covers the tail while you finish.
What to expect: Each user reads the tour in their language from one maintained flow. When you edit step three, you edit it once — the matrix immediately shows which translations need catching up.
When not to use localization.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
Before product-market fit in one language
Localization is leverage on something that works. If the English tour's completion rate is poor, translating it ships the same problem in five languages — fix the flow first.
Languages without owners
Auto-translate drafts well but reviews nothing. Adding a language nobody on the team can sanity-check risks shipping wrong register or broken idioms to an entire market — add languages you can stand behind.
Translating the product's chrome
Wakeline localizes your guides. If the app around them is English-only, a German tour pointing at English buttons is a stranger experience than consistent English — sequence guide localization with product localization.
How does a user get the right language?
Send a locale trait in identify() and Wakeline serves each user the matching translation automatically. One flow, per-language content, no duplicate guides to keep in sync.
What happens when a translation is missing?
Graceful fallback to your default (authoring) language — users never see an empty step. That makes partial coverage shippable: launch when the important guides are done, let the matrix track the rest.
How do I know what still needs translating?
The translation coverage matrix in Settings shows percent-translated per guide per language — a live to-do list. "Auto-translate missing" (when AI is enabled) bulk-drafts the gaps for human review.
Which languages are available?
A catalog of 27, chosen per project. You pick the set you actually support rather than pretending to forty — the matrix keeps honesty about the difference between added and finished.
Does multi-language onboarding change targeting?
No — targeting stays language-independent. One tour targets "logged-in, first session" everywhere; the locale trait only decides which words render. You can still segment by locale deliberately (an EU-only notice) when the message itself is regional.
Who reviews the auto-translated content?
You do — auto-translate drafts, humans approve. The coverage matrix makes review manageable: it shows exactly which guides and languages changed, so a native-speaking teammate reviews deltas, not the whole catalog. Ship the reviewed languages; the fallback covers the rest honestly.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.