By using the Marketing and support project type you can import, translate, and export content to Contentful, Contentful Native, Webflow, Iterable, Marketo, Freshdesk, Contentstack, Ditto, Hubspot, Intercom Articles, Salesforce CRM, Salesforce Knowledge, Storyblok, WordPress, Zendesk Dynamic Content, Zendesk Guide.
This project type helps translate landing pages, blog posts, emails, articles, user guides and all other content coming from the connected platforms.
Project type differences
The Marketing and support project editor differs from the Web and mobile project editor. Here are the main differences:
Such projects use the concept of entries. An entry is, for example, a blog post or an email template. Each entry is usually composed of multiple translation keys.
The editor allows connecting one content or customer support app.
The editor has a header that separates the keys of each entry.
Layout, formatting and embedded images are preserved.
Separate keys are created for each text unit: headers, paragraphs, etc.
You cannot add new keys or paragraphs or remove the existing ones inside the Lokalise editor. Layout changes should be performed on the connected third-party service and then re-uploaded to Lokalise. In this case, translations will be restored from the translation memory.
Keys are displayed in the same order as in the uploaded entry. You won't see the Sort button in the Lokalise editor.
Key names, descriptions, and other similar properties cannot be changed.
Regular content uploading or downloading is not available. Instead, there's a Content management tab where you can synchronize content with the connected app.
To get started, open your projects dashboard, click New project, and choose the Marketing and support option:
Enter the project name, choose the base language (the one you'll be translating from), one or more target languages (the ones you'll be translating into) and select a content integration you will be connecting to.
Please note that you should add the exact locales as you have in the third-party platform. For example, if you have
en-US locale in your content management system, you should select
en_US locale in Lokalise (dashes and underscores can be used interchangeably):
Once you are ready, click Create project.
Add the credentials required for the chosen integration. Here is an example for Iterable:
After setting the connection up, Lokalise will start collecting content available for translation. It might take several minutes.
Please note that when Lokalise imports your content from content sources (like Marketo, Salesforce, Iterable, and others), it initially converts formatted content into HTML. This process happens regardless of the original format the content is authored in. To learn more about this process and adjusting HTML parsing rules, please refer to the corresponding article.
Proceed to the Content management tab and to see the list of content available for localization. The content refresh 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
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.
If you upload multiple language versions of the same entry, and they contain minor layout differences (for example, some paragraphs are missing), Lokalise still will try its best to properly align the content without creating any weird extra keys. Learn more about this behavior in the corresponding document.
The project editor allows you to perform translations, review content and add new languages.
Each entry is represented by related fields. For example, an email on Iterable contains subject, preheader, and several body keys. Editing, searching, and applying bulk actions is possible across multiple files simultaneously.
Long HTML content will be segmented. For example, suppose we have the following email on Iterable with a relatively long body:
Then, on Lokalise you'll see the following keys:
This is convenient because translators can work on individual phrases rather than on a huge pieces of text.
Entries are ordered by the upload datetime (with the most recent files being shown first). Keys have a fixed order and are sorted the same way as they appear in the original entry.
Selecting entries for the editor
An entry is a single entity exported from the third-party system (for example, Iterable). Click the Entries button in the top menu to open the Entries widget:
Here you can see two different email templates, and both are currently displayed in the editor. Each email, in turn, is composed of multiple translation keys.
By using the Entries widget, you can:
Show and hide entries in the editor. Please note that if you've chosen to hide an entry, its content will be excluded from searching.
Delete files from the project by clicking on the trash bin icon next to the entry.
Please note that it will take several seconds to delete an entry and no progress indicator will be shown.
Search for specific entries.
Sort entries in the entries selector.
Please note that this sorting won't be applied to an order of entries in the editor.
Once you are done editing translations, you can export them back to the connected app. To achieve that, proceed to the Content management tab:
Switch to the Imported tab and pick one or more entries to export:
Then press Export:
Choose one or more languages and then press Export again:
This is it!
Marketing and support projects in the dashboard
Marketing and support projects are displayed in a similar way to Web and mobile and Ad hoc documents projects in the dashboard:
Here you can see the overall progress of your project as well as that of the languages.
However there are a few differences from a software projects:
You can track the progress of each entry in the project separately. Click on the entry name to view its content.
To the left you'll see the currently enabled apps for this project (Iterable in the example above).
There's no button to download translations as content will be sent back to the Iterable.