If you are a global brand that runs Jebbit experiences in multiple regions you may wish to take the same underlying experience but run it in a different language and display different product recommendations for each region. This is a Localization.
If your Jebbit contract includes Localization support, you will be given the proper permissions to localize your campaigns which will help you track your usage against your contract utilization.
Further, 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.
Video Tutorial
Step-by-Step Guide
The option to copy an experience is found either by hovering over the experience in the Workbench, or within the toolbar in the upper right corner of the Builder Map. You will need to start by creating a copy of an experience which will open the Copy menu.
To take an existing experience and copy the same experience to a new language, select the language you want from the dropdown within the Copy menu:
When copying a campaign, you will notice the option to 'Localize'. We will default to localizing the campaign you are copying, but you can choose any campaign to tie the Localization to (even campaigns you have access to under your parent brand).
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.
If an existing campaign is technically a Localization of another root campaign, you can still make that designation without having to start a new copy. To Localize an existing campaign, click on the campaign name from the navigation within the Builder Map, and select the 'Localization' check box. You just need to tie the campaign you're localizing to a root experience.
Frequently Asked Questions
Can I specify the formality of the translation?
If you are translating your experience to a language that offers both a formal and informal translation option, then you will see the option to specify which one you want after selecting the language.
Which languages are supported 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?
The Jebbit platform uses Amazon's AWS translation services as the technology for the translation.
Can I translate my Dynamic Product Feed?
Yes! 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. Keep an eye out for updates in the future!
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.