Overview
Every Application in CX Platform keeps a running record of changes made to it. Whether someone's tweaked a template, updated a setting, or copied the Application to spin up a new one, it's all logged in the History tab.
The audit trail is your go-to when you need to track down when something changed, confirm a recent edit, or check who made a particular update. It's especially handy for compliance reviews, troubleshooting, or just sense-checking what's happened in the lead-up to a send.
Each entry shows you the basics at a glance, and a Detail button lets you drill into the specifics of what actually changed.
Find the History tab
- In the secondary navigation menu, click Applications to view a list of all available Applications.
- In the Application list view, double click the auto-highlighted Application or click the Settings icon on the right hand side of the list view to open it.
- Click the History tab in the Application settings.
You'll land on a paginated list of every change made to this Application, with the most recent activity at the top.
What you'll see
The History view is a sortable table covering everything that's happened inside the Application. Here's what each column tells you:
You can sort by any column using the arrows in the header, and step through older entries using the pagination controls at the bottom of the list.
View the detail behind a change
The summary line tells you what happened, but the Detail button is where you get the full story.
- Find the entry you want to investigate in the History list.
- Click Detail on the right hand side of the row.
- Review the change in the View detail panel that opens.
What you see in the detail panel depends on the type of change being logged:
- Database changes — for things like Application copies, setting updates, or group changes, you'll see the underlying data in JSON format. For example, an Application - Copied From entry will show you the new Application Id and name that were created.
- HTML changes — for template edits, you'll see the HTML content that was saved, so you can confirm exactly what was changed in the template body.
It's a quick way to verify what someone updated without having to dig through the Application itself or compare versions side by side.
Tip
If you're investigating a specific issue, sort by Date to find the change closest to when the problem started, then use Detail on a few nearby entries to see what was in flight at the time.
What's next
The History tab is read-only — it's there for visibility, not editing. If you spot a change that needs reverting, head to the relevant section of the Application (Templates, Fields, Channel selection, and so on) to make the update. Your fix will then show up as the next entry in History, keeping the trail complete.