If visitors use different languages, one message may not be enough. Add language versions to the same campaign instead of sending duplicate campaigns to the whole list.
Add translations
- Edit the notification and open Settings.
- Choose the default language.
- Add separate translation rows with a language, title and body. Translate any button labels too.
- Do not select the same language in multiple rows. Save the campaign.
How text is selected
DropUI uses the language saved with the subscription. It looks for an exact version, then a base language and then the default. If a matching translation is unavailable, it uses the available default content.
The dashboard language used by the campaign author does not determine every recipient's language. Check subscriber data and choose a fallback deliberately.
Example of language selection
For a subscription marked en-US, the system first looks for that version, then the base language en. Without a match, it uses the default content. Adding Portuguese in the dashboard does not automatically mark every subscription from Brazil as Portuguese.
Choose a default language that makes sense for recipients without a matching version. Translate the whole message, not only its title, and check that the linked product is available on the destination page.
Check consistency
Every title should promise the same offer. Translate button text and ensure the destination fits the recipient. Adding a notification translation does not automatically translate the product page.
Do not leave fields empty expecting the system to write them. Check versions with your own test subscriptions before sending. UTM parameters can help distinguish campaign visits later.

