Statistics reconciliation
Compare your numbers with ours by the same events and only between neighboring sides of the chain: each pair of participants has its own reconciliation.
What we count
Your account manager configures the event for the win, the impression and the billable event for the integration; find it out before launch.
| Event | How we count it |
|---|---|
| Request | Every processed request, with or without a bid. |
| Bid | A response with a bid. |
| Win | By the selected event: nurl, burl or our impression pixel. If none is selected, we don't count wins. |
| Impression and viewable impression | By the format's signal: our tracker in the creative, nurl, burl, or the push image load in the JSON feed. For popunder, the opening of the URL from the response. |
| Click | A visit through our click URL. |
| Billable event | One event: nurl, burl or our impression pixel. With CPC, the click. |
The amount for a billable event:
- OpenRTB, billing by
nurlorburl: the clearing price from${AUCTION_PRICE}, but not above our bid (Notifications, Price and floor). - OpenRTB, billing by our impression pixel: our bid.
- Popunder over OpenRTB: our bid, since the notifications have no price macro.
- JSON feed:
cpcfrom our response (Impression counting and payouts, Click).
Time, time zone, currency
- The event time is the moment the notice, pixel or click reaches us, not the request time.
- We accept notices for a limited time after the bid, so past days may grow slightly after the fact. Reconcile closed periods.
- The time zone is selected in the report: set the same one you count in.
- Amounts are in the account currency, converted at the rate on the event date: allow for discrepancies of a few cents.
Statistics in the publisher dashboard
- In the Reports section: metrics Requests, Impressions, Viewable impressions, Fill Rate, RPM, CPM, Clicks, Publisher profit; groupings and filters by date (hour, day, week, month), publisher, country, connection type, device, OS, browser, Zone ID and language.
- Fill Rate = impressions / requests × 100, RPM = revenue / requests × 1000.
- The reports have no bids or wins; ask the manager for them. External DSPs reconcile through the manager.
Common causes of discrepancies
| Cause | What happens | What to do |
|---|---|---|
The notice got 400, the event is not counted | ${AUCTION_PRICE} holds the macro, an encrypted price or a non-number; id or t was changed; the URL was encoded again; the acceptance period expired. | Pass the price as a plain number, for example 0.85; call the URL as it came and right after the event. |
| Different events | You count an impression by your render, we count by the configured event, which you don't call. | Call both nurl and burl. |
| Day boundary | Different time zones or a late notice. | Reconcile in one time zone with an hourly breakdown. |
| Repeated notices | A repeat gets 200 but is counted once. | Count one event per bid. |
| Bid after timeout | You dropped a late response; for us it is a bid without a win. | Reconcile bids and wins separately. |
| Invalid traffic | We don't count clicks that fail the quality check or popunder opens by bots. | Discuss a noticeable click discrepancy with the manager. |
What to send the manager
- The period and time zone.
- The integration identifier: the
idparameter from the URL. - A daily breakdown, and an hourly one for disputed days: requests, bids, wins, impressions, clicks, amount in the integration currency.
- Which event you count the impression and the billable event by: render,
nurl,burlor something else. - 5–10 bids with a discrepancy:
bid.id(the same asidinnurlandburl), event time, the price you passed. - Logs of the notice calls for these bids: full URL and HTTP response code.