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

# Buyer's Report

The Buyer's Report allows you to generate reports that analyze the traffic you receive and your bidding landscape, such as Bid Status, Demand sources, and SKOverlay, for daily bids on DT Exchange. This report updates hourly.

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

## What's in the Report?

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

### Default View

The Buyer's report with the Totals view has the following default settings:

* Metrics: Gross Revenue, Bid Requests, Bid Responses, Bids Won, and Impressions.

To view the Buyer's report in a table, split or filter by Publisher ID or Placement 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 %}

## Buyer's Report Dimensions

The following sections describe the dimensions available in the Buyer's 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>Bid Status</summary>

The status of each full bid transaction:

* Win: Bid wins the auction.
* Adapter Failure: FairBid only. DT's SDK fails to activate the adapter of the mediation network.
* Below the Floor Price: Bid response does not meet the publisher's floor price.
* Blocked Advertiser App: Bid response rejected due to a blocked app.
* Blocked Advertiser Domain: Bid response rejected due to a blocked advertiser domain.
* Blocked Category: Bid response rejected due to a blocked category.
* Blocked on Creative: Bid response is manually blocklisted for creative content.
* Blocked On Creative Attribute: Bid response rejected due to a mismatch between the required and supported ad features.
* Capped: Bid request dropped due to frequency cap.
* Child Audience Eligibility Filter/Child Content Support Bundle Domain Filter: Only age-appropriate content can be shown when a user is flagged as a child with Google Play Families Ads API. The bid response was rejected because the campaign was determined to be not age appropriate.
* Demand QPS Throttling: Bid request blocked exceeding the manual queries-per-second (QPS) cap.
* Empty Advertiser Domain: Bid response rejected as the advertiser domain is empty.
* Failed Creative ID Blocked: Bid is automatically blocked due to a consistently low survival rate.
* Filtered Out for Optimization: Automatically blocked for optimization.
* HTTP Error: Request failed due to a server error.
* Incompatible SKAD Versions: Bid response is blocked when the `SKAdNetwork version` returned on `BidResponse.seatbid.bid.ext.skadn.version` is higher than the `SKAdNetwork` supported by the app and on the bid request.
* Invalid Advertiser Domain: An invalid bid response where the demand source bids with an invalid advertiser domain.
  * Valid values:
    * Advertiser domains and subdomains, for example, `us.company.com`.
  * Invalid values:
    * Domains without a dot, for example, `financecom`.
    * Domains that start with a dot, such as `.abc.com.`
    * Domains with `www`, `http(s)`, `/`, and any parameters.
    * Domains from `play.google.com` and `itunes.apple.com`
    * Bundles in numeric iOS or standard Android format are invalid.
* Invalid or Malformed Bundle: An invalid bid response where the demand source bid with an invalid bundle format.
* Invalid Response: Bid response fails due to an invalid format or missing parameters.
* Invalid SKAD Parameters: An invalid bid response where the demand source returned one or more invalid parameters on the `BidResponse.seatbid.bid.ext.skadn`.\
  More information is available in [IAB specifications](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/6f675a9a85bee693bddf6f46aacd0043344bed0f/extensions/community_extensions/skadnetwork.md).
* Lost on Price: Bid loses because the price is lower than the bid in the auction.
* Missing Creative Data: The non-video bid response for a rewarded request rejected because the required fields `bid.ext.crtype:`, `Playable` and `seatbid.bid.attr: 13` do not pass.
* No Bid: `HTTP 204`: No Content response.
* Timeout: Response exceeds the timeout window.
* Blocked Due To Publisher Playable Blocking: Bid response rejected as the publisher has blocked playable ads.

</details>

### 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 Name</summary>

Identifies the demand source across systems, including mediated networks or DSPs.

</details>

<details>

<summary>Demand Source ID</summary>

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

</details>

<details>

<summary>Seat ID</summary>

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

</details>

<details>

<summary>Seat Name</summary>

The seat name for the winning buyer on the DSP's side.

</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>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>Ad Unit ID</summary>

Ad identifier within DT's system.

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

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

</details>

<details>

<summary>SKOverlay</summary>

An iOS class that displays a banner or overlay at the bottom of the screen, which recommends or promotes apps. It allows users to download apps directly, without redirecting to the App Store.\
Valid values:

* NotSupported: SKOverlay is unavailable when the app opts out of SKOverlay support.
* DSPNotSupported: The winning bid does not include SKOverlay, even though the available inventory supports it.
* Supported: The winning bid includes SKOverlay, and the impression displays the overlay.

</details>

### Location

<details>

<summary>Country</summary>

Identifies the country where the ad request originates.

</details>

## Buyer's Report Metrics

The following sections describe the metrics available in the Buyer's report.

### Auction

<details>

<summary>Avg. Bid Price</summary>

The average price the demand partner bids on for 1000 impressions divided by the number of bid requests.\
Formula: Bid Prices ÷ 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>Avg. Win Bid Price</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>

<details>

<summary>Bid Response Rate</summary>

The rate at which bid requests receive a valid bid response marked as Won or Lost on Price from a demand source in DT FairBid. Other mediation providers may refer to this as Network Fill Rate or Availability Rate.\
Formula: Bid Responses ÷ Bid Requests

</details>

<details>

<summary>Bid Responses</summary>

Number of valid bid responses, Won or Lost on Price, from the demand source.

</details>

<details>

<summary>Bids Won</summary>

Number of auctions that the demand source wins.

</details>

<details>

<summary>Win Rate</summary>

The rate at which a demand source wins the auction out of the total bid responses it provides.\
Formula: Bids Won ÷ Bid Responses

</details>

### Bids

<details>

<summary>Bid Requests</summary>

Number of outgoing requests that DT FairBid sends to demand sources after receiving an ad request from the app.

</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>Ad Completions</summary>

The number of times users completed watching a rewarded video.

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

The number of times an ad appears to a user.

</details>

### Revenue

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


---

# 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/buyers-report.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.