Fraud, fail traffic and conversion quality reports
See which fraud signals the edge recorded on clicks, where fallback and blocked traffic went, and how fast and how cleanly conversions arrive.
Last updated 4 min read
On this page
Two pages cover traffic quality:
- Reporting → Fraud & fail traffic (
/app/reports/fraud) — click-level fraud signals and traffic that fell back or was refused. - Reporting → Conversion quality (
/app/reports/quality) — click-to-conversion time (CTIT), fraud-rule hits on conversions and status reasons.
Both use the date range in the top bar and exclude signed compliance-probe clicks. Fraud signals are recorded only: they never change where a link redirects.
Fraud signals tab#
KPI cards: Clicks, Flagged (share of clicks with at least one signal), Bots and Rejected / fallback (share of clicks that did not plainly redirect). Most frequent signals lists the signals with their counts.
The table groups clicks by one dimension — Affiliate, Offer, Country, Source ID, Sub 1 or Traffic source — sorted by flagged clicks, with Clicks, Flagged, Rejected / fallback and one count per signal.
Signals#
The two conversion signals are set by the conversion engine when a conversion arrives (they are stored on the conversion, never on the click). The report counts them on the conversions of the selected period, by conversion time, in the same groups; they are not part of Flagged, which counts clicks. A conversion request cannot set them itself.
Hover a signal name in the panel for its description. A click's individual flags are listed in Click details.
Fallback & blocked tab#
KPI cards: Fail traffic (of all clicks), Fallback ("Affiliate links that went to the fallback URL (paused offer, not approved, targeting, caps).") and Blocked (4xx) ("Transparent links refused without a redirect (not on the allowlist, invalid url=…).").
A breakdown by reason, then a table with Outcome (fallback or blocked), Reason, Sent to (the
destination host, or "(neutral page)" when no fallback URL was configured), Clicks, Offers and Affiliates
(top 300 combinations). Reason codes are explained in Error and reason codes.
Use it to find partners still sending traffic to paused offers, offers whose caps run out early, or transparent links pointing at destinations that are not on the allowlist.
Conversion quality#
Click-to-conversion time#
KPI cards: Attributed conversions, Average CTIT, Median CTIT and Under 15 seconds — "Conversions within 15 s of the click — often bots or click injection. Set a minimum CTIT on the offer to reject them."
The chart buckets conversions into 0–15 s, 15–60 s, 1–10 min, 10–60 min, 1–24 h, 1–7 d and > 7 d. The tables By offer and By partner show Conversions, Avg CTIT and Median per row. Only conversions with a click are counted.
Fraud#
Conversions caught by the fraud rules under Settings → Conversion rules (status reason fraud:<check>):
Rejected by fraud rules, Flagged only (rules set to flag keep the conversion's status) and Partners
affected, a Hits by check chart, and a table per check and partner with Rejected, Flagged only and
Payout not paid.
Status reasons#
Approved, pending and rejected conversions grouped by status reason (for example duplicate, outside_window,
cap_exceeded, too_fast, hold, manual) with Conversions, Payout and Revenue.