Import and export translations

Instead of generating translations with AI Translate, bring your own from a translation vendor, a spreadsheet, or another Pushwoosh preset.

Open Content → Push presets, open the preset, then use Import or Export next to the language selector in the Push presets editor.

• Export: download the current title, subtitle, and message for every language as a CSV to translate elsewhere or reuse in another preset.
• Import: upload a CSV or JSON file to apply translations to this preset.

Note

Import and Export cover only title, subtitle, and message text. They do not move images, buttons, links, or other preset settings.

Export the current content

Click Export to download the preset’s title, subtitle, and message for every language it currently has, including the default one, as a CSV file. The download name looks like welcome-series-translations.csv (the preset name, slugified, then -translations.csv).

The file looks like this:

language	title	subtitle	message
default	Welcome to our app!		Thanks for installing.
es	¡Bienvenido a nuestra app!		Gracias por instalar.
de	Willkommen in unserer App!		Danke fürs Installieren.

Import translations into the preset

Prepare the file

Use the CSV from Export after you edit it, or build a file that matches the same layout. Import also accepts .json.

• language: required header column. Write each code the same way it appears in the language selector, for example zh-Hant for Traditional Chinese. Letter case does not matter (ES and es both work). If the import preview lists a code Pushwoosh does not recognize, fix it in the file and import again. That language will not be sent to anyone until the code is valid.
• title, subtitle, and message: optional. Columns can be in any order. A column you leave out is treated as blank for every row, the same as an empty cell in a column you kept. Each following row is one language.

Note

subtitle shows on iOS only, the same as when you add a subtitle in the editor.

Use a JSON file instead of CSV

If your vendor or team already sends a .json file, Import accepts it too. You do not need JSON if you work with the CSV from Export.

• Same fields as the CSV: title, subtitle, and message, grouped by language code:

  {
    "default": { "title": "Welcome to our app!", "message": "Thanks for installing." },
    "es": { "title": "¡Bienvenido a nuestra app!", "message": "Gracias por instalar." }
  }

• The same shape the Presets API uses for localizedTitle, localizedSubtitle, and localizedContent (these match the CSV columns title, subtitle, and message). Useful if you already export presets through the API:

  {
    "localizedTitle": { "default": "Welcome to our app!", "es": "¡Bienvenido a nuestra app!" },
    "localizedContent": { "default": "Thanks for installing.", "es": "Gracias por instalar." }
  }

Note

To update many presets at once from scripts, ask your development team to use the Presets API UpdatePartial call. For one preset in the Control Panel, use Import on this page. It takes the same localizedTitle, localizedSubtitle, and localizedContent maps.

Import the file

1. Click Import next to the language selector.
2. Choose a .csv or .json file. The preview shows how many languages will be applied, how many of those are new to this preset, and how many are skipped.
3. Check Overwrite languages that already have text only if you want the file to replace existing translations. Leave it unchecked to fill empty languages and add new ones without changing text you already wrote.

4. Click Import.

After import, switch the language selector to a language from the file and confirm the title and message look right.

Note

A language is skipped when nothing in its row would change anything:

• every field in the row is blank, or
• the preset already has text in every field that row fills in, and Overwrite languages that already have text is off.

A language in the file that isn’t in the preset yet is added automatically. An empty cell or field never clears existing text, even with Overwrite checked. It’s only skipped, not written as blank.

If Pushwoosh can’t read the file

Instead of a preview, you see one of these messages:

Message	When it happens
The file is empty.	The file has no content.
The file is not valid JSON.	A .json file (or a file starting with {) can’t be parsed as JSON, or its top level isn’t an object.
The CSV file has no “language” column.	The header row of a CSV file is missing the language column.
The file has no translations.	Every row, or every JSON entry, is missing a language code.