Read it before you buy, not after.
The full admin and end user documentation set for MCT, organised the way an evaluation actually runs: install, use, reference, govern.
Four sections, no scavenger hunt.
- What MCT is
A custom Content Block inside Content Builder that translates an email once and assembles every language version for you.
- Prerequisites
An SFMC instance with Content Builder, permission to create an installed package, and a user who can add a Content Block to a template.
- Install in under a day
Create the installed package, paste the block endpoint, authorise, run the smoke test.
- Translate a template
Drop the MCT block, pick source and target languages, press Translate, review the side by side result, save to your folder.
- Folder and naming rules
Output is written to a folder you choose. Growth and Enterprise can set a custom naming pattern per language code.
- Reviewing and editing
Every generated version is a normal Content Builder asset. Edit it like any other email, MCT never locks it.
- AMPscript and personalisation
AMPscript blocks, %%tags%% and handlebars placeholders are extracted before translation and put back byte for byte afterwards.
- Recursive assembly
Nested slots and blocks are walked depth first so a template made of templates still comes out intact.
- Limits and chunking
Long emails are split on block boundaries to stay inside translation request limits, then reassembled in order.
- Error messages
Every failure returns a code and a plain sentence. Common ones are listed in the troubleshooting section of the install guide.
- Permissions and scopes
MCT requests only the Saved Content scopes it needs. Nothing about Data Extensions or subscriber data.
- Data handling
What is sent to translation, what is stored, for how long, and which sub-processors are involved.
- Uninstall
Remove the block, delete the installed package, revoke credentials. Generated assets stay yours.
Your first translated email.
Assuming MCT is already installed and authorised in your instance.
- 01
Open the template
In Content Builder, open the email or template you want to translate and drop the MCT block where the body lives.
- 02
Pick languages
Choose the source language and one or more targets. Starter covers 10 languages, Growth and Enterprise cover the full set.
- 03
Translate and review
Press Translate. Compare source and output side by side. AMPscript and merge fields are shown untouched.
- 04
Save and send
Save each language into the folder you selected. Use them in a journey or a send exactly like hand built assets.
What the documentation covers.
Need the version tailored to your instance, or a PDF for a procurement pack? Ask support@genetrix.tech and we will send the current build with your configuration filled in.
Questions the docs do not answer?
Book a working session and we will walk your template through MCT live.
