Every automation map in Ontraport keeps its own version history. It's a complete record of your map's earlier saved versions. When your results change, it lets you look back at how the map was built before and see what's different. Here's how it fits with saving and publishing, and how to use it to find and fix a change that didn't work.
As you edit in the Automation Builder, your changes save automatically every minute. But they don't go live until you publish. Click Save if you're not ready to launch. When you are, click Publish, then Save & Publish. And if someone else on your team is editing the same map, Ontraport warns you.
Version history keeps those earlier versions of your map, so you can see its elements and flow as they were. It answers a simple question: what did this automation look like before, and what's different now?
Here's an example. Say you rewrite a sales email in a lead funnel, and conversions drop afterward. Start in Performance Mode, which shows your results right on the map.
Set the date range to before your change, then to after it. Only contacts added to the map during the range are counted, so you can compare the two. Then use version history to see exactly what changed in between. Maybe it was the email itself. Maybe it was a one-day wait you added between steps.
Once you've found the problem, click Edit, make your changes using the earlier version as your guide, and publish again. Take care on a live map: if you delete an element that contacts are sitting on, they're removed from the map. The version that didn't work stays in your history, so you can look back at it later and avoid the same mistake.
So: Ontraport saves your work as you go, nothing goes live until you publish, and version history keeps your earlier versions, so you can see what changed when your results do. Next up: sharing automations with other users.