Supported channels
- App push
- Web push
- In-app popups
- Web popups
Localized messages must be enabled for your project.
1. Enable localized messages
Choose where you want to set up localized messages.Campaigns
- On the campaign creation page, select App Push, Web Push, In-App Popup, or Web Popup.
- Open Advanced Settings.
- Turn on Use localized messages.
User journeys
- Add a message node or open an existing one.
- Select App Push, Web Push, In-App Popup, or Web Popup.
- Turn on Use localized messages.
2. Write push messages
For app and web push, write the default message and the messages for each language directly in the editor.2-1. Write the default message
In Default, enter the title and body to send when none of the localized versions matches the user’s language. Make sure recipients can understand the default message and take the intended action.2-2. Add a language
- Select Add language.
- In Search languages, enter a code such as
jaor a language name shown in the list, such as 日本語. - Choose a language.
- Enter the message to send in that language.
2-3. Auto-fill translation drafts
Use the default message as the source for the translation drafts.- Enter the default title and message content.
- Add the languages you want to translate into.
- Select Auto-fill N languages. The number on the button shows how many languages will be filled.
- Review and edit the translations.
2-4. Write promotional messages
3. Connect popup templates
Popup localization uses templates you create in advance.- Create a popup template for each language you plan to use.
- In-app popup: Create an in-app popup template
- Web popup: Create a web popup template
- Under Default, select the popup template to show by default.
- Select Add language, then choose a language.
- Select the added language, then choose the template you created for it.
4. Set a user’s language
By default, Notifly checks the user’s$locale first, then the last observed locale ($last_observed_locale). For each value, it looks for a match on the full code, then on the language subtag. If neither value matches, it uses the default message or popup template.
If your service lets users choose a language, save their choice in $locale.
4-1. Save $locale
When a user signs in or changes their language, call the Notifly SDK’s setUserProperties method to save $locale.
- Android
- iOS
- JavaScript
- React Native
- Flutter
setUserId before calling setUserProperties. Save $locale again whenever the user changes their language in the app or website.
For SDK-specific instructions, see the Android SDK, iOS SDK, JavaScript SDK, React Native SDK, and Flutter SDK guides.
4-2. Language code format
Store a BCP 47 language code in$locale. Use the same code as the language you added in the message editor.
You can include a region, as in
en-US, ko-KR, or ja-JP. For example, if $locale is en-US, Notifly looks for an en-US message first, then an en message.
4-3. Language selection examples
These examples assume that$last_observed_locale is not set.
5. Check before sending
Push notifications
- Make sure recipients can understand the default message on its own.
- Check that all added languages show a check mark.
- Review the Liquid variables, images, and links for each language.
- If you used auto-fill, review the wording and placement of variables.
- For promotional messages, check the advertising disclosures and opt-out instructions for each language.
Popups
- Check that you selected the correct template for Default and every language you added.
- Check the copy, images, buttons, and links in each template.
