Live in a day. Out in an hour.
No custom code inside Marketing Cloud, and a documented exit path, because a buyer should never have to guess how they would remove you.
Prerequisites checklist.
Five steps, one admin.
Typical elapsed time is under 24 hours, most of which is waiting on internal approvals rather than work.
- 01
Install the package
Your admin installs the MCT package in Setup, Installed Packages. This registers the custom content block so it appears in Content Builder.
- 02
Create the API integration
Add a server-to-server component with OAuth 2.0 client-credentials and only the Saved Content read and write scopes. Copy the client ID, secret and REST base URI.
- 03
Deploy the backend
Deploy to Azure App Service, CloudPages or your PHP host. Put the SFMC credentials and the Google Cloud key in the secret store, never in the app config file.
- 04
Point the block at the backend
Set the backend endpoint in the block registration. The block loads in an iframe inside Content Builder and handshakes with the editor.
- 05
Configure defaults
Set target languages, block prefix, output folder names and do-not-translate terms so every marketer starts from the same setup.
Every setting, explained once.
Prove it works before you roll out.
Run this smoke test on a sandbox email. It takes about fifteen minutes.
Leaving is a five-step job.
No lock-in: your compiled content is native Marketing Cloud content and keeps working after MCT is removed.
- 01
Remove the block from templates
Swap the MCT block out of any active template or email. Existing compiled blocks keep rendering because they are ordinary content blocks.
- 02
Revoke the API integration
Delete the installed package's API integration in Marketing Cloud Setup. The backend loses access immediately, with no further action needed.
- 03
Delete the package
Uninstall the MCT package. The custom block disappears from Content Builder.
- 04
Decommission the backend
Delete the App Service, CloudPage or PHP deployment and remove the entries from your secret store.
- 05
Decide what to keep
Everything MCT produced is yours and stays: per-language content blocks, the switch email, and any edits your team made. Nothing breaks when MCT is gone.
The five things that actually go wrong.
The block loads blank in Content Builder+
The backend endpoint is unreachable or blocked by mixed content. Confirm the endpoint is HTTPS with a valid certificate and reachable from the browser.
401 when compiling+
The API integration is missing Saved Content write scope, or the secret in the vault is stale after a rotation.
Personalization got translated+
The token is in a syntax MCT did not recognize. Add it as a do-not-translate term and re-run, then send us the sample so we can extend the parser.
Only part of a long email translated+
Usually a translation API quota, not a chunking issue. Check the Google Cloud quota page for the connected project.
Blocks compile into the wrong folder+
Output folder name in the block config does not match an existing folder. Folder names are matched exactly, including case.
Still stuck? See support channels and response targets
We install it with you on the call.
Bring your admin. Most orgs are translating a real email by the end of the session.
