Browse the documentation

RTB Statistics & Reports

Applies to: Advertisers · Optional feature — available when your network has it switched on

What this is#

When you buy traffic with your own bidder through an RTB campaign, the ad server sends your bidder a bid request for every matching impression. The RTB pages show what happened to those requests: how many your bidder answered, how many it won, how fast it responded, what went wrong and what you spent.

There are three places to look, all under RTB (or Campaigns → RTB on accounts without a separate RTB menu):

  • Dashboard — a focused dashboard with RTB panels: an overview, your top RTB networks, campaigns and countries, bot browsers and quick RTB settings.
  • RTB Stats — the full table, grouped and filtered any way you like, with an error breakdown per row.
  • RTB Reports — ready-made reports with a chart: traffic against bids per day, per campaign and per country.

When you'll use this#

  • After launching an RTB campaign, to check that requests arrive and your bidder answers them.
  • When spend drops: to see whether you stopped bidding, started losing auctions, or are timing out.
  • To compare your own counts with what your bidder reports.
  • To find the countries, sites or ad spaces where your bids win and pay off.

Step by step#

Read RTB Stats#

  1. Open RTB → RTB Stats.
  2. Pick a Date range, and optionally a Campaign and an Ad type.
  3. Under View, choose Hourly, Daily, Weekly, Monthly or Summary (one total row per group).
  4. Under Group by, choose how rows are split: Date, Campaign, Country, ISP, Domain, Ad Space, RTB Network, Ad Type, Device Type, OS, Browser or Connection.
  5. Use Metrics to show or hide columns, then click Refresh. Export CSV downloads the table.
  6. Click a non-zero Errors cell to open the Error breakdown for that row: every error code with its count, for exactly the slice you clicked.

Read RTB Reports#

  1. Open RTB → RTB Reports.
  2. Pick the date range; filter by Campaign, RTB Network or Ad Type. All tabs share these filters.
  3. Switch tabs:
    • Overview — Daily Performance: requests, bids, wins, views and clicks, spend and eCPM per day, with a chart you can hide.
    • Campaigns — the same figures By Campaign, with Win % and CTR.
    • GEO — the same By Country.

Use the RTB dashboard#

Open RTB → Dashboard. It works like your main dashboard: add, remove and rearrange panels. Resetting it brings back the RTB default panels.

Options reference#

RTB Stats metrics#

Metric What it means
Requests Bid requests the ad server sent to your bidder.
Avg Bid Floor The average floor price on those requests. Bids below the floor are ignored.
Avg Resp (ms) How long your bidder took to answer, on average.
Bids Requests your bidder answered with a bid.
Bid Rate Bids as a share of requests.
Wins Bids that won the auction.
Win % Wins as a share of requests.
No Results Requests your bidder answered without a bid.
Timeouts Requests your bidder didn't answer in time.
Skip Timeouts Requests not sent at all, because your bidder was timing out too often at that moment.
Skip No Bids Requests not sent at all, because your bidder kept answering without a bid for that country or ad space. The ad server pauses sending there for a few minutes and then tries again.
Views / Clicks / CTR What your winning ads delivered.
eCPM What you paid per thousand views.
Errors Answers that couldn't be used (invalid response, wrong format, connection problems). Click the cell for the breakdown.
Spent What your won impressions cost.
Network Views / Network Clicks / Network Spend The figures your RTB network reports through its own API, where that connection is set up. Empty otherwise.
Views Discrepancy / Clicks Discrepancy How far the network's count is from ours, as a percentage.

Example#

Nadia runs a bidder for a mobile-app advertiser. Her spend halves overnight. In RTB Stats, grouped by Date, she sees Requests steady, Bids steady, but Timeouts jumped and Skip Timeouts appeared: her bidder slowed down after a deploy, so the ad server first saw timeouts and then stopped sending part of the traffic. Avg Resp (ms) confirms it. She scales the bidder back up; the next day Skip Timeouts is back to zero and spend recovers.

Tips#

  • Watch Avg Resp (ms) against the timeout your account manager set for your RTB network; answer well inside it.
  • Skip No Bids isn't an error: it saves your bidder from requests it never buys. If you change your bidding and want traffic back sooner, ask your account manager.
  • Group by Ad Space or Domain to find placements where you win often but pay too much.
  • A steady discrepancy of a few percent between our counts and your network's is normal; a sudden jump is worth a look.

Troubleshooting#

Symptom Likely cause Fix
Requests is zero Campaign paused, no budget, or its targeting matches no traffic Check the campaign's status, budget and targeting.
Many Timeouts Your bidder answers too slowly Speed up the bidder, or ask your account manager about the network's timeout.
Many Errors Bid responses the ad server can't read Open the error breakdown; compare your response with the RTB integration reference.
Bids but almost no Wins Bids at or near the floor, or below competing bids Raise bids where it pays; check Avg Bid Floor.
Network columns empty No API connection for your RTB network Ask your account manager whether network reporting can be set up.