Selling in more than one language? Prepare the entire campaign journey, including button labels, consent and errors. Translating only the first heading leaves customers with a mixed-language experience.
Choose the content language
Open Content language at the top of the editor. Review the base language and add the versions you need.
The content language is separate from the language of your DropUI dashboard. Switching the interface does not translate the offer.
Translate the complete offer
Review headings, descriptions, buttons, form labels, consent, error messages and thank-you screens. Check text inside images too.
Keep discounts and conditions equivalent across versions. Use links to the correct store language and current privacy policy.
Automatic translation, where used, still needs a review of product names and commercial terms.
Check language selection
Review the campaign's language matching settings and fallback. A customer's browser language and the language of a store URL can differ.
Do not confuse content variants with audience restrictions. Restricting visibility by language does not create a translation.
Test each version
Select every language and device in Preview. Look for missing text, unsuitable line breaks and untranslated later screens.
After saving and publishing, test the store under the intended language conditions and also with an unmatched language. Confirm that fallback content remains understandable.
Compare both versions
This guide has English and Polish content with page-language detection enabled. A page using <html lang="en"> selects English, and one using <html lang="pl"> Polish. The editor switch checks content; a store test checks automatic selection.

