> 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/getting-started/what-is-the-difference-between-hb-analytics-and-ad-revenue-insights-old.md).

# What is the Difference Between HB Analytics and Ad Revenue Insights? (OLD)

**HB Analytics logs all calls related to your Header Bidding setup.**

It is used to ensure that your Header Bidding setup functions correctly, and that the data returned from your SSPs loads in a timely and reliable manner. This data can be used for both technical monitoring and yield optimisation. The HB Analytics module is a natural companion to HB Manager for data collection, but it can also be used with other Header Bidding solutions or “wrappers”.

**The main difference between HB Analytics and Relevant Yield’s Ad Revenue reports lies in the datasets and collection methods they use.**

HB Analytics collects data directly from your website and the responses from your Header Bidding setup. This means the data is captured in near real time (with a delay of around three seconds). In contrast, Relevant Yield’s Ad Revenue Insights data is gathered once per day via the SSPs’ APIs.

These tools also track different types of metrics, although there is some overlap. As a result, they serve different purposes and can complement each other by providing additional, valuable insights.

### Comparing HB Analytics and Ad Revenue Insights

#### Monitor technical performance

**HB Analytics** provides near real-time feedback, with an approximate three-second delay. Use it to detect dropped ad tags, bidder activity declines, and other urgent issues.

**Ad Revenue Insights** provides daily data from SSP and ad server APIs. Use it to review platform-reported results after reconciliation.

#### Understand header bidding activity

**HB Analytics** logs calls and performance by site and placement. It helps you assess wrapper health, provider performance, and bid responses.

**Ad Revenue Insights** consolidates data that SSPs and ad servers recognise as valid. Its figures can differ from header bidding logs.

#### Analyse bids and revenue

**HB Analytics** captures returned and losing bids, response times, and rendering times. Compare call-level revenue with SSP reports to identify rejected traffic and potential losses.

**Ad Revenue Insights** reflects revenue adjustments from SSP and ad server reconciliation. This data better supports revenue forecasting and financial reporting.

#### Optimise performance

**HB Analytics** supports rapid testing and alerting. Use the near-instant feedback to validate changes to your header bidding setup.

**Ad Revenue Insights** provides advertiser, buyer, and direct campaign data. Use these validated dimensions to evaluate commercial performance.

{% hint style="info" %}
Use HB Analytics for operational monitoring and bid-level analysis. Use Ad Revenue Insights for reconciled revenue and platform-reported performance.
{% endhint %}

### In conclusion:

Both products complement each other well, and it is important to understand that although both provide reports, they focus on two different areas:

* **The HB Analytics module** concentrates on logging and reporting ad calls and their returns.
* **The Ad Revenue Insights** module focuses on collecting and reporting consolidated bidder and ad server data.

Both are important for a comprehensive evaluation of performance.


---

# 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/getting-started/what-is-the-difference-between-hb-analytics-and-ad-revenue-insights-old.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.