> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/rtb/advertisers/reducing-measurement-discrepancies.md).

# Reducing measurement discrepancies

When integrating your demand with ExoClick RTB platform, how billable events are signalled affects how closely your counts align with the publisher's:

* **Include `burl` in your bid response** (alongside `nurl`) to be fired server-to-server when the impression (or click, in the case of CPC pricing models) becomes billable, so events are counted from the billable event rather than a client-side pixel.
* **Without `burl`,** ExoClick publisher zones that use billable-event counting will record `Impressions = 0` for that demand, so providing it matters for accurate reconciliation.
* **Reconciliation is between adjacent nodes only** in a multi-hop supply chain, each pair of networks aligns independently; it doesn't carry across the whole chain.
* **The billable event follows the pricing model** an impression for CPM or a click for CPC, per the `btype` field.
* **Reconcile clicks like-for-like** (valid + invalid together), and expect display formats to reconcile most reliably on impressions, and click formats on clicks.

<br>


---

# 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.exoclick.com/rtb/advertisers/reducing-measurement-discrepancies.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.