Audit logs

Learn about how the audit logs feature can help you meet your compliance requirements and troubleshoot your Adobe Experience Platform implementation. For more information, please visit the audit logs documentation or the API reference.

Audit logs provide transparency and visibility into all activities on Adobe Experience Platform based applications, helping you to comply with corporate data stewardship policies and regulatory requirements. This accountability and transparency will also help you to troubleshoot issues on platform by giving you easy access to who did what and when. Access to the logs is governed by Experience Platform access control and requires administrators to add the view user activity log permission to relevant users through the admin console. Once access is provided, you can go into the platform interface, and then the left rail, click on the audits link to view the logs. Here, you can see the list of logged actions ordered by most recent activity. For each logged action, the system captures and exposes key metadata, including the name of the asset acted upon, type of action, and the user ID of who performed the action. Additional details such as asset identifiers and IP addresses are available in this sidebar. You can filter the logs and export the logs as CSV or JSON for additional discovery and analysis. For example, your IT department could upload the data into a log aggregator for analysis across your tech stack. All these actions can also be executed through the API, and that includes controls to query, filter and export logs based on key facets. You can learn more about the API usage in our Experience League and Developer Portal documentation. Here’s a list of actions that are captured in the logs today and includes key configuration activity in schemas, data sets, sandbox management and activation. We plan to extend this list and include more critical event types and metadata over time. In summary, audit logs help you to comply with corporate data stewardship policies and regulatory requirements, and to troubleshoot. Thank you. -