> 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/publishers/reducing-measurement-discrepancies.md).
# Reducing measurement discrepancies
RTB discrepancies - the gap between what one side counts and what the other counts or bills are largely driven by how impressions and clicks are tracked on the client side. To keep them low when integrating supply:
* **Prefer server-to-server (S2S) counting** over browser-based redirect chaining. Browsers can collapse intermediate redirect hops, especially Chrome on Android. So an event that rendered may never be logged. This is the biggest single driver of click discrepancies.
* **Use a header (`302`) redirect rather than a meta-refresh redirect** it's more reliable for firing tracking calls.
* **Fire the BURL and impression calls correctly**, so billable and rendered events are both recorded. See Billable Event Counting (BURL) for [OpenRTB 2.4](/rtb/publishers/open-rtb/pub-open-rtb-2.4-response.md#billing-notification) / [OpenRTB 2.5](/rtb/publishers/open-rtb/pub-open-rtb-2.5-response.md#billing-notification) for how billable-event counting works and how to reconcile it against "Served" metrics.
* **Reconcile clicks like-for-like.** Each side applies its own invalid-click and multiclick filtering, so compare totals on the same basis (valid + invalid together) before treating a gap as an error.
* **Be aware that some segments run higher on discrepancy** notably video formats, and client-side measurement methods such as Client Hints collection, `sendBeacon`, and browser "heavy ad" interventions.
## Discrepancy bands
Discrepancies are normal in RTB; the goal is to keep them low enough for clean invoicing rather than to eliminate them.
| Discrepancy | Action |
| ----------- | ----------- |
| Under 5% | Acceptable |
| 5–10% | Monitor |
| Over 10% | Investigate |
## Troubleshooting workflow
1. Compare your counts against the partner's and use the **Served Ratio** to see where the gap opens.
2. **Segment by device and browser** certain combinations (notably Android + Chrome) tend to run higher on discrepancy, because of how the browser handles navigation and redirects.
3. Check the **redirect method** a header (`302`) redirect is more reliable than a meta-refresh redirect.
4. Confirm the **BURL and impression calls are firing** as expected.
5. For traffic that crosses **multiple networks**, reconcile each adjacent pair independently. Alignment between two nodes doesn't propagate across the whole chain.
---
# 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/publishers/reducing-measurement-discrepancies.md?ask=&goal=
```
`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.