SFMC email and content localization
Localization Workflow for Salesforce Marketing Cloud teams.
How Campaign Builder helps teams translate Salesforce Marketing Cloud email and content variants while preserving campaign intent, tone, HTML structure, personalization tokens, and reviewed SFMC write boundaries.
What it supports
Concrete workflow support, not generic AI copy.
This use case is grounded in implemented Campaign Builder routes, agents, shared SFMC clients, and documented review boundaries.
Shared localization helpers normalize targetLanguages, targetLocales, targetLocale, language names, locale codes, and aliases before translation work begins.
Email Agent can translate subject lines, preheaders, HTML content, and slot-based email content after a preview or brief has loaded enough source material.
Content Agent can localize generated copy, campaign story fields, and email draft fields, then return localizedVariants or persist translated story metadata.
Translator Agent can save reviewed localized variants to Content Builder when asset type, folder, link template, fallback URL, and SFMC credentials are configured.
Implementation map
What technical evaluators can trace.
Localization support is shared through `utils/localization.js`, including locale normalization, account translator configuration, Content Builder URL construction, and token-preserving translation helpers.
Content Agent localization is mounted under `/api/v1/agent/content/*` and supports targetLocales, targetLocale, targetLanguages, sourceLanguage, tone, account style context, and generated draft localization.
`POST /api/v1/agent/content/:id/translate` stores translated title, description, and instagram_caption fields under story metadata translations with targetLocales and translatedAt.
Email Agent translation is documented through the `email.translate` skill and returns localizedVariants with translated subjectline, preheader, htmlContent, slots, and dirty review state.
The narrower authenticated helper `POST /api/v1/translate` remains available for Spanish title, description, and caption translation.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Localization creates translated variants, metadata, or configured Content Builder assets; it does not send campaigns or activate journeys.
Boundary
Translation prompts preserve URLs, personalization tokens, AMPscript, placeholders, class names, IDs, punctuation, whitespace, and HTML structure where preserveHtml is enabled.
Boundary
Content Builder saves depend on authenticated account context, available SFMC credentials, and configured translator asset settings rather than unrestricted asset writes.
Boundary
Email localization returns reviewable variants and dirty state before teams apply subject, preheader, HTML, or slot updates through confirmed write paths.
FAQ
Evaluation questions for Localization Workflow.
Can Campaign Builder localize SFMC email assets?
Yes. Email Agent can translate subject lines, preheaders, HTML content, and slot content when the connected account can preview enough source email content.
How does Campaign Builder protect SFMC-specific syntax during translation?
The shared localization prompts preserve URLs, personalization tokens, AMPscript, placeholders, class names, IDs, punctuation, whitespace, and HTML structure where requested.
Can localized variants be saved to Content Builder?
Yes, through Translator Agent configuration for asset type, folder, link behavior, and SFMC credentials. The page does not claim unrestricted Content Builder writes.
Next step
Review this workflow against your SFMC setup.
Bring one existing campaign, journey, email, Content Builder process, or Data Extension workflow to the demo so the evaluation can stay concrete.