User activity report

Overview

The Reports feature provides Instance admins and Governance users with two types of user activity reports. 

• Daily reports: Enables users to download a report for each of the past 7 days individually. Unity automatically generates these reports daily and retains them for 365 days.

• Bulk downloads: Allows users to request a report that spans multi-day period.

These reports give visibility into operations performed within their Unity tenants. They log Create, Read, Update, and Delete operations on Unity resources, such as segments and data objects.

Downloading a Daily Report

You can download reports from the past 7 days in the “Daily reports” section of the “Reports” tab by clicking the download icon (). If no operations were logged on a given day, the download icon will be disabled.

Note: All dates and timestamps are in UTC.

Downloading a Bulk Report

Reports spanning multiple days are available in the “Bulk downloads” section of the “Reports” tab. To generate a report, specify your desired time range and click “Submit”.

Once you have submitted your request, a status line will appear. While the request is being processed, the status will show as “In progress”.

As soon as the request has been processed, the status will update to “Success”, and the file can be accessed by clicking the download icon ().

Report contents

Each report contains one row per user operation and includes following details:

• Date Timestamp: The UTC timestamp of the operation performed.

• User Id: The identifier for the user (used to differentiate users with the same name).

• User Name: The first and last names for the user.

• Area: The section of the application (e.g. Segments, Data Model)

• Location: The specific functionality within the area.

• Resource Id: The unique identifier for the affected resource.

• Action: The type of operation performed (Create, Read, Update, and Delete).

• Status: The result of the action (Success, Server error and Client error).

Known limitations

This report tracks operations triggered by user actions that result in an API call. Many of these APIs can be called by an external application, such as Postman. However, the report does not identify the origin of the API call. For example, an event like “Update campaign job” could occur either in the Unity UI or through an external application calling the same API as the Campaign edit screen.

Currently, the report is limited to CRUD operations on resources like segments and data objects. It does not track create/update operations on data records from the Data viewer (which uses the NRT and Streams APIs), nor read operations from the Profile explorer (which uses the 360 API).

Create operations for resources generally do not include the ID of the resource being created except for Segments. And create operations for jobs do not specify the type of job (e.g., ingest, export).

Both the Segmentation canvas and the Data Viewer allow users to request a sample of data. The report does not differentiate between these locations, so the area is listed as “Segments/Data Viewer”. These operations are labeled as “Create” rather than “View” as the sample must first be “created” before it can be displayed.

The initial version of the report includes several operations that are either redundant with other operations, or do not reflect direct user operations. These are listed below. They can be ignored and will be removed in future versions of the report.

 

Area	Location	Resource Id
Data Model	Object	Diff
Intelligent Attributes	Intelligent Attribute	Diff
Jobs	Ingest Job	Diff
Segments	Segment / Template	Counts
Segments	Segment / Template	Guid
Segments	Segment / Template	Validate