By using the Marketing and support project type, you can import, translate, and export content to:

This project type helps translate landing pages, blog posts, emails, articles, user guides, and all other content coming from the connected platforms.

Video tutorials

Webflow

Iterable

Zendesk Guide

Project type differences

The Marketing and support project type works differently from the Web and mobile project type. The editor and workflow are designed for content like blog posts, email templates, help center articles, and similar structured text.

Key differences:

These projects are organized into entries. An entry represents a piece of content, such as a support article or email template, and usually contains multiple translation keys.
The project is connected to one specific content or support platform (e.g., Contentful, Zendesk, Iterable). All content exchange goes through this integration.
The editor includes a header section that separates entries and shows which keys belong to each one.
The editor keeps the original layout, formatting, and images where possible. (Some formatting limitations may apply.)
Lokalise generates separate keys for different text elements (headings, paragraphs, etc.).
You cannot add or remove keys directly in the Lokalise editor. To change the structure (like adding a new section), you must update the content in the connected platform and reimport it into Lokalise. Translations will remain intact via translation memory.
Keys appear in the same order as in the original entry. There is no sort button in this editor.
You cannot modify key names, descriptions, or similar attributes in this project type.
Content management is done from a Content tab, which lets you pull new or updated entries from the connected application and push translations back.

Getting started

To get started, open your Projects dashboard and click New project. Select the Marketing and support project type:

Choose the base language (the language you'll translate from).
Select one or more target languages (languages you'll translate into).
Choose the content integration you plan to connect (for example, Contentful, Iterable, or Zendesk).

Make sure to add languages exactly as they exist in your content platform.
For example, if your CMS uses en-US, select en_US in Lokalise (dashes and underscores are interchangeable).

When everything is set, click Create project.

Next, enter the integration credentials required to connect the external service.
For example, when connecting Iterable, you’ll need to provide the relevant API key and configuration details.

View image

Once the connection is set up, Lokalise will begin fetching content from the linked platform. Depending on the amount of content, this may take several minute

Importing content

When importing content from platforms like Marketo, Salesforce, or Iterable, Lokalise converts formatted text into HTML, regardless of the original format.

If you need more control over how formatting is handled, see the HTML parsing article for details and customization options.

To view and import content, go to the Content management tab. Lokalise will start refreshing content automatically. If it doesn’t, click Refresh.

In the Available for import view, select one or more items and click Import to Lokalise.

You’ll see a dialog where you can:

Choose which languages to import.
Enable Overwrite existing keys if you want to update keys already stored in the project.

The import runs in the background. When it’s finished, you’ll receive a notification.

Click View activity if you'd like to see how many keys were created or updated.

Once content is imported, return to the Editor and perform translations as usual, or create tasks for your translators.

If you import multiple language versions of the same entry and there are small layout differences (such as missing paragraphs), Lokalise will try to align entries automatically so duplicate or misaligned keys are not created. For more details, see the Translation alignment document.

Project editor overview

The project editor is where you translate and review content, as well as manage project languages.

In Marketing and support projects, each piece of content is displayed as an entry. For example, an email from Iterable might include keys for the subject, preheader, and multiple body sections. You can search, filter, and apply bulk actions across entries.

Entries are listed by upload time, with the most recent ones shown first.
Keys inside an entry appear in the same order as in the original source content.
The order of keys is fixed and cannot be rearranged in the editor.

This ensures that translations stay aligned with the structure of the original content when synced back to the connected platform.

If an entry contains long HTML text, Lokalise will segment it into smaller parts. For example, a long email body will appear as a series of shorter keys in Lokalise.

This makes translation easier: instead of working on one large block of text, translators can work on smaller, clearer sections.

Selecting entries for the editor

An entry is a single piece of content imported from your connected platform (for example, an email template from Iterable). To manage which entries are shown in the editor, click Entries in the top menu to open the Entries panel.

In this panel, you’ll see a list of all imported entries. Each entry may contain multiple translation keys (such as subject, preheader, and body sections).

Using the Entries panel, you can:

Show or hide entries in the editor. If an entry is hidden, its keys are not shown in the editor and are excluded from search results.
Delete entries by clicking the trash bin icon next to the entry.
Deletion may take a few seconds and does not display a progress indicator.
Search for specific entries by name.
Sort entries in the selector. Note that sorting affects only how entries appear in the selector, not the order they appear in the editor.

Exporting content

After translations are complete, you can sync the updated content back to the connected platform. To do this, go to the Content management tab.

Switch to the Imported view and select one or more entries you want to export.

Then press Export:

Choose the languages to include and click Export again.

Lokalise will send the translated content back to the connected app. That’s it.

Marketing and support projects in the dashboard

Marketing and support projects appear in the dashboard the same way as Web and mobile or Ad hoc documents projects. You can see the overall translation progress and the progress for each language.

However, there are some differences:

You can track progress per entry. Click an entry name to open and review its content.
On the left side, you’ll see the apps connected to this project (for example, Iterable).
There is no Download button, because content is returned to the connected platform through the export process instead of being downloaded as files.

Known issues and technical limitations

Image handling in Marketing and support project types

When using Marketing and support projects, localized images in target-language articles are not preserved during retranslation.

For example, if you update an English article in Intercom, retranslate it in Lokalise, and then export the updated versions back to Intercom, all target-language articles will once again display the English images. Any localized screenshots or visuals you previously added to the target-language articles will be overwritten.

This behavior affects all Marketing and support content integrations and is due to current technical limitations.

Suggested workaround

It is currently not possible to automatically preserve localized images during the retranslation process. While this is not an ideal solution, you can reduce the need to reapply images manually by adjusting your project’s HTML parsing rules.

In your Marketing and support project, go to Settings > HTML parsing rules.
Locate the following block:

img:
  ruleTypes: [ATTRIBUTES_ONLY, INCLUDE]
  elementType: image
  translatableAttributes: [title, alt]
  writableLocalizableAttributes: [href, src]

Modify the translatableAttributes line so it becomes:

translatableAttributes: [title, alt, src]

(note the addition of src)

Do not change or remove any other lines.
Save the changes.

After applying this update, the Lokalise editor will display additional keys containing the image URLs for both source and target languages. This allows you to translate or replace image links directly within Lokalise instead of reapplying images manually after every retranslation.

Ad hoc documents project type