This report is intended for use by Publishers.
The Demand Performance report provides you with the ability to create reports based on actual and accurate revenue data pulled directly from the dashboards of mediated networks and programmatic data from DSPs in DT Exchange. The report updates once a day at 10.00 am GMT.
This report saves publishers the burden of logging in to each individual mediated networks' dashboard to discover how much revenue was generated.
What's in the Report?
In Demand Performance, you can find all the dimensions and metrics required to analyze how the publisher’s demand partners (mediated or programmatic) are performing. All of the dimensions and metrics previously available in the Mediation Overview report are still there, with the addition of DEU and ARPDEU.
As previously, in this report you can find Response Rate (also referred to as Ad Network Fill Rate or Availability Rate in competing platforms). This metric represents the % of fills for a demand source provided from the total bid requests sent to them. It is available at the instance level for mediated ad networks.
The revenues and impression count for traditionally mediated networks data in this report come from the mediated networks' reporting APIs.
For full instructions of the functionality available to you with DT's Dynamic Reporting, click here.
To make it easier, the Demand Performance report default view shows the following details when the report is opened:
- Split by “Demand Source Name” (with a default limit of 50 sorted by descending Revenue)
- The following metrics “Revenue”, “Publisher eCPM”, “Impressions”, “Response Rate” (in this order)
- Results are sorted by “Revenue” in descending order
- Three dimensions in the Pinboard “Demand Source Type”, “App Name” and “Device OS” (in this order) sorted by descending Revenue
Demand Performance Dimensions
- Set out below are the groups and the dimensions contained within them, relevant to the Network Performance report.
|Date/Time||-||Date and time of the report.|
The final status of the bid response received by the mediated network. The bid response values can be one of the following:
Lost on Price: Bid response lost because the price returned was lower than another bid in the auction.
Below the Floor Price: Bid response was rejected because it was lower than the publisher floor price passed on the bid request.
Blocked Category: Bid response was rejected because the campaign's IAB category corresponded to a blocked category by the publisher.
Blocked on Creative: Bid response was blocked by manual blacklisting of the creative ID.
Failed Creative ID Blocked: Bid response was automatically blocked due to a consistent low survival rate.
Invalid Response: Bid response failed because it was invalid. Common examples include, the JSON was invalid and the response was missing mandatory parameters. See our Demand Docs for a list of mandatory parameters.
No Bid: Bid response returned an HTTP 204 "No Content" response signaling the bidder had no bid for the auction.
Demand QPS Throttling: Bid response was blocked according to a manual QPS (Queries Per Second) cap set on the demand integration level.
Filtered out for Optimization: Bid request was automatically blocked due to an internal optimization mechanism that blocks 95% of unmonetized traffic.
HTTP Error: Ad request failed due to a web server error.
Timeout: Bid response failed because it exceeded the timeout window (350ms for RTB Bidders). A best practice is for Demand Partners to pass a no bid instead of timing out.
Capped: This metric is only relevant to waterfall mediated networks. The bid request was dropped when the frequency cap was reached.
|Demand Source Name||The name of the demand source, mediated network or DSP.|
|Demand Source Type||
The demand source type of integration. It can be one of the following: DT Exchange, Mediated Networks, SDK Bidding.
|Instance ID||The Instance ID as generated on the mediated network's dashboard.|
|Instance Name||The name of the instance as written in the instance settings.|
|Reporting Source||The source of the data. This can be either from DT's data or the mediated networks' reporting API.|
|Device||Advertising ID Availability||
Availability of Advertising ID (IDFA for iOS or AAID for Android) in the ad request.
|Device OS||The operating system of the phone/device.|
The name of the variant as written in the variant settings.
A variant is a group within a placement experiment or test. A placement test allows you to make informed decisions based on data by testing a different placement configuration on a subset of your users.
Once you have analyzed the results of the test, choose the variant that performs best.
|Inventory||App ID||The DT unique identifier for the app.|
|App Name||The name of the app as written in the app settings.|
|App Version||The version of the app.|
|Coppa||App compliance with coppa.|
|Placement ID||The DT unique identifier for the placement.|
|Placement Name||The name of the placement as written in the placement settings.|
Placement type describes the format and location of ads in your app according to the placement setting when it was created.
Placement types can be either:
DT FairBid or DT Exchange.
|Location||Country||The country from which the ad request was received.|
Demand Performance Metrics
Metrics appear in the left pane under the dimensions. Set out below are the metrics relevant to the Network Performance report.
|Delivery||Bid Requests||The number of outgoing requests sent from DT FairBid to each demand source after an ad request was received from the app.|
|Bid Responses||The number of 'valid bid responses' ('Won or 'Lost on Price') returned by the demand source.|
|Bids Won||The number of times the demand source won the auction.|
The rate at which a demand source provided valid bid responses ('Won' or 'Lost on price') out of the total number of bid requests received from DT FairBid. The calculation is Bid Responses divided by Bid Requests.
Other mediation providers may refer to this as 'Network Fill Rate' or 'Availability Rate'.
The rate at which available ads were displayed and became impressions. The calculation is impressions divided by fills.
|Win Rate||The rate at which a demand source won the auction out of the total number of bid responses it provided. The calculation is Bids Won divided Bid Responses.|
|Engagement||Avg. Rev. per Engaged User||
Average Revenue Per Engaged User. The calculation is Publisher Revenue divided by Engaged Users.
The total number of times a user clicked on an ad.
|Completion Rate||The rate at which a user completed viewing an ad. The calculation is Completions divided by Impressions.|
|Completions||The number of times a user completed viewing a video ad.|
|CTR||Click Through Rate. The rate at which users clicked on an ad they've viewed. The calculation is Clicks divided by Impressions.|
|Engaged Users||The number of unique users that had at least one impression in the selected timeframe.|
The number of times an ad was shown to a user.
When the ad comes from a waterfall mediated network, the impressions are retrieved via the mediated network's reporting API and is subject to change.
Effective Cost Per Mille (Thousand Impressions). Ad revenue generated per 1,000 ad impressions.
When the ad comes from a waterfall mediated network, the value may change over time as both impressions and revenues are retrieved via the mediated network's reporting API and is subject to change.
The total revenue generated from ads.
When the ad comes from a waterfall mediated network, the revenue is retrieved via the mediated network's reporting API and is subject to change.