Conversions event log
A walkthrough for the page at Events → Conversions. This screen is the raw, row-per-conversion record of everything Routy has attributed to your traffic. If someone asks "did this conversion arrive?", "why is my number different from the network's?", or "when did we actually get this?", this is the screen that answers it.
What this page is for
Every row is one conversion event — a signup, a deposit, a commission line — tied back to the click that produced it. Unlike the Report Builder, which aggregates, this page shows individual events exactly as Routy stored them.
Use it to:
- Confirm a specific conversion was received and attributed.
- Trace a conversion back to the click, link, and traffic source behind it.
- Understand when a conversion arrived versus when it happened.
- Spot conversions that landed late, or landed with the wrong type or value.
Date
The date the conversion happened, as reported by the affiliate program. This is the network's own timestamp — the moment the user deposited, signed up, or generated the commission.
This is the date almost every report and payout is based on. When you compare Routy against a network's dashboard, this is the field that should line up.
Click Date
When the click that led to this conversion happened. Hidden by default — turn it on from the columns button in the toolbar.
The gap between Click Date and Date is the conversion window: how long the user took to convert after clicking. A conversion dated days after its click is normal for deposits; one dated before its click means something is wrong with the attribution and is worth escalating.
Tracked
When Routy recorded the conversion. This is a different question from Date, and the distinction matters more than it first appears.
- For real-time postbacks, Tracked is seconds after Date. The two columns look redundant, and for these rows they effectively are.
- For conversions collected by integration (where Routy logs into the network and reads reports on a schedule), Tracked can be hours or days after Date. The conversion happened Monday; we learned about it Wednesday.
This is why both columns exist. When someone says "this conversion wasn't in my report yesterday but it is today", the answer is almost always visible in the gap between Date and Tracked — the conversion was backfilled by an integration run, not lost and re-found.
Tracked is shown as a relative time ("2 days ago"); hover it for the exact timestamp.
Not to be confused with the Age column on the Clicks event log. That one is simply the click's own date shown as elapsed time — it is not an ingestion timestamp. "Tracked" in the ingestion sense only exists here, on Conversions.
Reading the rest of the row
Columns can be shown, hidden, and reordered from the columns button in the toolbar; your layout is remembered per browser.
Calculated commissions
Commission reaches this page in two ways. CPA Commission, RevShare Commission and Earning are what the brand reported. Calculated CPA Commission, Calculated RevShare Commission and Calculated CPL Commission are Routy's estimate from your commission plan, for activity the brand didn't put a figure on. A calculated figure carries an Estimate marker.
When the two differ, the brand's figure is right: it allows for baselines, carry-over and later adjustments that an estimate can't know about.
Don't add them together
They are two measures of the same thing. To total commission, total each type on its own: filter Conversion Type to one type, or use the type column in an export. The same filter isolates or excludes the Calculated types.
A click with both
A click can have a CPA Commission and a Calculated CPA Commission. That is not a duplicate. A postback can report a qualification or first deposit with no commission, so Routy records an estimate straight away, and the brand's report brings its own figure later. A plan that pays both CPA and revenue share can also show a reported commission of one kind beside an estimate of the other.
Where an estimate comes from
- Integration: the brand's report for that day has no column for that commission.
- Postback: the postback reported a CPA qualification or a first deposit without a commission. This estimate uses the plan in force when the postback arrived, and editing the plan later doesn't change it.
Commission rows can appear on past dates, because estimates were also added for history. Until late October 2026, a CPA estimated from a postback was stored as plain CPA Commission, so on older conversions an estimate can look like the brand's figure. If one doesn't match the brand's portal, contact support with the conversion and the date.
Account mismatch
Sometimes a conversion is reported under one account but its click came through a tracking link that belongs to another. This usually happens when one login reaches several accounts (an Impact login with access to many advertisers is the common case), and a link created under one account, say Main, is used to send traffic to a brand you report under another, say FanDuel.
Routy still credits the conversion to the click. The row shows a yellow Link from Main marker beside the account, and hovering it names both accounts.
Why per-account numbers look off
The click and the conversion are counted under different accounts. Main shows a click that never converted, and FanDuel shows a conversion with no click. Neither account is wrong on its own; the pair is split across them.
How to fix it
Use a link that belongs to the account the brand reports under. In the example, send FanDuel traffic through a FanDuel link. New clicks then keep the click and the conversion on the same account. Conversions that already happened stay where they are.
Finding these conversions
- Filtering by either account shows the conversion, so it appears under FanDuel and under Main.
- Because of that, don't add up the totals of two separately filtered views: a mismatched conversion is in both. Filter by both accounts at once instead.
- Turn on the Link Owner Account column to see both accounts side by side.
Older conversions
Routy only started recording which account a conversion was reported under in July 2026. Coverage is complete from August 2026; for July it is partial, and for June 2026 and earlier it is almost absent. A conversion from before then shows no marker because Routy can't tell, not because the accounts match.
The marker also compares accounts only. A conversion through a link of the right account but the wrong brand is not flagged.
Common tasks
"I want to see the click behind this conversion"
Click the Click ID. This opens the Clicks event log filtered to that one click, with the date range set to an hour either side of the click, so the row is in view.
If you instead paste a click ID into the Clicks page by hand, remember that page defaults to the last 6 hours — an older click will show nothing until you widen the date filter yourself.
"My webhook never got this conversion"
Click the webhook button on the conversion's row (Why didn't this fire?). It lists every webhook that applies to the conversion, says whether each would be sent, and if not, why and how to fix it. See Why didn't my webhook fire?.
"My CPA webhook went quiet"
A webhook set to CPA Commission receives only the brand's figures. If it used to fire on postbacks, it was receiving Routy's estimates. Add Calculated CPA Commission to the webhook, or set it to send all types.
"Which traffic source does this conversion belong to?"
You have a click ID or a dynamic parameter value, often from a brand's own report, and want to know where the conversion came from.
- Set the date range to cover when the conversion happened. The page opens on the last 7 days; widen it if the conversion is older.
- Paste the value into the search box.
- Read the Traffic Source, Account and Link columns on the row that comes back.
Search accepts two things:
- A Routy click ID (36 characters, like
0192f3c4-…) finds that click's conversions. - Anything else is matched against the conversion's dynamic parameter, the per-click token the brand receives. Part of the value is enough, but capitals must match: paste it exactly as it appears.
Search looks at nothing else, so an account name, a Parameter A value or an External Click ID returns nothing here. If the value isn't found, look it up on Events → Clicks as well. A click with no conversion yet only shows there.
"I searched for a click ID and nothing came back"
A click ID search only looks inside the date range you have selected, and that range applies to the conversion's date, not the click's. A conversion can land days or weeks after its click, so don't go by when the click happened.
When a click ID finds nothing, the page tells you which dates it looked at and offers Search all time. That drops the date range, keeps your search and your other filters, and runs again. It can take a while, because it looks through your whole history. The date picker then reads All time. Pick a range, or clear the search, to go back to a bounded view.
The Click ID filter works the same way as pasting one into the search box.
If Search all time finds nothing either, Routy has no conversion for that click under the filters you have on.
"The network shows more conversions than Routy"
Check the Tracked column on the most recent rows. If the account is integration-collected rather than postback-driven, recent conversions may simply not have been picked up yet — the next integration run will backfill them. Compare the newest Tracked timestamp against the integration schedule for that account.
If Tracked is current and conversions are still missing, that's a genuine gap worth escalating.
"A conversion has the wrong value or type"
Note the Conversion Source. A value that came in via postback originates from the network's postback configuration; a value from integration was read off the network's report. These fail differently, and knowing which one you're looking at determines who can fix it.
To correct a single wrong amount yourself, use Edit value. That fixes this one conversion. If a whole account's values are off, the source needs fixing too, or new conversions will keep arriving wrong.
"I need conversions for one country"
Use the Country filter in the toolbar. It filters server-side across the whole result set, not just the rows currently loaded.
Filters
Every filter applies to all your conversions, not just the rows loaded on screen, and the filtered view is kept in the page address, so you can copy the URL and share it with a colleague.
Available: Account, Brand, Link, Traffic Source, Conversion Type, Affiliate Tracker, Country, Conversion Source (Postback or Integration) and Click ID. Clear all in the filter panel resets them.
The Click ID filter takes one or more Routy click IDs: paste one, press Enter (or Add filter), then paste the next.
The date range starts at the last 7 days and filters on Date (the conversion date), not Tracked. It applies to a click ID search too. Refresh reloads the list and, on a quick range such as "Last 7 Days", moves it forward to now.
Conversion details
Click … at the end of a row (or Show more on a phone) to open the conversion with the click behind it: the click's details, the visitor's device, the referrer, attribution, and every other event on the same click (its other Conversions, Incoming Postbacks, Outgoing Webhooks and User Page Views).
Edit value
When the value Routy recorded for a conversion is wrong — the brand reported a first deposit of 0 that was really 250, or adjusted a commission afterwards — you can correct that one conversion.
- Click the pencil at the end of the row (on a phone, expand the row and tap Edit value).
- The dialog shows the Recorded value and, if one is set, the Current override. Both are in the conversion's own currency.
- Enter the new value, in that same currency, and click Save.
The row then shows the new value marked Overridden. Hover the marker to see what was recorded.
To undo, open the dialog again and click Reset to recorded value.
What an override does:
- The recorded value is kept. The override replaces it on screen, in reports and in the postbacks Routy sends, but the original is never lost.
- Saving re-sends this conversion's postbacks and webhooks straight away, carrying the new value. Your traffic sources receive the conversion a second time. Every save re-sends, so saving the same value twice sends it twice.
- Reports catch up within about half an hour. Until then the list can show the old value after a refresh. The row you just edited keeps showing the saved value while you stay on the page.
Things to know:
- Only money values (deposits, commissions, revenue) can be edited. Counts such as sign-ups show no pencil.
- Only the latest override is kept. There is no history of earlier overrides, and Routy doesn't record who set one.
- The Overridden marker only appears on rows you edited in this visit, or whose dialog you opened. An override set earlier or by a colleague shows as the plain value until you open its dialog.
- Account-level daily totals can ignore an override. For a day where the brand's own report supplies the account's totals, those totals are shown instead of the sum of tracked conversions. This list, and per-conversion reports, always show the override.
- Account managers can edit conversions of any affiliate in their book.
- "This conversion is no longer available" means the conversion no longer exists or belongs to an affiliate you can't reach.
Export
The Export button (download icon) offers:
- Export these results: a CSV of every conversion matching your filters and date range, whichever columns you have showing. Very large results are capped, and you are told how many rows were included.
- Download loaded rows (CSV): just the rows already on screen, in the columns you have showing.
- Full export, runs in the background: every conversion over a date range. It needs a plan that includes data exports.
Things to know
- The page loads incrementally as you scroll rather than in numbered pages.
- Values marked with
*arrived with no currency, so they are shown in the account's default currency. - In exports, the account columns are the reported account, followed
by
link_account_id,link_accountandaccount_mismatch.
When to escalate to engineering
Escalate when:
- A conversion exists on the network's dashboard but never appears here, and the account's integration has run since (check Tracked on neighbouring rows).
- A conversion's Click Date is after its Date.
- A conversion has no Click ID at all, or a Click ID that opens an empty Clicks view even with a wide date range.
- Values are systematically wrong for one account — a single odd row is usually network-side, a whole account is usually ours.
Include the Click ID and the conversion Date in the ticket; those two together are enough to find the record.