To increase the transparency and visibility of activities performed in the system, Customer Journey Analytics (CJA) allows you to audit user activity for various services and capabilities in the form of “audit logs”. These logs form an audit trail that can help with troubleshooting issues, and help your business effectively comply with corporate data stewardship policies and regulatory requirements, such as the Health Insurance Portability and Accountability Act (HIPAA).
In a basic sense, an audit log tells who performed what action, and when. Each action recorded in a log contains metadata that indicates the action type, date and time, the email ID of the user who performed the action, and additional attributes relevant to the action type.
This topic covers audit logs in CJA, including how to view and manage them in the UI.
When the feature is enabled for your organization, audit logs are automatically collected as activity occurs. You do not need to manually enable log collection.
In order to view and export audit logs, you must have been granted the Audit Logs Access access control permission in Adobe Console. To learn how to manage individual permissions for CJA features, please refer to the access control documentation.
In CJA, navigate to Tools > Audit Logs.
The audit log for today and yesterday are shown by default.
You can select which columns are visible by going to the column selector at the top right.
Double click the info (i) button next to a description.
The following items are shown:
Item | Description |
---|---|
Action Name | Here is the list of possible actions:
|
Description | A summary of the action, component type (with ID) and other values. |
User Name | The user taking the action. |
Component Type | Possible component types include:
|
IMS Org ID | A unique ID that is given to your instance when you first log in to Adobe Experience Cloud. It should be in the format: xxx@AdobeOrg. |
User ID | A unique ID identifying the user who took this action. |
Date Created | When this action was taken. |
The email of the user taking the action. | |
Component ID | A unique ID that identifies the component that is being actioned upon. |
Log ID | A unique ID identifying this log entry. |
User Type | Possible types include: IMS, OKTA |
Select the funnel icon () to display a list of filter controls to help narrow results. Only the last 1,000 records are displayed, irrespective of the various filters selected.
The following filters are available for audit events in the UI:
Filter | Description |
---|---|
Date Range | Filter on a different date range by selecting a different date or selecting a date range by dragging the cursor across multiple dates. By default, today’s and yesterday’s date are selected. |
Action | Filter on one or more of the following actions:
|
User ID | Filter on a specific user by their user ID. The user ID can be found by selecting the info (i) button next to a user name. |
Filter on a specific user’s email address. The email can be found by selecting the info (i) button next to a user name. | |
Component ID | Filter on a specific Component ID. The user ID can be found by selecting the info (i) button for a desired component. |
Component Type | Filter on one or more component type/s:
|
The following table outlines which actions on which component types are recorded by audit logs:
Component Type | Actions |
---|---|
Annotation |
|
Audience |
|
Calculated Metric |
|
Connection |
|
Data View |
|
Date Range |
|
Filter |
|
IMS Org |
|
Project |
|
Report |
|
Scheduled Project |
|
User |
|
User Group |
|
You can download audit logs in CSV or JSON formats. Any filters applied or columns selected are reflected in the downloaded files.
All actions that you can perform in the UI can also be done using API calls. See the CJA API reference document for more information.