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

# Auctions

The Auctions report allows you to generate reports that track performance metrics, such as revenue, number of impressions, and number of clicks, for daily transactions on the DT console. This report updates hourly, with a latency of three hours.

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

## What's in the Report?

The Auctions report provides all the necessary dimensions and metrics to analyze auction outcomes, such as Gross Revenue, Ad Requests, and Impressions. The report allows you to track total bids, bids won, and completion rates, which provides insights into bid values, success rates, and competitor activity.

### Default view

The Auctions report opens with the Totals view that has the following default settings:

* Metrics: Gross Revenue, Ad Requests, and Impressions.

To view the Auctions report in a table, split or filter by Publisher ID or Publisher Name.

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

## Auctions Report Dimensions

The following sections describe the dimensions available in the Auctions report.

### General

<details>

<summary>Date/Time</summary>

Defines the date range the report covers.

The default filter is set to today’s date.

</details>

### Auction

<details>

<summary>Deal ID</summary>

A unique identifier string that signals the presence of a PMP in a bid report.

</details>

### Delivery

<details>

<summary>SDK/Tag Version</summary>

The version of the source; SDK or JavaScript tag.

</details>

<details>

<summary>Mediation Platform Name</summary>

The mediation platform that mediates the DT Exchange SDK.

</details>

### Device

<details>

<summary>Advertiser 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>

<details>

<summary>DNT</summary>

Do Not Track. Indicates whether the user opts out of tracking.

</details>

### Inventory

<details>

<summary>Ad Size</summary>

The creative ad size as specified by the advertiser.

</details>

<details>

<summary>Ad Unit Type</summary>

The type of ad container for an ad unit. The available ad types depend on the placement type when you create it:

* Display
* Video
* Playable

</details>

<details>

<summary>App Bundle</summary>

A unique identifier of an app in Android or iOS.

</details>

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

Indicates the app's compliance with COPPA regulations.

</details>

<details>

<summary>Interstitial Skipability</summary>

Indicates whether the publisher requests skippable ads, non-skippable ads, or both.

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

<details>

<summary>Publisher ID</summary>

The unique identifier that represents the publisher in the DT Console.

</details>

<details>

<summary>Publisher Name</summary>

The name of the publisher as specified in the DT console.

</details>

<details>

<summary>Variant ID<br>(Ad Unit ID)</summary>

A unique identifier that represents the variant.

</details>

<details>

<summary>Variant Name<br>(Ad Unit Name)</summary>

The name of the variant in the experiment settings.

</details>

### Location

<details>

<summary>Country</summary>

Identifies the country where the ad request originates.

</details>

### Winning Demand

<details>

<summary>Advertiser Domain</summary>

A destination domain that the advertiser defines for an ad.

</details>

<details>

<summary>Advertiser Bundle</summary>

A unique identifier that represents the advertiser's app, for example, `com.123.appname`, which represents the advertiser in the context of their specific application.

</details>

<details>

<summary>Campaign ID</summary>

A unique identifier that represents the campaign in the bid response.

</details>

<details>

<summary>Creative ID</summary>

A unique identifier that represents the creative in the bid response:

* Display
* Video
* Playable

</details>

<details>

<summary>Creative Type</summary>

Indicates the ad format in the bid response.

</details>

<details>

<summary>Demand Source ID</summary>

A unique identifier that represents the demand source that wins the auction.

</details>

<details>

<summary>Demand Source Type</summary>

The demand source integration:

* Programmatic
* Bidding Mediated Networks
* Waterfall Mediated Networks
* Custom API

</details>

<details>

<summary>Demand Source Name</summary>

Identifies the demand partner that wins the auction.

</details>

<details>

<summary>Seat ID</summary>

A unique identifier that represents the winning buyer on the DSP's side.

</details>

## Auctions Report Metrics

The following sections describe the metrics available in the Auctions report.

### Auction

<details>

<summary>Ad Requests</summary>

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

Ad requests are not the same as bid requests.

</details>

<details>

<summary>Avg Mediation Min Bid To Win</summary>

The average minimum required to win the auction for DT bidding.\
Formula: Mediation Min Bids to Win ÷ Bid Requests

</details>

<details>

<summary>Avg. Clear Price</summary>

The average price a demand partner pays for 1000 impressions.\
Formula: Clear Price ÷ Cleared

</details>

<details>

<summary>Clear Rate</summary>

Calculates the rate of auctions that result in a successful transaction.\
Formula: Bids Won ÷ Ad Requests

</details>

<details>

<summary>Bids Won</summary>

Number of auctions that the demand source wins.

</details>

<details>

<summary>Delivery Rate</summary>

Calculates the rate of impressions divided by the number of ad requests.\
Formula: Impressions ÷ Ad Requests

This is the full-funnel success rate indicator.

</details>

<details>

<summary>eCPM</summary>

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

</details>

### Bids

<details>

<summary>Avg. Win eCPM</summary>

Average winning bid price in terms of CPM. This reflects the average price of all bids that won the auction.\
Formula: Win Bid Prices ÷ Cleared\
In a second-price auction, the Avg. Win eCPM is usually higher than the actual amount the demand partner pays for the impression.

</details>

### DT Exchange Bidder

<details>

<summary>Billing Event</summary>

Total number of billing events counted from billing URLs (burls) sent by the mediation partner.

</details>

<details>

<summary>Lose Event</summary>

Total number of loss events, counted from loss URLs (lurls) sent by the mediation partner.

</details>

<details>

<summary>Win Event</summary>

Total number of win events counted from notification URLs (nurls) sent by the mediation partner.

</details>

### Delivery

<details>

<summary>Survival Rate</summary>

The rate of impressions served divided by total winning bids\
Formula: Impressions ÷ Clears

</details>

### Engagement

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

The average number of ads served per unique user in a selected timeframe.\
Formula: Impressions ÷ Unique Users

</details>

<details>

<summary>Impressions</summary>

The number of times an ad appears to a user.

</details>

<details>

<summary>Unique Users</summary>

The number of all unique users who trigger at least one ad request during the selected timeframe.

Formula: Unique Users per device ID\
The system de-duplicates users in real-time based on the selected dimensions. This metric calculates:

* DAU (Daily Active Users)
* ARPDAU (Average Revenue per Daily Active User)
* Ad Frequency (Impressions ÷ Unique Users)

To view the DAU, select the Unique Users metric and do one of the following.

* Filter the Date to one day.
* Split by Date/Time and view with daily granularity (1D).

</details>

### Revenue

<details>

<summary>ARPU</summary>

Average Revenue Per User. The average revenue per unique user.\
Formula: Total Revenue ÷ Unique Users

To view the ARPU, select the ARPU metric and then do one of the following.

* Filter the Date to one day.
* Split by Date/Time and view with daily granularity (1D).

</details>

<details>

<summary>Fee</summary>

DT applies a 5% fee to all Bidding Mediated Networks, deducts it from total spending, and pays it directly to DT.\
This fee does not affect the Publisher payout.

</details>

<details>

<summary>Publisher Revenue</summary>

Calculates the total revenue ads generate.

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