Reports and logs overview
Use reports to investigate traffic and recorded screening outcomes. Use delivery and server logs to troubleshoot requests. A rejection is a recorded decision, not independent proof of fraud; a non-rejected record is not necessarily approved for payment.
Statistics documentation
Section titled “Statistics documentation”| Task | Guide |
|---|---|
| Compare grouped totals | Overview reports |
| Inspect individual clicks | Click reports |
| Inspect conversions and event fields | Conversion reports |
| Investigate a grouped row | Traffic insights |
| Troubleshoot outbound HTTP delivery | Postback logs |
| Inspect inbound request handling | Server logs |
| Share a filtered report | Shared reports |
| Export selected fields | Export reports |
| Retrieve queued exports | Download center |
| Screen historical conversion records | Bulk conversion import |
Investigation example
Section titled “Investigation example”All examples and screenshots in these guides are illustrative, using fictional Northwind and Blue Harbor records and invented counts, not measured customer incidents. Start with a publisher in Overview, open its Traffic Insights, then compare filtered click or conversion rows. Check filter group matching before interpreting the recorded reasons. Keep delivery failures separate from traffic-quality conclusions.