About Reports and Logs

Reports and Logs is where you find out what happened. The difference between the two is the level you are working at.

  • Reports aggregate. A row is a day, an affiliate, an offer, a channel. They answer how many and for how much.
  • Logs are one row per event. A click, a lead, a conversion, a request. They answer why this particular one did what it did.

Most questions start in a report and end in a log.

The reports

  • Performance: results over time, and the same data grouped by affiliate, advertiser, or offer. This is where you look at profit, costs, revenues, and the per lead and per click metrics.
  • Pingtree: how leads moved through distribution, per offer and per channel. Pings, verifications, posts, and what each channel paid.
  • Transactions: every transaction as its own row, both sides of it, with the identifiers and the detail behind each one.

The logs

  • Clicks and leads: what arrived, whether it was accepted, and what happened to it afterwards.
  • Conversions: every conversion PalDock holds and whether it produced a transaction. This is where you go when a conversion exists but no payout came out of it.
  • Integration requests: each run of an integration, node by node, with what was sent and what came back.
  • Tracking requests: every pixel, postback, and Tracking API call, and how each was handled.

All of them are described in Logs.

What every table shares

Reports and logs are the same kind of table, so the same tools apply to all of them.

  • Period and granularity: a date picker with the usual presets, and a choice of hours, days, weeks, or months.
  • Highlights: the key numbers above the table, and the lines in the chart. Rows can be plotted instead. See Show rows in chart.
  • Advanced columns: which columns are on screen, from a fixed set of groups.
  • Filters: including filtering by columns you are not displaying.
  • Result type filter: whether pending and rejected transactions are counted.
  • Reporting time basis: which of the three dates a transaction is reported on.
  • Export and Import.

The last two are worth knowing before you compare numbers with anybody. Two people looking at the same data on a different time basis or a different result filter will get different totals, and both are correct.

Who sees what

Affiliates and advertisers open the same reports you do, restricted to their own data. Columns that belong to the other side are hidden or relabelled, and an affiliate is never shown which channel bought a lead. See Transactions report.

Individual report functions can also be limited by role, from adding a Highlight to exporting.

Where to start

  • Which affiliate is performing best: performance report, grouped by affiliate.
  • Why leads are not selling: pingtree report, then the lead log.
  • Why this lead was rejected: lead log, read the status, then the detail.
  • Why there is no payout for this conversion: conversion log, then How PalDock picks a commission.
  • Why the advertiser’s postback did nothing: tracking log, then Tracking errors and reasons.

Insights that
helps you grow

  • Release notes 2026/08/14
    This was a big one. We went through roughly 200 pages of our knowledge base and rewrote the whole thing. Clearer structure, consistent terminology, and…
  • Release notes 2026/07/31
    What’s new in PalDock? A lot of this month went into things you won’t see directly – query optimisation, indexing, and general tuning under the…
  • Free Affiliate tracking software
    Many companies (inlcuding YOU) search for free affiliate tracking software because they want to launch an affiliate program without committing to expensive monthly fees. The…