> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-console/reports/user-activity.md).

# User Activity

The User Activity report allows you to track the number of Daily Active Users (DAUs) and analyze user engagement with ads.

<div align="left" data-with-frame="true"><img src="/files/MjlE09B4FhjTZU58zFe2" alt=""></div>

## What's in the Report?

The User Activity report provides all the necessary dimensions to analyze user activity, including engagement, ad interactions, and active user behavior. To explore user activity, filter or split the data by App Name or App ID.

{% hint style="success" %}
For more details on the DT Dynamic Reporting functionality, see [Using the Reports](/dt-console/reports/using-the-reports.md).
{% endhint %}

### Default View

The User Activity report opens with a table that has the following default settings:

* Split: App Name and Date/Time (default limit: 50).
* Metrics: Active Users, Ave. Rate per Active User, and Publisher Revenue.
* Sorting order: Descending by Revenue.
* Pinboard dimensions: App ID and Device OS.

## User Activity Dimensions

The following sections describe the dimensions available in the User Activity report.

### General

<details>

<summary>Date/Time</summary>

Defines the date range the report covers.

The default filter is set to today’s date.

</details>

### Device

<details>

<summary>Advertising ID Availability</summary>

Determines the availability of an Advertising ID (IDFA for iOS or AAID for Android) in the ad request.

</details>

<details>

<summary>Device OS</summary>

Identifies the device's operating system.

</details>

### Inventory

<details>

<summary>App ID</summary>

The unique DT identifier for the app.

</details>

<details>

<summary>App Name</summary>

The name of the app as configured in the app settings.

</details>

<details>

<summary>App Version</summary>

The unique identifier for the specific app release.

</details>

<details>

<summary>COPPA</summary>

Indicates the app's compliance with COPPA regulations.

</details>

### Location

<details>

<summary>Country</summary>

Identifies the country where the ad request originates.

</details>

## User Activity Metrics

The following sections describe the metrics available in the User Activity report.

### Engagement

<details>

<summary>Active Users</summary>

Number of unique users who use the app at least once in the selected timeframe.

</details>

<details>

<summary>Banner Engagement Rate</summary>

The rate at which users watch at least one Banner ad in the selected timeframe.\
Formula: Unique users who watch a Banner ad ÷ Active Users.

</details>

<details>

<summary>Banner Frequency</summary>

Number of Banner ad impressions per user.

</details>

<details>

<summary>Engagement Rate</summary>

The rate at which Active Users watch at least one ad in the app.\
Formula: Engaged Users ÷ Active Users.

</details>

<details>

<summary>Frequency</summary>

The average number of impressions per user.

</details>

<details>

<summary>Impressions</summary>

The number of times an ad appears to a user.

The mediated network's reporting API retrieves impressions for ads from a waterfall-mediated network, and the value may change over time.

</details>

<details>

<summary>Interstitial Engagement Rate</summary>

The rate at which Active Users watch at least one Interstitial ad in the selected timeframe.\
Formula: Unique users who watch an Interstitial ad ÷ Active Users

</details>

<details>

<summary>Interstitial Frequency</summary>

Number of Interstitial ad impressions per user.

</details>

<details>

<summary>Rewarded Engagement Rate</summary>

The rate at which Active Users watch at least one Rewarded ad in the selected timeframe.\
Formula: Unique users who watch a Rewarded ad ÷ Active Users

</details>

<details>

<summary>Rewarded Frequency</summary>

Number of Rewarded impressions per user.

</details>

### Revenue

<details>

<summary>Avg. Rev. per Active User</summary>

The rate at which each Active User generates revenue within a specific period.\
Formula: Total Revenue ÷ Active Users

</details>

<details>

<summary>Banner Avg. Rev. per Active User</summary>

The rate at which each Active User generates revenue by watching a Banner ad within a specific period.\
Formula: Banner Publisher Revenue ÷ Active Users

</details>

<details>

<summary>Interstitial Avg. Rev. per Active User</summary>

The rate at which each Active User generates revenue by watching an Interstitial ad within a specific period.\
Formula: Interstitial Publisher Revenue ÷ Active Users

</details>

<details>

<summary>Publisher Revenue</summary>

Calculates the total revenue ads generate.

The mediated network's reporting API retrieves revenue for ads from a waterfall-mediated network, and the value may change over time.

</details>

<details>

<summary>Rewarded Avg. Rev. per Active User</summary>

The rate at which each Active User generates revenue by watching a Rewarded ad within a specific period.\
Formula: Rewarded Publisher Revenue ÷ Active Users

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalturbine.com/dt-console/reports/user-activity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.