Iterable is a cross-channel marketing platform that powers unified customer experiences and empowers you to create, optimize and measure every interaction across the entire customer journey.

Lokalise enables you to translate Iterable emails, as well as push, SMS and in-app notifications.

Currently it's not possible to localize message templates that were created with the Drag-and-Drop editor as it will result in a mismatch between the JSON content generated by the editor and the translated HTML content. We recommend using either the WYSIWYG editor or Side-by-Side editor to create the templates you plan to localize with this integration.

If you want to continue using the Drag-and-Drop editor to create your templates, there are a couple of workarounds you can use to convert the HTML for localization:

Before using this app, you should add all the necessary locales on Iterable. To achieve that, proceed to Iterable, click on the "cog" icon in the top menu and choose Project settings:

Find the Locales section and add your locales by pressing on the corresponding button:

Please note that your locales should be equal to language ISO codes in your Lokalise project.

To install app, you'll need to generate an Iterable API key, therefore click Integrations > API keys:

Next click Create API key button in the top right corner:

Give your key a name and make sure to choose Server-side type:

Once you are ready, click Create.

Finally, copy your key:

Please note that you won't be able to see the key once you close this dialog therefore make sure to copy the key right away.

To install the app, open your Lokalise project and click Apps in the main menu. Find Iterable in the apps list, and click on it:

Next, click Install. You'll be presented with the following screen:

Enter your Iterable API key in the corresponding field and press Authorize.

Once you install the app, the list of available templates on Iterable will be presented to you. The refresh of the content should start immediately; otherwise, click Refresh:

On the Available for import view, choose one or more items and click Import to Lokalise. You'll be presented with the following dialog:

Choose the languages to include in the import operation.

Tick the Overwrite existing keys option if you want to update existing translation keys with any updates that happened on the Iterable content since the last import. Updated keys will return to the Unverified status.

If you want to use Automations, you should import only the default language with the Overwrite existing keys option enabled. An alternative is to import all the desired languages, but keeping the Overwrite existing keys option disabled.

Importing will happen in the background, and once the operation is completed, you'll see the following notification:

Click View activity if you want to see how many keys were created.

Now you can return to the Editor and perform translations as usual, or create tasks for your translators.

In certain occasions, the content on Iterable might go through some updates before the translations were finished, or even after they were exported. In that case, you can use the Refresh button to see the last update date, select which items you want to reimport, and click on Reimport to Lokalise.

Once the translations are reviewed, return to the Iterable app on Lokalise, and switch to the Translation in progress view. Choose one or more items that are Ready to export and click Export to Iterable.

You'll be presented with the following dialog:

Choose one or more languages and hit OK. The operation will be performed in the background, and you'll be notified once it is completed.

Once you've exported the item in all languages, you'll find them under the Translation exported view.

Note that if the app is reinstalled, translation statuses of all items are kept. If you want to clean the previous statuses of your items, you need to delete the keys from the Editor.

Please note that as you mark your translations as reviewed on Lokalise, their statuses will change under the Translation in progress view. For example, if your project has three languages and you've reviewed the translations for one language only, you'll see the 1 of 3 languages translated label.

Only once you have reviewed translations for all languages, the global status for the given item will change to Ready for export.

You can export any items even if their status is not Ready for export.