Reading your reports
How to interpret summary, click detail, and conversion detail views, and what to do when numbers don't line up.
Updated 2026-05-21
You have the same three report views as publishers, but scoped to your campaigns only.
Summary
Aggregated counts: total clicks, conversions, payout owed, average CR (conversion rate), broken down by campaign, day, country, and publisher. Use this for performance reviews and ROI checks.
Click detail
Row-level click log. Most useful when investigating quality of a specific publisher's traffic — sort by publisher, look at geo / device mix, conversion rate.
Conversion detail
Row-level conversion log including your transaction_id, the click ID, the publisher who drove it, payout, currency, and any rejection reason. Reconcile this against your billing system every cycle.
Reconciling with your billing system
The most common discrepancy:
"I see 102 conversions in my orders table, but the network shows 98."
Run through this checklist in order:
- Rejected conversions. Filter Conversion detail to "Rejected" — duplicates, chargebacks, and fraud-flagged events show up here and don't count in totals.
- Test conversions. If you fired test postbacks during integration with
transaction_idstarting withTEST-or similar, they're usually filtered out by the network. - Postback timing. Your DB stamps the order at checkout-complete; the network stamps it at postback-receive. A 5-minute window can shift counts across day boundaries.
- Currency conversion. If your store charges in EUR and you set the campaign payout in USD, the network records both. Compare payout in the network's reporting currency.
- Postback failures. Check the Postback log in your portal for any conversion postbacks that returned 4xx/5xx from the edge — those didn't make it.
For a clean reconciliation, store the network's click_id on every order row in your DB. Then a simple LEFT JOIN tells you which orders were tracked and which weren't.