> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/hb-analytics/reporting-and-metrics/hb-analytics-dimensions-and-metrics.md).

# HB Analytics - Dimensions and Metrics

Here we cover the Dimensions and Metrics available in the HB Analytics. Please notice that the Dimensions shown here are the Default Dimensions, if you have added custom dimensions they are most likely not covered in this article.

## Dimensions

<table><thead><tr><th width="227.0531005859375">Dimension</th><th>Description</th></tr></thead><tbody><tr><td><strong>Time Period</strong></td><td>Defines the report breakdown granularity. HB Analytics supports periods down to 10 minutes, subject to your contract. Smaller periods aggregate into daily values.</td></tr><tr><td><strong>Publisher</strong></td><td>The publisher account where the auction occurred.</td></tr><tr><td><strong>Site</strong></td><td>The site where the auction occurred.</td></tr><tr><td><strong>Placement</strong></td><td>The placement where the auction occurred.</td></tr><tr><td><strong>Bidder</strong></td><td>The SSP or source returning a bid through your Prebid configuration.</td></tr><tr><td><strong>Source</strong></td><td>The bidder's name or ID for this auction and placement. Use it to verify setup IDs and investigate SSP rules.</td></tr><tr><td><strong>Bid-range</strong></td><td>Returned bidder values grouped into tiers. Use it to see where a bidder usually bids and adjust bid levels.</td></tr><tr><td><strong>Creative Size</strong></td><td>The served creative size, such as <code>300x250</code> or <code>160x600</code>.</td></tr><tr><td><strong>Media Type</strong></td><td>The served media type, such as video or banner.</td></tr><tr><td><strong>Revenue type</strong></td><td>Whether revenue and metrics relate to Direct, Deals, or OpenRTB performance.</td></tr><tr><td><strong>Demand Channel</strong></td><td>Whether revenue and metrics relate to ad server or header bidding performance.</td></tr><tr><td><strong>Country</strong></td><td>The user's country. Use it to compare regional and country performance.</td></tr><tr><td><strong>Prebid Configuration</strong></td><td>The name of the Prebid configuration, including child configurations.</td></tr><tr><td><strong>Hostname</strong></td><td>The domain name of the website or app hosting the auction.</td></tr><tr><td><strong>Operating system</strong></td><td>The operating system used to access the website or app during the auction.</td></tr><tr><td><strong>Browser name</strong></td><td>The browser used during the auction.</td></tr><tr><td><strong>Browser version</strong></td><td>The browser version used during the auction.</td></tr><tr><td><strong>Platform</strong></td><td>The platform used to access the website or app during the auction.</td></tr><tr><td><strong>URL</strong></td><td>The specific web address visited during the auction.</td></tr><tr><td><strong>Prebid.js version</strong></td><td>The Prebid.js version running on the site or publisher account.</td></tr><tr><td><strong>Floor range</strong></td><td>A description of the floor prices used.</td></tr><tr><td><strong>Ads. Floor optimised</strong></td><td>Whether Google floor price optimization is on or off when <strong>Adserver optimized %</strong> is set on placements.</td></tr><tr><td><strong>Host Name</strong></td><td>The host name. This usually matches the domain.</td></tr><tr><td><strong>Is approximation</strong></td><td>AdX revenue whose CPM is estimated from earlier traffic. GAM reports usually provide final data after about one hour.</td></tr><tr><td><strong>Adserver bids</strong></td><td>The number of bid requests sent as ad requests to an ad server with real-time logging.</td></tr></tbody></table>

## Metrics

<table><thead><tr><th width="189.3563232421875">Metric</th><th>Description</th></tr></thead><tbody><tr><td><strong>Revenue</strong></td><td>Gross revenue is the accumulated value of winning Prebid bids. It includes bids later overruled by the ad server.</td></tr><tr><td><strong>Auctions</strong></td><td>The number of Prebid auctions held.</td></tr><tr><td><strong>Ad Unit Requests</strong></td><td>The total number of ad unit requests. An auction can include multiple ad unit requests.</td></tr><tr><td><strong>Impressions</strong></td><td>The number of sold impressions used by Prebid.</td></tr><tr><td><strong>Winning Bids</strong></td><td>The number of winning Prebid impressions before the ad server decides whether to use them.</td></tr><tr><td><strong>eCPM</strong></td><td>The average CPM of all won and used impressions.</td></tr><tr><td><strong>Ad unit eCPM</strong></td><td>The average CPM of all ad unit requests.</td></tr><tr><td><strong>Auction eCPM</strong></td><td>The average value of all auctions. It is usually higher than ad unit eCPM because an auction can include multiple ad unit requests.</td></tr><tr><td><strong>Fill rate%</strong></td><td>The percentage of impressions relative to ad unit requests.</td></tr><tr><td><strong>Bid eCPM</strong></td><td>The average CPM of all bids returned for the Prebid auction.</td></tr><tr><td><strong>Bid requests</strong></td><td>The number of bid requests sent from auctions. Each ad unit request usually sends one request per connected SSP or source. Some SSPs send one request per dimension.</td></tr><tr><td><strong>Bid rate%</strong></td><td>The percentage of bid requests answered with a bid response.</td></tr></tbody></table>

{% hint style="warning" %}
**Important:** Bid rate% is not compatible with these dimensions:

* Bid Range
* Creative Size
* Media Type
* Revenue Type

Combining Bid rate% with these dimensions always returns a 100% Bid rate%.
{% endhint %}

<table><thead><tr><th width="223.1187744140625">Metric</th><th>Description</th></tr></thead><tbody><tr><td><strong>Total bid revenue</strong></td><td>Revenue from all returned winning bids across each ad unit request. It can exceed gross revenue because not every winning bid is shown.</td></tr><tr><td><strong>Cancelled bids</strong></td><td>Bids interrupted when a user closes a tab or similar.</td></tr><tr><td><strong>Avg. response ms</strong></td><td>The time from auction start until a bidder returns a response.</td></tr><tr><td><strong>Avg. render ms</strong></td><td>The time from auction start until the ad renders.</td></tr><tr><td><strong>Timed out bids</strong></td><td>Bids without a response before the timeout threshold. Slow loading can cause timeouts.</td></tr><tr><td><strong>Timed out bids%</strong></td><td>The percentage of bids that timed out.</td></tr><tr><td><strong>No bid responses</strong></td><td>The number of bids without a response.</td></tr><tr><td><strong>Bid responses</strong></td><td>The number of bids that received a response.</td></tr><tr><td><strong>Failed renderings</strong></td><td>The number of bids that failed to render.</td></tr><tr><td><strong>Unique bid revenue</strong></td><td>Revenue from bids where no other SSP returned a bid response.</td></tr><tr><td><strong>Incremental bid revenue</strong></td><td>Revenue added by the winning SSP, calculated as the winning bid minus the second-highest bid.</td></tr><tr><td><strong>Lost revenue to adserver</strong></td><td>Revenue lost when the ad server serves another ad or no ad.</td></tr><tr><td><strong>Bid density%</strong></td><td>Bid responses divided by ad requests. It can exceed 100% when an SSP sends multiple responses.</td></tr><tr><td><strong>Win rate%</strong></td><td>Impressions divided by bid responses.</td></tr><tr><td><strong>Page Views</strong></td><td>One page view for all auctions during one page load, until the user navigates elsewhere.</td></tr><tr><td><strong>Sessions</strong></td><td>Similar to page views, but remains valid while the user keeps the current tab open, including across page navigation.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.relevant-digital.com/hb-analytics/reporting-and-metrics/hb-analytics-dimensions-and-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.