MCE Version Controller

Automatically saves version history for your Marketing Cloud assets, starting with CloudPages, with more asset types coming soon.

MCE Version Controller is a productivity tool designed for Marketing Cloud Engagement Administrators and Developers. Its goal is to fulfill the need for a version history of the various elements you work with within MCE. The extension detects when an element is saved, validated, or published within Queries, Query Studio, CloudPages, Code Snippets, and Content Blocks. Whenever this occurs, it automatically saves a version of the element along with the date. The first time an element is saved, a folder is created using the name of the Business Unit. All items are grouped under that Business Unit, although you can also create and reorganize folders as needed. When working with an element that has a version history, a chip appears on the right side of the screen. You can expand it to review the available versions and restore any of them directly from there. When you restore a version, the current state is automatically saved before being overwritten by the selected one. Furthermore, it offers additional features such as a line-by-line version comparator (with word-level highlighting), the ability to give any version a name, a label (Draft / Test / Prod) and notes — named Query Studio queries can also be restored quickly from the tool — a per-folder summary of saved elements and storage used, optional auto-deletion of old versions by age, a full backup you can export and import as a JSON file, and the option to download the code or all versions as a ZIP file. Privacy and Security: Everything is stored locally in your own browser using Chrome's local storage. No data is ever sent to any external service or to the developer, no logins or accounts are required, and the extension makes no outbound network calls with your data. It only reads the content already shown in the MCE editors — it never accesses your Salesforce credentials or session. Because the version history is kept locally in your browser profile, treat it with the same care as your source code: use the extension only on a device and browser profile you control, following your organization's security policies.