Experiences by Jebbit enables you to create interactive experiences tailored to various regions and languages. By localizing and translating your campaigns, you can provide personalized content that resonates with diverse audiences. This guide outlines the steps to localize and translate your experiences effectively.
Furthermore, even if you are not using Localizations, you are able to very easily translate your experience into a different language while copying. Localizing and Translating an experience is accomplished when creating a copy of the experience.
Before you begin
Ensure your Experiences by Jebbit contract includes Localization support.
Review your campaign assets ahead of time to ensure they are ready for localization.
Identify the languages and formality preferences needed for each target audience.
Steps to Localize and Translate an experience
Duplicate an experience
Navigate to the Workbench and hover over the experience you wish to localize.
Click on the dropdown menu and select Duplicate.
In the modal that appears, assign a name to the copied experience.
Within the modal, click on Advanced Settings.
Under the Translate your experience section, choose the desired language from the dropdown menu.
If the selected language offers formality options, select either Formal or Informal based on your audience.
(Optional) select whether to Translate Dynamic Product Feed select all that apply. Click Apply.
Click on Localize Experience.
You'll be prompted to select a root campaign to tie the localized version to.
After selection, click Duplicate Experience to create the localized and translated experience.
Note: All Localizations will be tied to one root campaign, so you will not be able to tie a Localized campaign to another Localized campaign. You can identify your Localized campaigns by viewing the icons in the Workbench.
Localize an existing campaign
Open the existing campaign you wish to localize.
Click on the pencil icon next to the campaign name.
Select Localize your experience.
Choose the root campaign to associate with the localized version.
Click Save to finalize the localization.
Next Steps
Review the localized experience to ensure all elements are accurately translated and functioning as intended.
Test the experience thoroughly before publishing to your audience.
FAQ
Which languages are supported by Experiences by Jebbit?
We currently support the following languages for translation: Arabic, English, French, German, Japanese, Korean, Portuguese, Spanish and Thai. However, if there is a language that you need that is not currently supported, reach out to your Customer Success Manager or the Support Team to submit a request.
What service does Jebbit use to translate experiences?
Experiences by Jebbit uses Amazon's AWS translation services as the technology for the translation.
Can I translate my Dynamic Product Feed?
You have the option to translate key elements of the product feed from the copy modal. Just check off the Translate Dynamic Product Feed checkbox and select which elements you'd like translated.
If I translate my feed, does it override the original?
Your feed will be translated and saved as a new feed in your brand.
What are the limitations to DPF translation?
We presently cannot accommodate feeds with greater than 5000 products or Shopify feeds.
What happens if I localize an experience that uses Google Tag Manager or Google Analytics 4?
GTM and GA4 configurations generally copy over during localization. However, localization can impact data, so always thoroughly test your implementation in the localized version.
Here's a breakdown of key considerations:
Pixel ID (GA4 Measurement ID/GTM Container ID): In most cases, you do not need to update the pixel IDs for localized versions. However, if you require separate GA4 properties or GTM containers for each localized experience for more granular reporting, you would need to manually update them.
Testing:
Always test your GTM implementation in the localized experience before publishing.
Use the draft link of your localized experience to simulate user interactions.
Verify that events are firing correctly using tools like:
The browser's Inspect tools (Network and Console tabs)
Google Tag Assistant
Confirm that all expected data is being collected and reported accurately in your GA4 property.
Copying Functionality: When copying or localizing experiences, ensure that any options related to carrying over GTM or GA4 configurations are enabled.