-
Team, Business and Enterprise plans (not available for LSP plans)
Get in touch with Sales for licensing questions.
-
Ultimate and Enterprise plans (Legacy)
Get in touch with Sales for licensing questions.
With the Phrase TMS integration for Braze, customer engagement can be increased and growth driven into new markets with seamless localization. The integration enables Braze users to translate email templates and content blocks.
Translatable content elements:
-
Email templates created with HTML editor
-
Content blocks
Note
Due to continuous improvements, the user interface may not be exactly the same as presented in the video.
There are a number of use cases for the connector:
-
Project managers can add files directly to projects from an online repository.
-
Set up the submitter portal to allow Submitters to add files to requests directly from the online repository.
-
Use automated project creation (APC) to have new projects automatically created when a change in the specified workflow states is detected.
-
Selected content items are imported the very first time APC runs.
-
-
The connector API can be used to automate steps otherwise performed manually through the UI. Webhooks can be used to have 3rd party systems notified about certain events (for example, a job status change).
-
From the Settings
page, scroll down to the section.
-
Click on Connectors.
The page opens.
-
Click New.
The page opens.
-
Enter the obtained from the Braze site.
-
Enter the obtained from the Braze dashboard.
See the list of endpoints here: https://www.braze.com/docs/api/basics/
Please verify which URL is present in the Braze instance's dashboard.
-
Select how the connector should import email templates with linked content blocks.
-
Email templates import mode
-
Selected email template only
-
Include content blocks
-
-
-
Select how the connector should export email template translations.
-
Export mode
-
Create new item
-
Original item
-
Note
exports translations to the same template/block. Language segments are defined by provided custom attribute.
-
-
If is selected for the export mode, provide the .
When localizing templates that need to be exported with the mode in order to have a final multilingual output, consider that the mode will only treat content contained in the tag structure as content for localization and the rest will be ignored. In this mode, localizable content must be included in this structure in the body, subject, and pre-header.
Note
Language attribute defines language of if/elsif - structured segment.
In order to use the option, structure
if/elsif/else/endifcontent like this:{% if {{custom_attribute.${attribute_name}}} == 'da-DK' %}
danish content
{% elsif {{custom_attribute.${attribute_name}}} == 'pt-PT' %}
portuguese content
{% elsif {{custom_attribute.${attribute_name}}} == 'sv-SE' %}
swedish content
{% else %}
Original content
{% endif %}
The bold formatting of the content must be strictly followed otherwise it won’t work. Language attribute (in this case attribute_name) and languages/keys/values are of course modifiable.
Each language code can be used only once in the entire document in order to find where to export translations but multiple languages can be used for one segment.
Example:
{% elsif {{custom_attribute.${attribute_name}}} == 'de-DE' or
{{custom_attribute.${attribute_name}}} == 'de-AT' or
{{custom_attribute.${attribute_name}}} == 'de-CH' %}
-
Click Test connection.
A checkmark will appear if the connection was successful. A red exclamation point will appear if it wasn't. Hover over the icon to see additional details.
-
Click Save.
The connector is added to the list on the page.