Reading your reports
Understand the three report views and which one to use when reconciling traffic with the network.
Updated 2026-05-21
Your publisher portal ships three report views. They share filters but answer different questions.
Summary
Aggregated counts across the time window you select, broken down by campaign, day, country, device, sub-ID, and event. Use this view when you want a high-level read of what's making money.
Click detail
Row-level log of every click that hit the network on your tracking links. Each row includes the timestamp, campaign, your sub-IDs, country, device, IP-derived city, and whether the click resulted in a conversion. Use this view when:
- You're debugging a sudden drop in conversion rate
- You want to verify the network is receiving your
transaction_id - You're investigating fraud (repeated IPs, suspicious UAs, etc.)
Conversion detail
Row-level log of every conversion fired against your clicks. Includes the event name, payout, the original click's sub-IDs, advertiser-provided fields, and any rejection reason if the conversion was held or rejected. Use this view when:
- Your own ledger disagrees with the network's payout total
- A specific transaction never showed up — search by your
transaction_id - You want to export conversions for billing or audience tools
All three views support CSV export. Apply your filters first, then click Download CSV. The exported file matches the visible columns and respects your timezone.
Why a conversion might not show up
- Reject reasons — the advertiser sometimes rejects events (chargeback, duplicate, fraud filter). Look at the rejection field in Conversion detail.
- Outside the campaign cap — campaigns have daily and per-publisher caps. Once hit, additional conversions roll over or get dropped depending on the network's policy.
- Postback hasn't been sent yet — some advertisers batch conversions hourly. Check the advertiser's integration docs.