Routy

Incoming postbacks

This screen answers one question: did the postbacks a network sent us turn into conversions?

A postback is a server-to-server call a network makes when one of a publisher's referrals converts. It is fire-and-forget from the sender's side — they configure a URL, the network calls it, and nothing tells them whether we received it, understood it, or matched it to a click. This screen is where you look instead of querying the database.

Outcome

Every postback has exactly one outcome, and it is the first column.

Outcome What it means What to do
Processed We matched it to a click and created the conversion(s). Nothing.
Not matched We received it but could not find the click it refers to. This is the actionable one — see below.
Pending Received, not processed yet. Normal for a few seconds. Nothing, unless it stays.
Stuck Still unprocessed more than 15 minutes after we recorded it. Escalate — processing is behind or has stopped.

Not matched is not final. Unmatched postbacks are retried in the background, so a row can become Processed on its own with nobody doing anything. Do not tell a publisher a conversion is lost on the strength of one Not matched row.

Reading a "Not matched" row

Almost always the sub-ID the network sent does not match the one in the tracking link. Check the Sub-ID column against the link the publisher is actually using.

An unmatched postback has no account, brand or traffic source either — we cannot attribute it until we know which click it belongs to, so those columns are empty by definition. The emptiness is the finding, not missing data. Group by Sub-ID instead: "300 postbacks on this sub-ID, none matched" is the shape of the diagnosis.

Scope

The counts and the list both cover the date range shown in the header, and the date range is the scope of every number on the screen. The default is the last 24 hours.

Leaving the Affiliate filter empty means every affiliate. Pick one or several to narrow. Account managers see the affiliates they manage.

Counts

The cards above the table count postbacks per outcome over the selected range, so "they sent 300 and 290 did not match" is visible without scrolling. Clicking a card filters the list to that outcome; clicking it again clears it. The counts themselves never change when you click — they always show the full breakdown, so you can see the distribution while looking at one slice of it.

Opening the publisher's own view

The arrow at the end of each row opens that affiliate's own postbacks page in a new tab, as they see it, with the row's sub-ID already searched. Use it to confirm what the publisher is looking at before replying to them.

When to escalate to engineering

  • Stuck rows in any quantity — processing is behind, which is not a configuration problem.
  • Postbacks the network insists it sent that do not appear here at all, over a range where other postbacks for the same affiliate do appear.
  • A row that stays Not matched across several hours while the sub-ID visibly matches the tracking link.