Features

Everything you need to ship multilingual email.

Purpose-built for Salesforce Marketing Cloud. Nothing to integrate, nothing to maintain.

Why MCT vs. the alternatives

The same job, three very different bills.

What multilingual email really costs when you do it yourself, bolt on middleware, or run MCT.

DIY / duplicate emails

Translation middleware

MCT

Lives inside Content Builder

Translation cost per send

N/A

Per recipient × languages

Zero

Cached & reusable across campaigns

Same deliverability & IPs

Setup time

Days per campaign

Weeks

Under 24 hours

Right-to-left languages

Depends

Editable strings before send

Capabilities

Every capability, in one Content Builder block.

Native Content Builder blocks

Drag it in, pick a source language, and every locale renders inline, no external editor, no copy-paste.

42+ languages, one workflow

Every major EMEA, APAC and LATAM locale. Add a language once and it applies to every future send.

Translations cached forever

You pay per translation, not per send. Reuse across journeys, campaigns and triggered sends.

Personalized at send time

AMPscript picks the right variant per subscriber based on the language field you already store.

No per-send fees

Flat per-org license. Ship 10M sends or 10, the price is the same.

Reusable everywhere

Translated blocks live in your Content Builder library. Any email in the org can drop them in.

Right-to-left safe

Arabic, Hebrew and Farsi render with correct direction, mirrored buttons and preserved layout.

Zero middleware

No proxy, no external send API, no new deliverability domain. Marketing Cloud sends as usual.

Preview every locale

Switch language in-editor and see subject, preheader and body update instantly.

One-click retranslate

Update source copy and MCT queues only the changed strings, the rest stay cached.

AMPscript-safe translation

Your AMPscript is stashed, not translated.

Before any copy leaves for Google Cloud Translation, MCT extracts every AMPscript block, %%=v(@field)=%% substitution and personalization token, replaces them with placeholders, then re-injects them into the translated output. Your dynamic logic is round-tripped intact in every language.

AMPscript blocks stashed with unique keys
%%=v(@field)=%% and %%Field%% preserved
Do-not-translate terms enforced per block
Chunked into 18KB batches for large emails

stash → translate → restore

Hola %%FirstName%%, tu pedido
%%[ IF @vip == true THEN ]%%
  premium está listo.
%%[ ELSE ]%%
  está listo.
%%[ ENDIF ]%%

✓ 0 personalization tokens leaked to translator

Recursive assembly

Nested templates, slots, blocks. One pass.

MCT walks the Content Builder tree recursively so templates that reference other blocks or slots get fully assembled before translation. The result is a single compiled email with per-language content blocks wired into an AMPscript IF/ELSE switch using ContentBlockById.

Walks templates → slots → blocks recursively
Writes one block per language (prefix__es, prefix__fr, ...)
Compiles a single IF/ELSE switch email
Reads any subscriber locale attribute or DE field

compiled switch email

%%[ SET @loc = AttributeValue("Language") ]%%
%%[ IF @loc == "es" THEN ]%%
  %%=ContentBlockByName("welcome__es")=%%
%%[ ELSEIF @loc == "fr" THEN ]%%
  %%=ContentBlockByName("welcome__fr")=%%
%%[ ELSE ]%%
  %%=ContentBlockByName("welcome__en")=%%
%%[ ENDIF ]%%

Language coverage

42+ languages. Every region your list touches.

Europe

EnglishFrenchGermanSpanishItalianDutchPortuguesePolishSwedishDanishFinnishNorwegianCzechGreekRomanianHungarian

APAC

JapaneseKoreanSimplified ChineseTraditional ChineseThaiVietnameseIndonesianMalayHindiTagalog

MEA & LATAM

ArabicHebrewFarsiTurkishBrazilian PortugueseMexican SpanishArgentine SpanishSwahili

Security & compliance

Your data never leaves your tenant.

MCT runs inside your Marketing Cloud org. Subscriber data stays where it belongs, with you.

OAuth 2.0 client-credentialsLeast-privilege scopesSecrets in managed storeIn-tenant contentGDPR aligned

100%

In-tenant

PII shared

AES-256

At rest

24h

Rollout

42+

languages supported

middleware to maintain

<24h

install to first send

block inside Content Builder

Ready to speak every subscriber's language?

Book a demo and see MCT in action inside your Salesforce Marketing Cloud.

Book a demo