Metrics & counting rules
If your numbers don’t match your traffic source or your network, the answer is almost always on this page.
How a visit is recorded
Roitrack writes one row per event, not one row per visitor:
| Event | What creates it |
|---|---|
| Visit | Someone hits your campaign link |
| Lander click | A visitor clicks the CTA on a hosted lander |
| Conversion | Your network fires the S2S postback |
A visitor who lands, clicks through, and converts produces three rows. This matters because it explains why the raw row count is never the number you want, and why each metric filters differently.
What each metric counts
| Metric | Counted as |
|---|---|
| Clicks | Visits only — lander clicks and postbacks excluded |
| LP views | Unique visits that landed on a lander (direct-to-offer traffic excluded) |
| LP clicks | CTA clicks on a lander |
| LP CTR | LP clicks ÷ LP views |
| LP Loaded% | Measured lander views ÷ LP views |
| LP Visible% | Measured views that were ever on screen ÷ measured views |
| LP Scroll% | Mean furthest scroll depth, averaged over visible views only |
| LP Measured | Lander views that reported back, weighted by the sampling rate |
| Conversions | Rows flagged as a conversion by the postback |
| Revenue | Sum of payout across conversions |
| Cost | Sum of cost across visits |
| CVR | Conversions ÷ clicks |
| EPC | Revenue ÷ clicks |
| ROI | (Revenue − cost) ÷ cost |
| Profit | Revenue − cost |
Direct-to-offer traffic has no lander, so LP views, LP clicks and LP CTR are all zero for those campaigns. That’s correct, not a bug.
Click mode vs performance mode
This is the setting most likely to make two reports of “the same” data disagree, and it exists because a conversion happens later than the click that produced it.
- Click mode (default) buckets everything by when the click happened. A conversion that arrives today for yesterday’s click is reported yesterday.
- Performance mode buckets conversions by when the conversion happened. That same conversion is reported today.
Neither is wrong; they answer different questions.
Use click mode to judge traffic quality — “of the clicks I bought on Tuesday, how many converted?” This is the number that tells you whether a placement is worth keeping, and it’s the one to compare against your own spend.
Use performance mode to reconcile with your network — “how much revenue landed on Tuesday?” Networks report by conversion time, so this is the mode that matches their invoice.
Uniqueness
A returning visitor inside the uniqueness window counts as a repeat rather than a new unique. The window is configurable in Settings → Performance, separately for visits and for lander clicks. Raising it makes uniqueness stricter across longer sessions; lowering it counts more returns as new.
Changing the window doesn’t rewrite history — it applies from that point on.
Reporting tools
- Grouping and drill-down — group by campaign, flow, offer, lander, country, device, OS, browser, traffic source, or any of your sub IDs, then drill into a row without losing the filters above it.
- Custom columns let you define your own calculated metrics from existing ones.
- Column presets save a set of visible columns and their order, per report.
- Saved filters store a filter set you use often.
- Events 1–10 are extra counters your network can populate through the postback — upsells, rebills, whatever you map them to. See Postbacks & conversions.
Why your numbers differ from the network’s
Ranked by how often it’s actually the cause:
- Mode mismatch. You’re in click mode, they report by conversion time. Switch to performance mode before concluding anything.
- Timezone. Reports render in the timezone you select. If the network reports in UTC and you’re on Europe/Moscow, days boundaries differ by three hours and every daily total near a boundary looks wrong.
- Postbacks that never arrived. A conversion the network recorded but never fired to you doesn’t exist in Roitrack. Check Postbacks & conversions.
- Rejected or reversed conversions. If the network reverses a conversion without firing an update, Roitrack keeps counting it.
- A few seconds of lag. Aggregated totals are eventually consistent and can trail live data briefly. If two views of the same range differ by a handful of clicks and reconcile a moment later, that’s this — not lost data.
Why your numbers differ from your traffic source’s
Almost always tracking loss rather than a reporting bug: bots and scanners filtered on the way in, visitors who abandoned before the redirect completed, and ad-blockers. A gap in the low single-digit percent is normal. A gap above roughly 10% is worth investigating — start with Common issues.
You do not have to estimate this. If your network has an API Roitrack can read, Automation measures the gap per zone against the network’s own figures and gives you two more columns: Zone Loss%, the share of billed clicks that never arrived, and Network Cost, what the network says the zone cost. Both are blank where nothing has been measured — a zone nobody has checked and a zone that loses nothing are different facts.
Totals
The TOTAL row is computed over the whole report, not the page you are looking at, and it is summed before anything is rounded. A grouping with hundreds of small rows adds up to the same figure as the same data grouped by day.
If a grouping spans more than one page, the footer still reports every row. The one exception is a mark filter, which is applied in your browser: with one active the footer describes what is on screen and says so.
Choosing columns
Settings → Columns decides which columns each screen shows and in what order. Pick the screen along the top — Campaigns, Analytics, Offers, Networks, Traffic sources, Landers — and each keeps its own list.
Visibility is per screen. Custom columns are not: a formula you write is available everywhere, and you choose separately where it appears.
The list is a working list rather than a form:
- Click a row to select it, and shift-click another to select everything between. ⌘ or Ctrl adds and removes one at a time.
- Drag any selected row and the whole selection moves with it, keeping its own order whether or not the rows were next to each other. The list opens up as you drag so you can see where the block is going to land.
- Shift-click a checkbox to show or hide the whole run in one go.
A column added to Roitrack after you first opened a screen stays hidden until you turn it on here. That is deliberate: a new column appearing in the middle of a report you had arranged is worse than one you have to go and find.