Four steps. No middleware.
Everything happens inside Salesforce Marketing Cloud. No external send domain, no proxy, no extra deliverability risk.
Where every piece lives.
MCT is a Content Builder block and a Data Extension cache. That's the whole surface area.
From install to first multilingual send.
- 01
Install the MCT block
Deploy the MCT installed package into your Marketing Cloud org. The block appears in Content Builder alongside your existing blocks.
- 02
Configure the block
Pick the source email by Asset ID or Customer Key, choose target languages, add do-not-translate terms and a naming prefix for the generated blocks.
- 03
Translate & preview in-browser
MCT's backend recursively assembles the email (templates → slots → blocks), stashes AMPscript, calls Google Cloud Translation v2 in chunks, and streams every language back into an editable preview.
- 04
Compile the switch email
MCT writes one content block per language (prefix__es, prefix__fr, ...) and rewrites the block into a single AMPscript IF/ELSE switch using ContentBlockById. Marketing Cloud picks the right language per subscriber at send.
Nothing hidden. Nothing external at send.
- Inside your SFMC: block UI, per-language content blocks, compiled IF/ELSE email, sends
- Inside MCT backend: recursive assembler, AMPscript stash, Google Cloud Translation calls
- Deployable on Azure App Service, SFMC CloudPages (SSJS), or a PHP host
- · MCT Content Builder block
- · Per-language content blocks (prefix__es, prefix__fr, ...)
- · Compiled AMPscript IF/ELSE switch email
- · Sends, IPs, tracking, journeys
- · Recursive email assembler (templates → slots → blocks)
- · AMPscript / personalization stash + restore
- · Google Cloud Translation v2 (chunked, DNT-aware)
- · SFMC REST client with least-privilege OAuth
Runs where your infra already lives.
Same MCT block, three hosting shapes. Pick the one your team already operates.
Default. Node.js backend, secrets in Azure Key Vault, path-based routing lets one instance serve multiple SFMC orgs.
Zero external infra. Runs entirely on Marketing Cloud CloudPages using Server-Side JavaScript for teams that want the backend to live inside SFMC.
Drop-in PHP variant for teams standardized on shared PHP hosting. Same block, same compile output.
Up and running in less than a day.
- Hour 0Admin installs the MCT package into the Marketing Cloud org.
- Hour 1Create an API integration and issue OAuth 2.0 client-credentials with Saved Content read + write scopes.
- Hour 2Configure the MCT backend (Azure App Service, CloudPages, or PHP host) with credentials in the managed secret store.
- Hour 3Drop the block into a first email, pick languages, add DNT terms, translate and preview.
- Hour 24First compiled switch email sends. Reruns overwrite by naming prefix.
Least-privilege by design.
MCT authenticates with OAuth 2.0 client-credentials and requests only Saved Content read + write. Client IDs and secrets live in a managed secret store, never in code or the block config.
Ready to see the four steps live?
Bring your sandbox. We'll install, translate a campaign, and send it in 5 languages, inside 30 minutes.
