Read your RTB reports
See how many bid requests your seat sent LtvAdx, how often LtvAdx bid, at what price, and where, by day, hour, channel or publisher.
RTB Reports shows your seat's own bid requests to LtvAdx and what LtvAdx did with them. Use it to confirm an integration works, to see which channels and publishers LtvAdx bids on, and to spot a floor that is too high.
It covers requests you send to LtvAdx only. For a bidder that LtvAdx calls, see the seat's row on DSP seats. To set up sending requests, see Connect with OpenRTB.
Open the report
- Open RTB Reports.
- Choose a date range with the date picker. The page opens on the last 30 days. A range can span up to 366 days. Days and hours are in UTC.
- Read the five figures at the top, then pick a tab: By Day, By Channel, By Publisher or By Hour.
- Select Export CSV to download the table you are looking at.
The figures at the top always cover the whole date range and do not change with the tab. The chart on By Day plots requests, LtvAdx bids and the bid rate for each day.
What the numbers mean
| Figure | What it is |
|---|---|
| Bid requests | Requests from your seat that reached a bidding decision |
| LtvAdx bids | Requests LtvAdx answered with a bid |
| Bid rate | Bids as a share of requests |
| Avg bid CPM | The average price of the bids LtvAdx made |
| Avg floor | The average floor in your requests that had one |
| Errors | Requests that failed inside LtvAdx while it was deciding. This is normally 0 |
| Avg response | How long LtvAdx took to decide, in milliseconds. It excludes network travel time |
Things to know:
- There are no wins. A bid here means LtvAdx answered with a bid. Whether it then won your own auction happens on your side and isn't reported back, so this report has no win rate.
- Only requests that reach a decision are counted. A request with a missing or wrong key, one over your rate limit, one with no impression, one for a channel ID LtvAdx doesn't recognise, or one for a publisher your seat isn't allowed does not appear. If your requests are failing for those reasons you will see fewer requests than you sent, not a high error count.
- Prices are per thousand impressions, in US dollars. A bid is the price LtvAdx offered. It isn't money paid to you. This report shows no payments.
- The By Hour tab adds up each hour of the day across the whole range. It shows what time of day your requests peak, not a timeline.
- A row labelled "Unknown channel" or "Unknown publisher" is a request LtvAdx saw but can't match to a record.
Exchange fee on inbound wins (Beta)
Below the table, Exchange fee on inbound wins lists the requests your seat sent where LtvAdx's bid won and its ad played and was billed. For each one, LtvAdx takes its exchange fee for your seat, a percentage of the clearing price shown at the top of the panel, before the publisher's share. The panel shows, for the dates you chose and by UTC day, the billed wins, the clearing prices, the exchange fee and the publisher's credit at billing time. Only billed impressions count, so an ad that never played is not in it. The amounts are in US dollars.
The CSV
Export CSV downloads the table for the tab you are on and the dates you chose, with a total row. It has more columns than the page: wins, no-bids and timeouts. For your seat, wins and timeouts are always 0, and no-bids is the number of requests LtvAdx passed on. If the file was cut short because it was very large, the page tells you so.
If something goes wrong
| What you see | What to do |
|---|---|
| "No bid requests in this date range" | Widen the dates. If you have just started, give it a few minutes. If requests are being sent and none appear, check the key and channel IDs in Connect with OpenRTB. |
| Requests are high but bids are 0 | LtvAdx has no eligible demand for those channels, or your floors are above what advertisers pay. Supply paths shows which publishers this affects. |
| "Could not load the report" | Try again. If it keeps failing, contact support. |
| "Date range is limited to 366 days" | Pick a shorter range. |