> 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/app-performance.md).

# App Performance

The App Performance report allows you to generate reports using accurate generated revenue data for analysis. This report eliminates the need to log into multiple mediated network dashboards to track revenue.

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

## What's in the Report?

The App Performance report provides all the necessary dimensions to analyze the performance of an app. It includes metrics such as Daily Engaged Users (DEU), Average Revenue per Engaged User (ARPDEU), and Fill Rate. This report includes the Impressions for Apps and Placements. The revenue and impression count for traditionally mediated networks comes from their respective reporting APIs.

{% 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 App Performance report opens with a table with the following default settings:

* Split: App Name (default limit: 50).
* Metrics: Revenue, Impressions, Fill Rate, ARPDEU and eCPM.
* Sorting order: Descending by Revenue.
* Pinboard dimensions: Device OS, Country, and Placement Type

## App Performance Dimensions

The following sections describe the dimensions available in the App Performance 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>Device OS</summary>

Identifies the device's operating system.

</details>

<details>

<summary>Availability of Advertising ID</summary>

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

</details>

### Experiment

<details>

<summary>Variant Name</summary>

The name of the variant in the experiment settings.\
\
A variant defines a group within a placement experiment or test, and a placement test compares different placement configurations on a subset of users to optimize ad performance. The system analyzes the results and selects the best-performing variant.

</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>

<details>

<summary>Placement ID</summary>

The unique identifier for a placement.

</details>

<details>

<summary>Placement Name</summary>

The name of the placment as configured in the placement settings.

</details>

<details>

<summary>Placement Type</summary>

Format and location of the placement:

* Banner: Rectangle ads appear either at the top or bottom of the screen. The user can view them but cannot dismiss them.
* Rewarded: Full-screen ad format that shows a short video ad to the user. Upon completion of the video, the user will earn a reward.
* Interstitial: Static or video full-screen ads. The user can view and then immediately dismiss them. This is a non-rewarded format for the user

</details>

<details>

<summary>Product Line</summary>

DT product: DT FairBid or DT Exchange.

</details>

### Location

<details>

<summary>Country</summary>

Identifies the country where the ad request originates.

</details>

## App Performance Metrics

The following sections describe the metrics available in the App Performance report.

### Delivery

<details>

<summary>Ad Request</summary>

The total number of times an app sends a request an ad from the exchange servers.

</details>

<details>

<summary>Fill rate</summary>

The rate at which ad requests receive an ad ready to appear.\
Formula: Fills ÷ Ad Requests

</details>

<details>

<summary>Fills</summary>

The number of times an ad is available to fill a request.

</details>

<details>

<summary>Show Rate</summary>

The rate at which available ads appear and become impressions.\
Formula: Impressions ÷ Fills

</details>

### Engagement

<details>

<summary>Ad Completions</summary>

The number of times users complete viewing a video ad.

</details>

<details>

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

The rate at which each engaged user generates revenue within a specific period.\
Formula: Total Revenue ÷ Engaged Users

</details>

<details>

<summary>Clicks</summary>

The total number of times a user clicks on an ad.

</details>

<details>

<summary>Completion Rate</summary>

The rate at which a user completes viewing an ad.\
Formula: Completions ÷ Impressions

</details>

<details>

<summary>CTR</summary>

Click Through Rate. The rate at which users click on an ad they view.\
Formula: Clicks ÷ Impressions

</details>

<details>

<summary>Engaged Users</summary>

The number of unique users who receive at least one impression in the selected timeframe.

</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>

### Revenue

<details>

<summary>eCPM</summary>

Effective Cost Per Mille. Calculates ad revenue generated per 1000 ad impressions.

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

</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>


---

# 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/app-performance.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.