The promotion path
Prerequisites
Promote the change
1
Work in the Test environment
Switch to Test with the toggle in the settings menu. Templates, brands, and topics you create here are isolated from Production. Edit your template, then send with your Test key. Those sends appear only in the Test dashboard.
2
Preview the draft with a draft key
A draft key renders the latest unpublished draft, not the published version. Use one to review a change against a real payload before publishing. Generate it in , send with it, then check the rendered output in .
3
Get approval (optional)
If your team reviews changes before they ship, enable the . Publishing then opens a submission instead of going live, and the template stays read-only until that submission is resolved.
4
Move the template to Production
Read the template’s content from Test and write it to Production with the Templates API. returns the
{ version, elements } JSON, and writes it, using each environment’s own key.Remove every checksum field and any locales key that starts with an underscore before the PUT, and keep each element’s locales so the Production template gets the same translations. covers the rest, and is the same flow as .Create a template’s dependencies in Production yourself. Brands, tags, and subscription topics are per environment, so set them up there first. A send that references one that is missing fails there while it worked in Test.Verify
1
Smoke test with your Production key
Send to an internal recipient in Production.
2
Confirm the right version rendered
Open the message in , expand the timeline, and confirm the migrated version is the one that rendered.
3
Confirm the provider accepted it
The same timeline shows the provider’s response. A
SENT status that doesn’t progress to DELIVERED points at the provider, not the migration.