Translate and localize experiences
Adobe GenStudio for Performance Marketing offers out-of-the-box translation on the HTML canvas so global and regional marketers can scale approved experiences into multiple languages without external translation tools.
The feature uses Azure Open AI by default. Your organization can also connect a preferred translation service through translation extensions.
Translation starts from an approved experience saved in Content. The source experience can be in any language. Each translated variant opens on the Create canvas as an editable draft that you can export, send for review, and publish as a separate experience.
Supported experiences
Out-of-the-box translation on the HTML canvas supports:
- Email experiences
- Paid media experiences, including Meta, LinkedIn, and Display ads
Before you begin
Confirm that the experience you want to translate is approved and available in the Content Experiences gallery. Draft or in-review experiences are not eligible translation sources.
If your organization registers a custom translation extension, GenStudio for Performance Marketing uses that service instead of the default Azure Open AI translation. See Find translation extensions.
Translate from Create translate-from-create
Start a translation from the Create landing page to localize an approved experience.
To translate from Create:
- In Create, scroll to the Content creation section.
- Click Translate & localize copy.
- Select the approved email or paid media experience that you want to translate. Click the Use button.
- Select target languages from the list of supported languages. Click Translate.
Translated variants appear on the canvas.
Translate from Content translate-from-content
You can also start translation from Content when you are browsing approved experiences.
From the Experiences gallery
To translate from the Experiences gallery:
- In Content, open the Experiences tab.
- Locate the approved experience that you want to translate.
- Click the options (three dots) menu on the experience card.
- Click Translate.
- Select target languages from the list of supported languages. Click Translate.
Work with translations on the canvas
On the HTML canvas, the source experience cannot be edited because it is already approved. Email source experiences appear locked. You can edit text in translated variants directly on the canvas. See Manage variants for guidance on editing variant copy.
Translated experiences do not run brand validation or display a brand score. The source experience was already created with brand guidelines, reviewed, and approved.
Fragment regeneration is not supported for translated experiences.
Delete a translated language
To remove a translated language from the canvas:
- On the Create canvas, click the options (three dots) menu on the translated variant header.
- Click Delete.
The translated language is removed from the canvas.
Refresh a paid media translation
After you edit translated paid media copy, you can reload the original translation output.
To refresh a paid media translation:
- On the Create canvas, open the options menu on the edited translated variant.
- Click Refresh translation.
Export, review, and publish
After translations load on the canvas, you can export them, send them for approval, and publish approved variants to Content.
To export translated experiences:
-
On the Create canvas, click Export in the toolbar.
-
Select an export format.
- Email: CSV and images or HTML only
- Paid media: CSV + JPG, CSV + PNG, or HTML + images
-
Click Export.
You can also export experiences from Content.
To request review and approval:
- On the Create canvas, click Request approval.
- Assign at least one approver and send the request.
See Request review and approval for details on the review workflow.
To publish approved translations:
- After approvers approve the translated variants, click Publish.
- In the publish window, confirm metadata such as campaign name, timeframes, regions, and keywords.
Each published translation is saved to Content as a separate experience.
Translated experience metadata
Published translations include metadata that links each variant back to its source, including:
- Title — follows the pattern
Translation from "<source title>" <channel>, such asTranslation from "Summer campaign" Meta - Created by — the user who initiated the translation
- Created date — the date of the translation
- Translated source — a link to the source experience in Content
- Translated from — the source language
Limitations
Keep the following constraints in mind when you translate experiences on the HTML canvas:
- The source experience must already be approved and saved in Content.
- Brand validation does not run on translated variants.
- Fragment regeneration is not supported on translated experiences.
- Refresh translation is available for paid media only.