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 Fyber Marketplace. The report updates once a day at 10.00am 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 counts 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 Fyber'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||-||The date and time of the report|
|Ad Behavior||Placement Type||Placement type describes how ads will look in your app and where ads will be located. Optional Placement types can be either banner, interstitial or rewarded.
A basic placement type that appears at the top & bottom of the device screen. Doesn't' support video content.
An ad placement type Supports video content.
Full-page ads appear at natural breaks & transitions, such as level completion. Supports video content.
|Demand||Bid Status||This dimension describes the status of each full bid transaction and is comprised of the following options:
The winning bid of the auction.
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.
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 consistent low survival rate.
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.
Bid response returned an HTTP 204 "No Content" response signalling 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.
Ad request failed due to a web server error.
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.
FairBid - new. This metric is only relevant to Traditional Mediated Networks buying FairBid. The bid request was dropped when the frequency cap was reached.
|(Winning) Demand Source Name||Demand partner that won the auction|
|Demand Source Type||Type of demand integration. Can be one of the following:
A demand partner connected via a bidder sending real-time bids to Fyber's auctions
A mediated network, connected via a bidder sending real-time bids to Fyber's auctions
A traditional ad network, connected to Fyber Mediation via the SDK APIs and participates in the auction using the defined fixed CPM or the mock bid (Auto CPM)
A demand partner, connected to Fyber's auctions without sending real-time bids, but only using mock bids
|Reporting Source||The source of the data. Can be either from Fyber's data or the mediated networks' reports.|
|Device||Device OS||The apps mobile operating system|
|Inventory||App ID||App identifier within Fyber's system|
|App Name||The name of the app|
|Instance ID||The Instance ID as generated by the demand network. Note: This is referred to differently, by various demand networks.|
|Instance Name||The name you provided to a mediated network's instance|
|Placement ID||A Placement's identifier in the Fyber system|
|Placement Name||A name given by publisher to a placement they created on Fyber|
|Placement Type||Placement type describes how ads will look in your app and where ads will be located. Placement types can be either banner, interstitial or rewarded.
A basic placement type appearing at the top or bottom of the device's screen. Does not support video content
An ad placement type supporting video content
* Full-page ads appear at natural breaks & transitions, such as level completion. Supports video content
|Product Line||Either Fyber FairBid or Fyber Marketplace|
|Location||Country||The country in which the impression was served|
|Reporting Source||Reporting Source||The source of the data. Can either by Fyber's data or the demand partner's reports|
|Experiments||Variant Name||Each variant defines how you split your traffic depending on your setup and platform configurations to each group|
|Variant ID||The Ad Unit ID|
Demand Performance Metrics
Metrics appear in the left pane under the dimensions. Set out below are the the metrics relevant to the Network Performance report.
|Engagement||Rewarded Completions||The number of times users completed watching a rewarded video|
|Unique Impressions||The number of unique users that had at least one impression in the selected timeframe|
|Completion Rate||The ratio of rewarded video completions to rewarded video impressions|
The number of impressions over fills.
[Sum (Impressions) / Sum (Ad Requests) ] * 100%
|Delivery||Bid Requests||The number of requests sent to each demand partner|
|Bid Responses||The number of "valid bid responses" ("Won" or "Lost on Price" responses) received from a demand partner out of the bid requests sent by the exchange.|
|Clicks||The total number of times users click on an ad|
|CTR||Click-Through Rate is the total number of clicks divided by the total number of impressions|
|Demand Fill Rate||The percentage of ads served (impressions) out of the bid requests that were sent to a particular demand partner|
|Impressions||The total number of ads shown to users across all of the selected placements and apps|
|Win Rate||The number of bids won over the number of bid responses|
|Revenue||eCPM||Effective cost per thousand impressions.
If the demand partner is a mediated network, the eCPM is calculated by dividing the reported revenue by the reported impressions.
Both the reported revenue and the reported impressions may change over time retroactively by the mediated network. This affects the presented figures of those metrics.
eCPM is calculated as (Total Earnings / Impressions) x 1000
|Publisher Revenue||Your earnings accrued so far. This amount is subject to change when your earnings are verified for accuracy at the end of every month.|