The Additional Reading Developer Hub

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

Get Started    

Auctions Report

This report is intended for use by Publishers.


The Auctions report provides a convenient way to track performance metrics such as revenue, number of impressions, number of clicks and more. It also enables you to perform in-depth analysis on your auction landscape and gather insights on the performance of the millions of transactions happening daily. The data shown in the Auctions report is based on aggregated data collected from the Fyber Marketplace, it is updated on an hourly basis with data latency of approximately 3 hours.


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

Auctions Report Dimensions

Set out below are the groups and the dimensions contained within them, relevant to the Auctions report.

Group Name



The date and time of the report


Auction Type

Describes whether an auction was either First Price, Second Price or Fixed Price

Deal ID

The unique identifier string passed in the bid request to signal the presence of a PMP



The age of the user when available.

Fyber does not collect data on users below 13 and abides by all COPPA regulations


The gender of the user, when available


SDK/Tag Version

Version of the source SDK or JavaScript tag

SDK Renderer

The renderer of the SDK

Winning Demand

Advertiser Domain

The destination domain that the advertiser has set for a given ad

Buying Mechanic

Programmatic or Mediation

Campaign ID

The campaign ID as defined by the advertiser and sent by the advertiser in the bid response

Creative ID

The creative ID as defined by the advertiser and sent by advertiser in the bid response

Creative Type

The format of the ad that was displayed as returned in the ad response. Can be one of the following:

  • Display
  • Video
  • Display or Video

Demand Source Name

Demand partner that won the auction

Demand Source Type

Type of demand integration. Can be one of the following:

  • Programmatic
  • Programmatic Mediation
  • Mediated Networks
  • Custom API

Seat ID

Seat ID of the winning buyer on the DSP's side

Seat Name

Name of winning buyer on the DSP's side


Connection Type

The type of connection as sent in the ad request. Can either be wifi, 3G, 4G.

Device Carrier

The carrier to which the device is registered. For example Verizon or AT&T.

Device ID Type

The type of unique device identifier. Can be either IDFA or AAID.

Device Language

The language of the operating system installed on the device

Device Manufacturer

The company that manufactured the device. For example Apple or Samsung.

Device Model

The model of the device on which the app is installed

Device OS

The mobile operating system on the device

Device OS Version

App's mobile operating system


Ad Size

The creative ad size as was defined by the advertiser

Ad Unit ID

The unique identifier of the ad unit in the Fyber system

Ad Unit Name

The name of the ad unit

Ad Unit Type

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

Native: A customisable ad unit type that matches the look and feel of the app. Ads appear inline with app content.

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

App Bundle

App ID

App identifier within Fyber's system

App Name

The name of the app

Category (App Store)

Category (IAB)

The category in which the app is placed, IAB categories are important for buyers to understand the content quality and context. Buyer networks use this data to target their campaign. A complete list can be downloaded here.


Indicated whether users has requested to not be tracked

Instance ID

The instance ID as generated by the demand network. Notice: this is referred to differently, by various demand networks

Instance Name

A name manually provided by the publisher for a mediated network's placement

Placement ID

Placement identifier in Fyber's system

Placement Name

A name given by a publisher to a placement they created on Fyber

Placement Type

Placement type describes how ads will look in the 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 or bottom of the device's screen. Doesn't' support video content.

Rewarded: An ad placement type that supports incentivized video content.

Interstitial: Full-page ads appear at natural breaks & transitions, such as level completion. Supports video content.

Product Line

Either Fyber FairBid or Fyber Marketplace



The country in which the user is located

Language Code

Language Type


Overridden Rank

For mediated networks, describes whether rank was manually overridden by publisher. Can be either "Overridden" or "Not Overridden".

Winning Demand Network Rank

The rank of the demand partner that won the auction. Applicable only to mediation or custom API demand sources.

Auctions Report Metrics

Set out below are the groups and the metrics relevant to the Auctions reports.

Group Name


Ad Requests

The number of requests for ads sent from an application to the servers of the exchange. Note - ad requests are not the same as bid requests.

Sum (Ad Requests)

Avg. Clear Price

The average price that the demand partner paid for 1000 impressions.

Sum (Clear Price)/Sum (Cleared)

Clear Rate

Reflects how many auctions were cleared out of the ad requests received

Sum (Bids Won)/Sum
(Ad Requests)


The number of ads that were successfully sold via an auction

Sum (Bids Won)


Fill Rate

The average cost of a thousand impressions

{(Revenue/Sum (Impressions)}
x 1000


Avg. Floor Price

Average floor price of all the ad requests received

Sum (Floor Prices) /
Sum (Ad Requests)

Avg. Win eCPM

Average 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 the price the demand partner will pay for the impression.

Sum (Win Bid Price) /
Sum (Cleared)


Survival Rate

Total number of impressions served divided by total winning bids

Sum(Impressions) / Sum(Clears)



The number of times users click on an ad

Sum (Clicks)

Completion Rate

The ratio of rewarded video completions to rewarded video impressions

Sum (Rewarded Completions) / Sum (Rewarded Impressions)


"CTR" means clickthrough rate and equals the total number of clicks divided by the number of impressions.

[Sum (Clicks) / Sum (Impressions) ] * 100%


The average number of ads served per unique user in a selected timeframe

Sum (Impressions) /
Sum (Unique Users)


The number of ads shown to users

Sum (Impressions)

Rewarded Completions

The number of times users completed watching a rewarded video

Sum (Rewarded Completions)

Unique Users

The number of all unique users that triggered at least one ad request during selected timeframe.
De-duplication is done in real time, based on the selected dimensions. This metrics is used to calculate the following metrics:

  • DAU (daily active users)
  • ARPDAU (average revenue per daily active user)
  • Ad Frequency (impressions / unique users)

To view DAU:

  • Select the Unique User metric
  • Filter selected timeframe to a one day range OR
  • Split by date/time and view with daily granularity (1D)

Sum (Unique Users [by device ID, with at least one ad request])



ARPU is calculated by dividing Total Revenue by the number of Unique Users. ARPDAU helps answer the question “how well do I monetise my users?” Typical splits include ARPDAU by app, creative type, and placement type

To view ARPDAU (Average Revenue per Daily Active User):

  • Select the ARPU metric
  • Filter selected timeframe to a one day range OR
  • Split by date/time and view with daily granularity (1D)

(Total Revenue) / (Unique Users)


A percentage of the eCPM. Fee is paid to Fyber by a publisher for Programmatic Mediation Impressions.

Sum (fee)

Total Revenue

Total payment received from demand. Some of this revenue will be paid directly by demand partner

Sum (Total Revenue)

Updated 4 days ago

Auctions Report

Suggested Edits are limited on API Reference Pages

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