CJA Audit logs

[#1]

We would like to understand what combination of events equal to what user actions via CJA Audit logs.

The CJA Audit logs help doc https://experienceleague.adobe.com/en/docs/analytics-platform/using/cja-privacy/audit-log gives insights on very general things but we want to be able to get more specific information.

For example: Project Created: Name = #### will that only show up once per project creation? Project Viewed will show up multiple times for a single view of a project(tested) or on a future date after the actual view. This makes it a bit challenging to extract precise usage insights.

What are API_REQUEST? Why is there no User Name against some Action Name in the Audit logs? Description would show: Project Viewed: Project Objects - What are Project Objects?

[#2]

I haven't worked too deeply in CJA's audit logs but I do understand there's a Product Usage Analytics feature that is coming soon.  This will allow an analysis of what projects and components CJA users are working with.  It seems this upcoming feature might be better for your use case.

[#3]

Hi @Sagar_Sharma - I happened to notice Product Analytics today in one on my CJA instances.  Check under your Tools menu to see if you have access yet.

[#4]

There isn't a lot of information about what the different audit log field values mean in the CJA documentation. My recommendation is to focus on the Description field, as this tells you what the Action Name is related to. In the case of API_REQUEST, remember that Workspace is really just a friendly UI that handles API calls. So you'll see this Action Name for lots of different Descriptions, including "Running report", "Project Viewed", etc.

As for the new Product Usage feature, we've found that it isn't very useful. It lacks the granularity we need to understand how people are using CJA, and doesn't include a lot of the data points available in the audit logs (e.g. Component IDs for Workspace projects). This can lead to situations in which CJA rolls up Workspace projects that have the same name, creating a scenario in which you don't know which one was used more. A better version of the feature would have imported the audit logs into AEP, created the Connection in CJA, and then had some pre-built derived fields and configured dimensions.