Home/Docs/Conversions
Docs

Conversions

Track every conversion in a live stream, triage holds, and act on fraud-flagged events from one workspace surface.

What "Conversions" means in Trcker

A conversion is any qualifying event your partners drove that you've agreed to pay for — a sale, signup, lead, install, or any custom event you've configured. Every conversion in Trcker is the result of a click on one of your tracking links, attributed to the partner who owned that click.

Conversions land in one of four statuses:

| Status | Why it ends up here | |---|---| | Approved | Default. Clean fraud check, the offer's hold period (if any) has elapsed. Partner is credited. | | Pending review | Your fraud mode is set to Flag and Radar scored the click above your threshold. Waiting on your operator decision. | | Hold | The offer has a configured hold period (e.g., 72h refund window). Auto-approves when the clock runs out. | | Rejected | Either manually rejected from the holds queue, or auto-rejected because your fraud mode is Auto-reject and Radar flagged the click. |

The Conversions page

The Conversions tab on each brand workspace ships three surfaces stacked top-to-bottom:

  1. KPI strip — Conversions count · Approved · Holds · Revenue for the active date range.
  2. Holds queue — Conversions that need your attention. Both pending review (fraud-flagged) and hold (offer-configured) rows appear here. Fraud-flagged rows get a colored severity chip (critical / high / medium) based on Radar's score; offer-hold rows get a quiet "Hold period" label.
  3. Live stream — The 50 newest conversions matching your active filters. Updates every 15 seconds.

Triaging holds

When the holds queue is non-empty:

  1. Check the rows you want to act on (or use the header checkbox to select all).
  2. Click Approve N or Reject N in the section header.
  3. The action posts immediately; the rows disappear from the queue once the API confirms.

Clicking any row (in either Holds or the Live stream) opens a right-rail with:

  • KPIs (revenue, payout, profit)
  • Attribution (partner + offer trail — both linked)
  • Sub IDs (sub1 through sub5)
  • Click context (IP, country, user-agent, holdout/test flags)
  • Fraud signal breakdown (when present)
  • The raw postback payload your advertiser sent

For holds rows, the rail's footer surfaces single-row Approve / Reject buttons — convenient when you want the full context before deciding.

Filters

Four filter chips drive the Live stream:

  • Offer — multi-select; restrict to specific offers.
  • Partner — multi-select; restrict to specific partners.
  • Status — multi-select; choose from Approved / Holds / Rejected.
  • Range — single-select; choose from the last 24 hours, 7 days, 30 days, or all time. Default is 30 days.

Filters live in the URL — share or bookmark a filtered view and reopen it later.

Export CSV

The Export CSV button (top-right of the page) downloads whatever's currently visible in the Live stream — same filters applied. Useful for ad-hoc analysis or sharing with a finance team.

How conversions get into Trcker

  1. A partner sends a visitor through their tracking link.
  2. Trcker captures the click and redirects to your destination.
  3. Your platform fires a postback when the visitor converts (configured per offer — see Setting up postbacks).
  4. Trcker validates the postback, checks fraud signals, and inserts the conversion at the correct status.

If you're not seeing conversions you expected, the most common causes are: (a) postback URL not configured on your platform, (b) postback firing without the clickId macro, (c) fraud mode set to Auto-reject and Radar caught it. The Setting up postbacks doc walks through the full setup; the Fraud detection doc explains how to tune your thresholds.

Related