Multilingual Email for Marketing Cloud.
Built for campaigns that can't afford to get it wrong.
Subject
Your September statement is ready
Hi Sarah,
Your September statement is now available. This month you earned 2,340 reward points and saved $48 with member pricing.
Translate once
Subject
Tu estado de cuenta de septiembre está listo
Hola Sarah,
Tu estado de cuenta de septiembre ya está disponible. Este mes ganaste 2.340 puntos de recompensa y ahorraste 48 $ con precios para miembros.
Today vs. With MCT
Scroll in to watch each side load. Flip the switch to compare the outcomes.
- Loop recipientsrunning...
- 2Call translation API~180ms
- 3Wait for response~180ms
- 4Build HTML with AMPscript~180ms
- 5Send email
- API cost + latency scale with your list, not your content.
MCT closes this gap by translating once in-browser, stashing AMPscript safely, and compiling every language into one email with a native IF/ELSE switch. Your Content Builder workflow doesn't change.
How MCT Solves It
Click a tab to watch the code type in and the live result render beside it.
Pick your locales in Content Builder. MCT calls the translation service a single time per language and stores each result as a first-class content block.
A Bento of Built-in Superpowers
Purpose-built for Salesforce Admins who ship multilingual email at scale.
Translate Once, Not Per Send
A single API call caches every language as a reusable block. Cost and send speed never scale with your list size.
Native Content Builder Block
Drop translation into any email alongside existing blocks. Zero custom code.
No Per-Send Cost
Sending to 1k or 1M subscribers costs the same. The API fires once, not per recipient.
Human-Reviewable
Every language is an editable block you can review before it ships.
Per-Subscriber Language at Send
Serve each subscriber their language automatically from your Data Extension locale field. No separate send per market.
Reuse Everywhere
Translated blocks live in Content Builder as first-class assets. Drop them into any future email or journey.
Top Use Cases
Real campaign scenarios where multilingual automation delivers measurable results. Tap any card.
Language rules are tightening.
Your ESP isn't tracking them.
Quebec's Bill 96, EU accessibility directives, and market-specific language mandates now shape how you can email customers. Compliance is no longer about having a translation available, it's about quality, consistency, and auditability. MCT keeps every translated block versioned inside Content Builder, so approvals and audits stay where your team already works.
How It Works
Click a step to see the exact screen your Salesforce admin will use.
Configure the block in Content Builder
Drop MCT into an email, pick the source by Asset ID or Customer Key, choose target languages, add do-not-translate terms for brand and product names, and set a naming prefix.
Enterprise-grade security.
No exceptions.
MCT runs with least-privilege OAuth 2.0 client-credentials scoped to Saved Content read and write. API keys and client secrets live in a managed secret store, never in the block config or source. Translated blocks and the compiled switch email stay inside your Marketing Cloud instance.
See MCT in Action
Watch how easy it is to add multilingual email to your Marketing Cloud sends.
Frequently Asked Questions
What is MCT and how does it integrate with SFMC?+
MCT is a native Content Builder block for Salesforce Marketing Cloud Engagement, distributed as an installed package. Drop it into any email, pick your languages, and MCT writes one content block per language plus a single compiled email that switches on the subscriber's locale.
Does MCT protect my AMPscript and personalization strings?+
Yes. MCT stashes AMPscript blocks, %%=v(@field)=%% substitutions and personalization tokens before sending copy to Google Cloud Translation, then re-injects them after translation. Nothing personal or dynamic ever hits the translator.
Can I keep brand names and product terms untranslated?+
Yes. Add do-not-translate terms in the block config. MCT preserves them exactly across every language, including in nested templates and slot content.
Does MCT handle nested templates and slot-based emails?+
Yes. MCT walks templates, slots, and blocks recursively so a template that references other blocks gets fully assembled and translated in one pass.
Where does MCT run?+
The backend runs on Azure App Service by default and can also be hosted on Marketing Cloud CloudPages using SSJS, or on any PHP host. Path-based routing means one instance can serve multiple SFMC orgs.
How is subscriber data secured?+
Compiled emails and translated blocks live natively in your Content Builder. Auth uses OAuth 2.0 client-credentials with least-privilege scopes (Saved Content read/write). API keys and client secrets live in a managed secret store, never in code or the block config.
Which Marketing Cloud edition do I need?+
Marketing Cloud Engagement with Content Builder. MCT does not run on Marketing Cloud Growth, Advanced, or Account Engagement (Pardot).
What happens when I change the source email?+
Click Translate again. MCT re-runs the recursive assembly, re-translates changed content, and overwrites the language blocks by key. You review, and the compiled switch email picks up the new versions automatically.
Ready to speak every subscriber's language?
Book a demo and see MCT in action inside your Salesforce Marketing Cloud.