Affiliate Reporting: Check Filter Scope Before Comparing Campaign Totals

Two affiliate reports can use the same date range and currency yet describe different populations. One may include only approved orders, another may exclude a traffic source, and a saved dashboard view may retain a country filter from an earlier investigation. Comparing their totals without checking that scope can turn a reporting difference into a false performance story.

This proposed reconciliation routine is designed for performance marketing media buying teams working with ecommerce CPS or virtual-product campaigns. It does not require a particular reporting platform or assume that every export exposes the same controls.

Write down the population behind the number

Before interpreting a total, record the included accounts, offers, countries, traffic sources and conversion statuses. Add the time zone, date field, currency and export time. These details define what the report can answer. A conversion-date report and an approval-date report may contain different orders even when their date pickers match.

Record exclusions as explicitly as inclusions. “All sources except internal tests” provides more information than “all traffic.” If the system does not expose a filter or its default value, mark that part of the scope as unknown.

Use one controlled comparison

Start from a baseline export with a documented scope. Change one filter and export again, keeping the other settings fixed. Compare both row counts and the relevant amount. Use the appropriate stable record identifier where one exists; do not assume that a display name uniquely identifies an order.

In a hypothetical example, a baseline report contains 120 eligible records. Applying a country filter leaves 85, excluding 35 records. The smaller count is expected from the narrower population. It is not evidence that 35 conversions disappeared from the underlying account. Revenue reconciliation still requires the actual amounts on those excluded records.

Check whether the screen and export share a scope

Some workflows offer several export routes, so test the route the team actually uses. Inspect whether the file reflects the current filters, a broader report or only selected rows. Read the report labels and documentation, then confirm the result using a known sample. Do not infer export behavior from the appearance of a filtered screen.

Also distinguish filtered detail from a summary tile. If the product does not explain whether a filter affects both, avoid using them as interchangeable checks until the scope is established.

Make scope visible at the handoff

• Attach a short scope note to the exported file.
• Keep the original export before editing or filtering rows locally.
• List any spreadsheet exclusions added after download.
• Record the rule used to handle pending and adjusted transactions.
• Require matching populations before comparing campaign performance.

Teams coordinating with advertisers can use the scope note to ask a precise reconciliation question: which records are included on one side and excluded on the other? This is more actionable than asking why two dashboard totals disagree.

Once scope matches, investigate any remaining differences in timing, amounts and record handling. A filter audit does not prove that a campaign is profitable or that tracking is complete. It establishes whether the numbers being compared refer to the same intended population.