Transaction journey
Follow one click from the redirect to its conversions, their status history and every partner postback, by click ID, conversion ID or Google click ID.
Last updated 3 min read
On this page
The transaction journey answers the question "what happened to this click?" on one page: the click with every captured field, how it was redirected, the conversions attributed to it with their full status history, and every postback that fired for them with the request and the response.
Open a journey#
Any of these lead to /app/reports/transaction/<id>:
- Reporting → Transaction lookup (
/app/reports/transaction; search "Transaction lookup" or "journey" with Cmd-K). Paste an ID into "Click ID (32 hex), conversion ID or gclid / gbraid / wbraid" and submit. - The row menu Transaction journey in Clicks or Conversions.
- A direct URL with the ID.
Accepted IDs#
Where to find IDs: click IDs are in the click log, on conversion rows and in partner postbacks ({click_id}); Google
click IDs come from Google Ads.
Reading the page#
Flow#
A row of steps summarises the journey:
- Click — time, offer and affiliate.
- Redirect — the status (
redirect,fallback,blocked) and reason; highlighted when it was not a plain redirect. - Conversion · <event> — one step per conversion with its status; Duplicate when it is a duplicate. "No conversion for this click yet." when there is none.
- Postbacks — green when all were delivered, red when one failed, or "No postback fired."
Click#
The click card groups every stored field:
Conversions#
Each conversion shows its ID (with a copy button), event, status and reason, payout, revenue, sale amount and currency, the advertiser's transaction ID, the method (s2s, pixel, js, manual, api, import), the conversion IP and notes, plus a Status history built from the audit log: every approval, rejection, adjustment and who made it.
Postbacks#
Every outbound postback for those conversions with its state, attempts, a Test badge for test fires, and the Request (URL, method, body) and Response (HTTP status, first 500 characters, duration). Use it to prove to a partner exactly what was sent and what their server answered.
When nothing is found#
"Nothing found for this ID" means the click is not in this workspace's click log — raw clicks are kept 13 months — and no conversion references it. Check that you are in the right workspace and that the ID is complete.
Typical uses#
- A partner says a conversion is missing: look up their click ID. If the conversion exists, check its status and the postback response; if not, check the advertiser's postback log (Postback log → Received).
- A conversion looks suspicious: open it and read the click's fraud flags, IP, ASN and user agent, and the time between click and conversion.
- Google Ads offline conversions: paste a gclid to find which click and partner it belongs to.
Access#
Staff with report access (analyst and above). Partners and advertisers do not have this page.