Author: Chris Stauffer, Director, Platform Adoption Specialists at Anaplan.
As organizations continue to embrace Anaplan's powerful platform for connected planning and decision-making, it is increasingly important to continuously monitor and analyze end user adoption, security and access events, as well as granular model data changes. Anaplan Audit Log and Model History contain critical data in achieving compliance and audit objectives. However, unlocking the full potential of the Anaplan Audit Log and Anaplan Model History and utilizing them effectively for reporting and analysis presents a set of challenges that requires some transformation of the raw data.
At our July 28, 2026 ACE webinar, “Driving Security, Compliance, and Governance with the Anaplan Audit Log”, we announced a Python + Anaplan solution to address those challenges and offer it as a free starter kit to help our valued customers get up and running to extract, transform, and load this valuable and insightful data into a business-user friendly Anaplan Model and UX App.
First let’s do a quick review of Anaplan Audit Log and Anaplan Model History:
Anaplan Audit is a native platform tenant level log that provides an immutable time-stamped log of 230 different events. Tenant Auditors can retrieve Audit Data via API or exported from the Administration UI, however the raw Audit data contains Anaplan IDs and not business friendly labels. (User ID and not user email for example). Depending on your entitlements, up to 30 or 90 days of Audit event data can be retrieved at any point in time.
Anaplan Model History is a native platform modeling feature that provides an immutable time-stamped event record of approximately 82 different model change types that may occur in model’s lifespan. WSA’s can export Model history from the MX but the data volume can be extremely large depending on model age, date range selected for export, and number of changes recorded.
Reporting Solution Components
Our reporting solution has two main components:
1) A free downloadable Python 3.13 CLI script that extracts Anaplan Audit events and per-Anaplan Model change event history using Anaplan APIs, blends this data with other metadata (Users, Workspaces, Models, Actions, Processes, CloudWorks integrations), transforms the result in SQLite, and finally loads the report-ready tabular data into a 2) free Anaplan Model and reporting UX App to receive meta data and data updates extracted and transformed by the script. The Anaplan Model is initially very small and has a simple design. The UX app contains sample pages.
To acquire the Model and App, please submit an Anaplan support ticket and request a copy of the Anaplan Audit and Model History Reporting Model and App. Please see the below request template and be sure to cc your Anaplan Customer Success Business Partner or Anaplan Account Executive.
Customers are responsible for configuring, testing, and operating these solutions for their own environments. Please note that standard Anaplan Support does not cover the troubleshooting, maintenance, or modification of code or implementations derived from this starter kit. This is solution is provided "as-is" and may not apply directly to your specific use case.
Set Up & Operation
Detailed installation, operation, and technical reference documentation is located on our GitHub location here.
The Python script settings.json configuration file contains several configuration options, starting with three different authentication options. Customers have the option to enable both Audit Log and Model History Data, or only Audit Log Data, or only Model History. Customers can limit the amount of Audit and Model History data used by specifying source workspace-model combinations which will limit both Audit and Model History data.
At runtime the python script retrieves and transforms data from the specified workspace + model combinations from the customer tenant, then calls Anaplan import processes in the Anaplan Reporting model to import any new data (since the last script execution) into the Anaplan Reporting model. Audit data imports into the ‘Audit’ module and model history into the ‘Model History Detail’ module. SUM and COUNT functions summarize event counts by activity category into various basic reporting modules. A "Refresh Log" module timestamps each script execution and counts the number of records imported. These modules are displayed on the sample UX pages and customers can modify the model and app as they wish. Customers can schedule script updates at any interval desired.
The Anaplan model is ~ 2MB initially but will grow over time as the volume of data inside the model increases. The Anaplan model is designed to store both audit and model history data, but it is possible to make a copy of the model and leverage two standalone reporting models to segregate Audit data from Model History data, which can become very large.
Customers may wish to periodically archive older audit and model history models to manage workspace usage. Customers are not obligated to use the Anaplan Model and can use the SQLite data with any third-party reporting capability.
Model History Export Actions
In order for the script to retrieve model history data, customers need to build one export action inside of each specified model.
From the Model History interface in each Anaplan model, set the desired history window (for example, the last 24 hours, last 7 days, last 30 days, all history, or a custom date range), then save and run the export action. If you set the export action to retrieve all model history for a specific model, be advised that model history export is model locking action, and the model will block users from using the model until the export action is complete. We recommend only running an ‘all history’ action once at the start of your project, then build a second export action to retrieve smaller amounts of weekly or daily model history. The script will detect and only recognize export actions named "MODEL_HISTORY_EXPORT".
Audit data does not require an export action since the data resides at the tenant level and not within a model. Extracting audit data is not a model blocking activity.
Conclusion
Together these capabilities — automated audit log and model history extraction, a ready-to-use Anaplan reporting model — give organizations a powerful, flexible toolkit for tracking, analyzing, and archiving data changes within their Anaplan environment. By addressing the complexities associated with audit log and model history reporting, organizations can strengthen their security posture, improve compliance, and enhance overall operational efficiency.
UX Pages
Here are some images of the UX pages from the Anaplan reporting model. We would love to hear how you are using Audit and Model History data, please comment below.
Audit
Tenant Data
Model History
Video of script running
Support Ticket Request
You can use the below template to request a copy of the model from Anaplan Support. Please copy the Anaplan Audit Reporting Model & App listed below into the customer classic workspace listed below.
FROM
Tenant: ‘PES Demo Tenant’
baf06b46e75f4ceb8f06cd3a0b4fdc19
Model: ‘Audit Reporting Prod’
95A51EFDC8FD494FA77596AEA73BF77B
App: ‘Audit Reporting Prod’
660801fb-f77e-4e9b-8cca-10fc7da826ad
TO
CUSTOMER ENVIRONMENT
<< customer to please copy paste your desired target workspace name and workspace ID here>>