The IA-dsp-staging Developer Hub

Welcome to the IA-dsp-staging developer hub. You'll find comprehensive guides and documentation to help you start working with IA-dsp-staging as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Buyer's Report

📘

This report is intended for use by Demand Partners

Introduction

The Buyer's Report is aimed at programmatic buyers using Fyber. The Buyer's Report enables you to perform in-depth analysis on the traffic you receive and your bidding landscape in order to optimize performance. The data shown in the Buyer's Report is based on aggregated data collected from the Fyber Marketplace and is updated on an hourly basis.

📘

Note

For full instructions of the functionality available to you with Fyber's Dynamic Reporting, click here.

Buyer's Report Dimensions

Set out below are the groups and the dimensions contained within them, relevant to the Buyer's Report.

Group NameDimensionDescription
Date/Time-The date and time of the report
AuctionAuction TypeThe type of auction - First Price, Second Price or Fixed Price
Bid StatusThis dimension describes the status of each full bid transaction and is comprised of the following options:

Won:
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.

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

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:
FairBid - new. This metric is only relevant to Traditional Mediated Networks buying FairBid. The bid request was dropped when the frequency cap was reached.

Blocked Advertiser Domain:
A bid response is blocked because the publisher specifically requested not to receive ads from this advertiser (usually a competitor).
Bid Price Bucket
DeliveryAd UnitAd units are containers you place in your apps to show ads to users.

Ad Units send ad requests to Fyber, then display the ads they receive to complete the request.

Type of ad unit can be either display, video or video and display.
SDK/Tag VersionSDK or JavaScript Tag version
DemandAdvertiser DomainThe advertiser's domain - for example, advertiser.com
Campaign IDThe campaign ID as defined by the advertiser in the bid response
Creative IDThe creative ID as defined by the advertiser in the bid response
Demand Source NameDemand partners who bid in the auction
Demand Source TypeThe type of demand integration. Can be one of the following:

Programmatic
Programmatic Mediation
Mediated Networks
Custom API
Seat IDSeat ID of the buyer on the DSP
Seat NameSeat name of the buyer on the DSP
DeviceDevice ID Type
Device Manufacturer
Device OSThe device operating system
InventoryAd SizeThe creative ad size passed in the ad markup
Ad Unit TypeType of ad unit container can be either video, display, video & display or native. The ad types available to an ad unit depend on the placement type you selected when creating it. (Suggest removing this)

Display: An ad unit type that supports display only
Video: An ad unit type that supports video only
* Video & Display: An ad unit type that supports video or display
Ad Unit Name
App BundleThe app's unique store identifier
App IDApp identifier within Fyber's system
App NameThe name of the app
Placement IDPlacement identifier in Fyber's system
Placement NameName given by publisher to a placement they created on Fyber
Placement TypePlacement 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.

Banner: A basic placement type that appears at the top & bottom of the device screen. Doesn't' support video content.
Rewarded: An ad placement type Supports video content.
* Interstitial: Full-page ads appear at natural breaks & transitions, such as level completion. Supports video content.
Product LineEither Fyber FairBid or Fyber Marketplace
LocationCountryThe country in which the impression was served

Buyer's Report Metrics

Metrics appear in the left pane under the dimensions.

GroupMetricDescriptionForumla
BidsAvg. Floor PriceAverage floor price of all the bid requestsSum (Floor Prices) / Sum(Bid Requests)
Bid RequestsThe number of requests sent to each demand partnerSum (Bid Requests)
AuctionClearedThe number of ads that were successfully sold via an auctionSum (Bids Won)
Avg. Clear PriceThe average price that the demand partner paid for 1000 impressionsSum (Clear Price) / Sum (Cleared)
Demand Fill RateTotal number of impressions divided by the number of bid requests. This is the "full funnel" success rate indicator.Sum (Impressions) / Sum (Bid Requests)
Avg. Win Bid PriceAverage winning bid price, in terms of CPM. Reflects the average price of all bids that won the auction. In case of a second price auction, Avg. Win Bid Price is higher than the price the demand partner pays for the impression.Sum (Win Bid Price) / Sum (Clears)
DeliverySurvival RateTotal number of impressions divided by total number of bids that won the auctionSum(Impressions) / Sum(Cleared)
EngagementClicksThe total number of times users click an adSum (Clicks)
Completion RateThe ratio of rewarded video completions to rewarded video impressionsSum (Rewarded Completions) / Sum (Impressions)
CTRClick Through Rate - the total number of clicks divided by the total number of impressions[Sum (Clicks) / Sum (Impressions)] * 100%
Rewarded CompletionsThe number of times users completed watching a rewarded videoSum (Rewarded Completions)
RevenueInternal Users: Gross Revenue

Demand Partners: Total Spend
Total payment received from demand. Some of this revenue is paid directly by the demand partner.Sum (Total Revenue)
Avg. Bid PriceThe average price the demand partner bids, in terms of CPMSum (Bid Price)/ sum(Bid Requests)
ImpressionsThe number of time an ad is shownSum (Impressions)
Demand Fill RateThe percentage of ads served (impressions) out of the bid requests sent to a particular demand partnerSum ((Impressions) / Sum (Bid Requests)) * 100
Bid Response RateThe percentage of "valid responses" ("won" or "lost on price" responses) received from a demand partner out of the bid requests sent by the exchangeSum ((Bid Responses ('won' or 'lost on price') / Sum (Bid Requests)) * 100
Bid ResponsesThe number of "valid bid responses" ("won" or "lost on price" responses) returned by the demand partner to bid on the inventorySum ((Bid Responses (with status 'won' or 'lost on price'))
Network Clear RateIndicates how successful a demand partner was to win the auctions in which they participatedSum (Cleared) / sum(Bid Requests)
Publisher PayoutNet revenue per publisher before ad serving fees (for Programmatic Mediation Networks only)Sum (Publisher Revenue)

Updated about a month ago

Buyer's Report


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.