SFMC localization workflow
How Campaign Builder localizes email and content for Marketing Cloud review.
Campaign Builder localization is built into Content Agent, Email Agent, Translator Agent, and shared translation helpers. It helps teams produce locale-specific variants while preserving SFMC tokens, HTML structure, tone, and review boundaries.
Localization path
From target locale to review-ready translated variant.
The implementation treats localization as campaign production support. It normalizes target locales, keeps tone and source-language context with the request, and returns translated variants that marketers can inspect before SFMC updates.
Normalize locale intent
Shared localization helpers parse targetLanguages, targetLocales, targetLocale, language names, locale codes, and aliases into deduped locale targets before Content or Email work begins.
Preserve campaign meaning
Translation prompts can include sourceLanguage and tone guidance, and they instruct the model to preserve URLs, personalization tokens, AMPscript, placeholders, punctuation, and whitespace.
Localize email surfaces
Email Agent can translate subject lines, preheaders, HTML content, and slot-based email content after an SFMC email preview or email brief has loaded enough transformable content.
Create localized content variants
Content Agent can localize generated copy, campaign story fields, and email draft fields, then return localizedVariants or persist translated metadata for later review.
Implementation map
What evaluators can trace to localization routes and helpers.
Localization is not just homepage positioning. It is implemented across shared helpers, specialist agents, and authenticated tool routes that produce translated variants, metadata, or configured Content Builder assets.
utils/localization.js normalizes languages and locales, maps language codes to default locales, loads account translator configuration, and builds SFMC Content Builder asset URLs.
translateCopy and translateVariants preserve HTML when requested and avoid translating URLs, personalization tokens, AMPscript, placeholders, class names, and IDs.
Email Agent translation uses targetLocale or targetLanguages, sourceLanguage, tone, and preserveHtml, then returns localizedVariants with translated subjectline, preheader, htmlContent, slots, and dirty review state.
Content Agent localization uses targetLocales, targetLocale, targetLanguages, sourceLanguage, tone, and account style context to translate generated drafts and story metadata.
POST /api/v1/agent/content/:id/translate stores translated title, description, and instagram_caption fields under story metadata translations with targetLocales and translatedAt.
Translator Agent can save localized variants to Content Builder with configured asset type, folder, link template, and fallback URL settings when SFMC credentials are available.
POST /api/v1/tools/translate remains a narrower authenticated helper for Spanish title, description, and caption translation.
Evaluation evidence
Ask for proof that localization is preserving SFMC-ready structure.
A useful localization demo should leave reviewable artifacts, not just translated prose. The implemented flows expose normalized locale targets, localized variants, saved translation records, metadata translations, and configured export details that an SFMC team can inspect before applying changes.
Parsed target locale set
Ask to see the normalized targets produced from targetLanguages, targetLocales, or targetLocale. The helpers dedupe language names, locale codes, aliases, and comma- or slash-separated input before a translation run starts.
Token and HTML preservation
Use a sample with links, personalization strings, AMPscript, SSJS, classes, IDs, and table markup. The output should translate human-readable copy while keeping those SFMC-specific structures intact for review.
Localized variant payload
For Email Agent and Content Agent flows, inspect localizedVariants or translated draft fields rather than accepting only a chat response. Review subjectline, preheader, HTML, slots, labels, locale codes, and dirty review state.
Story translation metadata
For Content Agent story localization, verify that title, description, and instagram_caption translations are stored under metadata translations with targetLocales and translatedAt so regional variants remain traceable.
Translator context and saved translations
Translator Agent keeps account-scoped chat logs, reusable context, saved translation documents, feedback, and recent translation lists so evaluators can inspect what source material produced the localized asset.
Configured Content Builder export
When a translation is exported to SFMC, check the configured asset type, folder ID, customer key, SFMC asset ID, generated URL, and translator_exports record instead of treating Content Builder writes as unrestricted.
Technical evaluator FAQ
Where localization helps, and where review still matters.
The safest evaluation lens is practical: Campaign Builder can create translated working assets and variants, while SFMC launch decisions stay with the team inside Marketing Cloud.
Does localization automatically send or activate campaigns?
No. Localization creates translated copy, variants, metadata, or configured Content Builder assets. Sends, journey activation, and final launch decisions remain reviewed Marketing Cloud steps.
Which campaign fields can be localized?
Implemented flows cover generated content text, story title/description/instagram_caption metadata, email subject lines, preheaders, HTML content, and slot-based email content when enough source content is loaded.
How are SFMC-specific tokens protected?
Translation prompts explicitly preserve URLs, personalization tokens, AMPscript, placeholders, class names, IDs, punctuation, whitespace, and HTML structure where preserveHtml is enabled.
How should evaluators test localization safely?
Use loaded previews or draft content, request explicit target locales, inspect localizedVariants and metadata translations, and verify any Content Builder save uses configured account or environment translator settings.
Enterprise guardrails
Translation stays scoped to reviewable campaign work.
Localization uses the same Campaign Builder pattern as other execution flows: authenticated context, scoped account configuration, explicit variant output, usage logging, and review before production-bound SFMC changes.
Authenticated account context
Localization routes run behind authenticated Campaign Builder agent or tool APIs before content records, style context, account settings, OpenAI usage logs, or SFMC credentials are used.
Reviewable variants before writes
Email localization marks translated briefs as dirty review state and returns localized variants, so teams can inspect subject, preheader, HTML, and slot changes before applying SFMC updates.
Configured SFMC saves
When localized content is saved to Content Builder, the asset type, folder ID, and content link behavior come from account or environment translator configuration rather than an unrestricted write path.
Evaluation takeaway
Localization reduces regional production handoffs without removing review.
A buyer evaluating Campaign Builder localization should expect locale-aware translated variants for content and email work, protection for SFMC-specific markup, and configured Content Builder saves where enabled. They should not expect automatic sends or unrestricted Marketing Cloud writes.