LLighter
RUEN Turn it on
Docs › Conversions
Analytics

Conversions

This is the screen where the web finally sees the money — one lead at a time. Reports fold everything into pretty numbers; Conversions show the raw material those numbers are built from: every postback, every payout, every status, every UTM tail. You come here to check the till, debug an integration, or work out why a lead went to trash. Newest on top. We count exactly what the classic interface counts — down to the last lead.

One screen, one job. Reports answer “how much in total.” Conversions answer “this one specific lead — what happened to it?” Want aggregates? That's Reports.

What's on the screen

The raw lead stream: newest first, 50 per page, counts identical to classic.

A dense table, newest leads on top, 50 per page, default sort newest-first (lead_id descending). The toolbar up top:

Default columns

Out of the box we show 13 columns (classic parity):

Time · Campaign · Stream · Landing · Status · Country · Payout · utm_source · utm_campaign · utm_content · utm_term · utm_medium · Domain · SubID.

The “Campaign” column shows the human name (e.g. “Premium Cat Food”) but click-filters by the campaign's hex code — that's intended: the name is for your eyes, the hex is for the machine.
«Campaign», «Stream», «Landing» are the words you're used to. In the real AlterCPA Lite the same objects are called поток, путь and сайт; settle in and you'll switch to them. The subtlety everyone trips on is the Russian word «поток»: in AlterCPA Lite it's the top object (shown here as Campaign), while the familiar «поток» is a branch (shown as Stream; AlterCPA Lite calls it «путь»). One word, two floors.

Columns popover

21 columns in four groups, 13 on by default. Status pills come from the number, not the string.

21 columns total, 13 on by default. Columns are sorted into four groups — Lead · Money · Tags · Debug. Optional extras: the info button, user (team), Goal, IP, Custom, Cost, Customer (utmu), Name · Phone · Email · Comment. Your chosen set is saved server-side (pref.ui.cols.conversions) and survives a full reload.

Column headers are click-to-sort — a click refetches from the server (sorting is server-side, not in the browser).

Workflow 1 — Filter the leads

~20 filter keys. Clicking a cell adds a condition to the query.
  1. Set the date range. Pick a period up top (or keep the 7-day preset).
  2. Click a status segment: All · New · Hold · Approve · Cancel · Trash. Approve, say, leaves only the approved ones, and the footer count updates.
  3. Add finer conditions. Open + Filter and add keys: geo, ip, click, goal, any tag (utm_*, subid, customer, domain). Each condition becomes a chip.
  4. Filter straight from the table. Clicking a value in any cell adds it to the query. Click google in utm_source and you get the filter “utm_source = google”.
  5. Start over. Clear the chips or hit Reset filters.
Clicking the “Status” cell FILTERS — it does not change the status. Click “Approve” and you filter the list to approved leads. The lead's own status stays put. You don't get to decide a lead is approved just by clicking it, kitten. Status is driven by the postback, not your mouse.

Workflow 2 — Inspect a single lead

The full lead record: parsed UA, meta, tags, payout. Read-only — Close is the only button.
  1. Open the lead details. Click the lead's row (the row itself, not a link value) — the “Lead details #NNN” modal opens.
  2. Read the full record. Inside: click code and UID (both clickable), geo and IP, UA with parsed browser and OS, the meta object, adid, data1..5, tags and customer, payout, cost, goal.
  3. Open the “Status history” tab. A read-only timeline: time · old → new status · price · cost. Statuses are drawn as pills from the numeric status.
  4. Close it. Close only. The modal is read-only.
The lead's diary: time · old → new status · price · cost. A chronicle, not a control panel.
Status history is the lead's diary: you can see it walk New → Hold → Approve and how the money moved with it. Nothing to edit — it's a chronicle, not a control panel.
v1 has no manual “approve / cancel.” Status changes only through postback ingestion. There is no “make it approved” button — and that's not a bug, it's a stance: the till reflects reality, not your mood.

Workflow 3 — Export to CSV

  1. Dial in your selection and columns. Range, status, filters and the columns you want — the export dumps what's visible.
  2. Hit “Export CSV”.
  3. Get the file. In it: status as a machine code (ca/cc/…, not the localized pill), money raw (with its currency), campaign as the human name, geo uppercased. Headers are localized, and the file carries a UTF-8 BOM so Excel doesn't mangle Cyrillic.
CSV is for spreadsheets and accounting, so status ships as a machine code: ca reads fine to a human and a machine, and doesn't break when someone flips the UI language.

Good to know (the gotchas)

On a narrow screen a lead collapses into a labelled card with a colored status pill.

Coming from an old tracker

This is your familiar conversions screen — the same raw lead stream, just labelled in plain words. Used to eyeball every conversion one by one? The habit carries over.