Questions, answered.
If your question isn't here, we're a short email away.
Install & setup
How is MCT distributed?+
MCT ships as an installed package for Salesforce Marketing Cloud plus a backend service you host (Azure App Service by default, or SFMC CloudPages / PHP).
How long does install take?+
Under 24 hours in most orgs. The admin installs the package, creates an API integration with OAuth 2.0 client-credentials, and the backend is pointed at the SFMC REST endpoint.
Do we need any dev work?+
No custom code inside SFMC. The MCT block is drag-and-drop in Content Builder. The backend is a standard deployment on infra you already run.
Technical
How does MCT handle my AMPscript?+
The backend extracts AMPscript blocks, %%=v(@field)=%% substitutions and personalization tokens before sending copy to Google Cloud Translation v2, then re-injects them after translation. Nothing dynamic is ever translated.
Does it support nested templates and slots?+
Yes. The recursive assembler walks templates → slots → blocks and fully composes the email before translation. One click, one compiled result.
How does it stay within Google Translate's request limits?+
Copy is chunked into ~18KB batches per request, keeping large emails well within v2 limits and avoiding partial translations.
Can I keep brand and product names untranslated?+
Yes. Add do-not-translate terms in the block config. MCT preserves them exactly across every language and every nested block.
Where does the compile output live?+
Per-language content blocks (prefix__es, prefix__fr, ...) in Content Builder, plus a single email that switches on the subscriber locale using an AMPscript IF/ELSE with ContentBlockById.
Security & data
How does MCT authenticate to Marketing Cloud?+
OAuth 2.0 client-credentials with least-privilege scopes (Saved Content read + write). Client ID and secret live in a managed secret store (Azure Key Vault or equivalent), never in the block config or code.
Do you store subscriber data?+
No. MCT only processes your marketing copy and writes compile output back into your Content Builder. Subscriber records never leave your Marketing Cloud org.
Where does the compiled email live?+
Inside your own Marketing Cloud instance as content blocks and a switch email. At send time Marketing Cloud renders it directly, the MCT backend is not in the path.
Hosting & deployment
Where can the backend run?+
Azure App Service (default), Marketing Cloud CloudPages using SSJS, or any PHP host. Same block, same compile behavior.
Can one backend serve multiple SFMC orgs?+
Yes. Path-based routing lets a single deployment host multiple org configurations with per-org credentials in the secret store.
Translation quality
What translation engine is used?+
Google Cloud Translation v2 by default. Every language is editable in the in-browser preview before compile, so your localization team can polish anything.
Can we use our own translators?+
Yes. Edit any language directly in the preview, or overwrite the generated content block after compile.
Pricing & contracts
How is it billed?+
Flat monthly per-org license. Each tier includes a fixed number of unique email translations per month. See pricing for details.
Is there a trial?+
Yes, 2-week sandbox pilot with your own content, no credit card.
Real humans reply within one business day. Ask us anything about install, security, or how MCT fits alongside your existing SFMC setup.
See it running before you ask more questions.
A 30-minute demo answers most of what teams ask on this page.
