Multilingual Messaging

Multilingual Messaging lets you send one push campaign in multiple languages.

Netmera selects the right language for each user automatically. It uses either the user's device language or a custom profile attribute. If no matching translation exists, Netmera sends the default language.

This flow applies to push campaigns.

Before you start

Make sure:

  • multilingual messaging is enabled in Settings > General > Language,

  • your users have a detectable device language or a populated language attribute,

  • and you choose one default language for fallback.

Step 1: Enable multilingual messaging

Go to Settings > General > Language.

Turn Multi Language on, then click Apply.

spinner

Step 2: Choose the language source

Choose how Netmera determines each user's language.

Device Language

Use this when the app language usually matches the user's device locale.

Netmera reads the operating system language from the user's device. If a campaign includes that language, Netmera sends that version.

Custom Profile Attribute

Use this when you store language preference on the user profile.

This option is useful when language comes from your app logic, CRM, or signup flow rather than the device. To create and manage language attributes, see Profile Attributes.

Language

Step 3: Create the campaign

Go to Messages > Campaigns > Create New Campaign.

Continue with the regular campaign flow until Step 2: What.

spinner

Step 4: Set the default language

In Step 2: What, select Default Language.

This is the fallback version of the message. Netmera sends it when a user's preferred language is not available in the campaign.

If a user language is missing, Netmera sends the default language version.

Step 5: Add translations

Click Add next to Default Language.

Add each language you want to support, then enter the translated content for that language.

Translate all message fields you use in the campaign. This can include title, body, subtext, and other content fields available for the selected push type.

Keep each language version semantically equivalent. Do not change the campaign intent between translations.

How language selection works

Netmera resolves the message language in this order:

  1. Check the selected language source.

  2. Find the matching language in the campaign.

  3. Send that version if it exists.

  4. Fall back to the default language if it does not.

Example:

  • Default language: English

  • Added languages: Turkish, Spanish

  • User language: German

  • Result: Netmera sends the English version

Best practices

  • Choose a widely understood default language.

  • Use Custom Profile Attribute if language preference is managed outside the device.

  • Test with users or devices that represent each target language.

  • Check translated button labels, links, and media before launch.

Last updated

Was this helpful?