Report Columns — Mapping Your Account's Reports
This screen lets you see and adjust how the columns in your account's report are understood by Routy. It lives on your account under Column Mapping.
What this screen is for
When you connect an affiliate account, Routy pulls that account's report — a table with columns like Registrations, NGR, or FTD Count. For Routy to turn those numbers into stats, each column has to be mapped to a Routy concept (Signups, Net Revenue, First-Time Deposits, a Date, a Brand, and so on).
This screen shows one row per column that actually appears in your report — your real columns, nothing else. For each one you can see what it's mapped to and change it if it's wrong.
A mapping takes two steps: you change it, then you approve it. A changed column is paused until you approve it — which is what lets you check the result first, and what to watch out for if you change something and leave it. See Status and Preview below.
How to read the screen
Each row shows:
- The column name exactly as it appears in your report.
- What it's mapped to right now — or not mapped yet if Routy doesn't know what it is.
- Its status — whether the mapping is actually being used. See Status below.
- A suggestion, when Routy recognizes the column name from a template. You can accept the suggestion in one click.
- Badges that tell you more about the mapping (see below).
Badges you'll see
- A type badge (e.g. Net Revenue, Date) — what the column is mapped to.
- A blue "Month only" / "Day, Month" badge — this mapping is limited to specific report types (see Applies to reports below). No badge means it applies to every report.
Mapping a column
- Find the column you want to fix.
- Pick the right type from the type dropdown, or click Accept on a suggestion if one is shown.
- Fill in the format box if the column needs one — what it asks for depends on the type you picked. See below.
- Click Preview to see what your reports look like with the change.
- Click Approve on the row to make it count.
Your change saves for this account only.
Whose mapping is it
Every column is mapped either by Routy — inherited from your program or software, and shared with other accounts — or by your account, because somebody here changed it.
The Source badge on each row tells you which: Software or Program means Routy's, Account means yours.
Most rows are Routy's, and those have nothing under the field — that's the resting state, and there is nothing on them for you to approve or undo. A row you own shows its controls under the field, and if it's paused it says so there too.
Changing a mapping pauses the column
This is the thing most worth knowing on this screen. Any change you make becomes a draft — picking a field, accepting a suggestion, editing a format, condition or formula. You don't choose this; it's what lets you check a change before it counts.
A draft is not "the old mapping carries on while the new one waits" — the column is paused. From the next report collected, it contributes nothing at all until you approve it. So if you open a column that was working, change it and walk away, that column stops being counted. Reports already collected are not affected.
A draft gives you two answers, both under the field:
- Approve — start counting your change.
- Undo — drop your change.
While any column is paused, a note at the top of the screen says how many.
Approving applies to reports collected from then on. To apply it to figures you've already got, use Re-run and pick the dates — see below.
Undo
Undo is on every draft your account owns. It removes your mapping for that column, and what happens next depends on what Routy has for it:
- Routy has a mapping for that column — the column uses it again, counting from the next report. That's the usual case: your first change to a column Routy had mapped didn't overwrite Routy's mapping, it made a copy for your account, and undo deletes the copy.
- Routy has no mapping for it — the column is left unmapped, and you can map it again whenever you like.
The confirmation tells you which of the two you're getting.
Two things worth knowing:
- It's permanent. There's no undoing the undo, and no list of what was removed.
- It removes your mapping, it doesn't step back one edit. If your account had already set its own mapping for that column before your latest change, undo goes to Routy's mapping, not back to your earlier one.
Undo doesn't change figures already built, exactly like approving doesn't — see Re-run below if you need those dates recounted.
Preview
Preview shows what your stored reports look like read through the mappings as they stand right now, drafts included. It is the only place a draft shows its effect, so it's the step between changing a mapping and approving it.
Pick a report type and a range of report dates (up to 31 days), then Run preview. Nothing is collected from your affiliate program and nothing is saved, so you can run it as often as you like while you get a mapping right.
Reading the result:
- The table shows a sample — "Showing 50 of 412 rows" means there are more. Show more fetches a bigger sample.
- Columns appear only if they produced a value in the rows shown. Anything mapped that produced nothing is listed above the table, so a column you just mapped is never silently missing.
- If there are no rows at all, the screen says which of two things happened: no report is stored for those dates and that report type, or reports are stored but your current mappings produce nothing from them. The second one means the mapping still needs work.
When the sample is chosen rather than the first rows
Some affiliate programs report one row per click. A single day on an account like that can be 130,000 rows of which only a hundred carry a signup or a deposit — so the first fifty rows of the day are fifty clicks that did nothing, and a preview built from them looks like a day on which nothing happened.
On a report that big the preview picks its rows instead: every row that carries something — a signup, a deposit, a commission — plus a couple of hundred of the click-only rows as evidence that the rest are there. The line above the table says so, and names both counts:
Showing 200 of 129,900 click-only rows, and all 100 rows with activity. This range is 130,000 rows — the click-only rows are a sample.
- The click-only rows are the greyed ones, each marked with a small pointer icon. Tick Rows with activity only to hide them and see just the rows your mapping is meant to change.
- The rows stay in report order, so the chosen rows are mixed in where they actually appear rather than grouped together.
- Nothing you need is missing. The rows held back are the ones that carry nothing, and the same window previewed twice gives you the same rows — so the table doesn't shuffle while you work on a mapping.
- Show more disappears here, because a bigger sample size doesn't change what comes back: every row with activity is already in the table.
Very occasionally a range holds more rows with activity than a preview can return. That is real data left out rather than clicks held back, so it gets its own warning above the table — pick a shorter range and run it again.
This is about what the preview shows you. It says nothing about which reports are stored or how your figures are counted.
Re-run
Approving a mapping decides what Routy does with reports from then on. It doesn't go back over figures that were already built — those still carry the mapping that was approved at the time. Re-run is how you bring them up to date.
Click Re-run, pick the report dates you want recounted, and queue it. Routy reads the reports it already collected for those dates and rebuilds your figures from them through the mappings as they stand approved now.
- Report dates are the dates on the report, not the day it was collected. The quick buttons cover since yesterday, last 7 days, last 30 days, month to date and previous month; any other range is a few clicks in the calendar.
- Report types starts with all of them selected. Leave it that way unless you know which report your change affects — a type you leave out keeps its old figures, and a type with nothing stored for those dates simply does nothing.
- It runs in the background. The task appears on the account's Integration tab, so that's where to watch it finish and where a failure shows up.
Two things it does not do. It never fetches anything new from your affiliate program — that's Queue extraction on the Integration tab, and you want it when the reports themselves are missing rather than when a mapping changed. And it won't apply a draft: a transform resolves approved mappings only, so approve the change first, then re-run.
Figures move once the task completes, which depends on how many days and report types you asked for.
Format
The format box asks for a different thing depending on the column's type:
- Date columns — the pattern the report writes dates in, e.g.
dd/MM/yyyy. A date column can't be read without one. - Everything else — an optional extract pattern that pulls the part you
want out of a longer value. A campaign column reading
BRAND_DEALwhen all you need is the brand is the usual case.
An extract pattern is a regular expression. Put the part you want in round brackets; with no brackets, whatever the pattern matched is used.
Use the test box beneath the field to check it: paste a real value from the report and the screen shows what the pattern would pull out of it. If it shows no result, the pattern didn't match that value — check whether every row really follows the shape you assumed.
Ignoring a column
Some columns exist in a report but shouldn't be used — a running total your network adds, a duplicate of a column you already map, a note field. To leave one out, map it to None (ignore this column).
None is a decision, and it is different from not mapped yet:
That override is the point. Types are usually set once on the software or program, and every account under it inherits them. When one account reports the same column name with something you don't want counted, setting it to None on that account switches it off there without changing anything for the others.
Setting a column back to a real type at any time undoes this.
Applies to reports
Some accounts send more than one report for the same data — for example a per-click report and a monthly-summary report. Once in a while the same column name means different things depending on which report it came from.
The "Applies to reports" control (in the advanced settings for a column) lets you limit a mapping to specific report types:
- Leave it empty to apply the mapping to every report type. This is the right choice almost all of the time.
- Pick one or more report types (Click, Day, Tracker, Brand, Month, Customer) to limit the mapping to just those. The column then shows a badge like "Month only". Customer covers per-player activity and only appears for integrations that collect it.
You only need this in the rare case where one column name genuinely means different things on different reports. If you're not sure, leave it empty.
Common questions
"I changed a mapping and the column stopped counting."
That's the pause described under Whose mapping is it — a changed column is a draft, and a draft isn't counted. Approve it to start counting your change, or Undo to drop it.
"I changed a mapping and my numbers didn't change."
Look under the field. Draft · not counted means the mapping is paused, not applied — click Approve. If it's already approved, the figures you're looking at were built before your change, and approving doesn't go back over them: use Re-run and pick the dates you want recounted. If a re-run doesn't move them either, check "Applies to reports" — a mapping limited to Month only won't be used on a Day report.
"A column says not mapped yet — is that a problem?"
It means Routy doesn't yet know what that column is, so its data isn't being used. Map it to the correct type to start counting it.
"Why is a column ignored when I never touched it?"
Because None is inherited like any other setting. If the column is set to None on the program or the software, every account underneath skips it. Map it to a real type on your account to override that.
"I mapped a column but it didn't seem to apply to a report."
Check the "Applies to reports" setting. If the mapping is limited to, say, Month only, it won't be used on a Day report. Clear the setting to apply it everywhere.
"I don't recognize the suggested type."
You can ignore the suggestion and pick the type you know is correct, or contact support if you're unsure.
When to contact support
- A column's data still isn't showing up after you've approved it and the mapping isn't limited to another report type.
- A Re-run finishes but the figures for those dates still look wrong, or the task fails on the Integration tab.
- You need figures rebuilt for dates whose reports Routy no longer has.
- The type you need doesn't appear in the dropdown.
- You see the same column with conflicting mappings and aren't sure which is right.