01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 click conversions <click-id>02What you get
Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.
$ p202 click conversions 2871 amount conv_id conv_time counts event_name linked_to source transaction_id ------ ------- ---------- ------- ---------- -------------------------- ------ -------------- 588 115 1791243739 counted API key created 2026-10-09 api ord-20115 Click 2871: 588 (replace mode), 1 of 1 conversions counted.
$ p202 click conversions 2871 --json { "click": { "campaign_id": 4, "campaign_name": "Project Tool Pro Annual / US", "click_id": 2871, "click_payout": 588, "counted_rows": 1, "lead": true, "ledger_state": "ledger", "ledger_value": 588, "matches_click": true, "payout_mode": "replace", "rows": 1 }, "data": [ { "amount": 588, "click_id": 2871, "conv_id": 115, "conv_time": 1791243739, "counted": true, "deleted": false, "event_name": null, "explanation": null, "linked_to": { "key_created_at": 1791538968, "key_digest": "03d1792eddc570e9", "label": "API key created 2026-10-09", "revoked": false, "type": "api_key" }, "not_counted_reason": null, "payable": true, "reverses_conv_id": null, "source": "api", "source_label": "API", "source_ref": "apikey:03d1792eddc570e9", "superseded_by": null, "superseded_reason": null, "transaction_id": "ord-20115" } ] }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 click conversionsSet flags below; the command updates as you type.
04How it works
Lists every conversion recorded on the click — counted, unpaid, superseded, deleted and reversals alike — with its amount, what produced it (source), what that is (a goal and version, an upload, the conversion a reversal nets, the API key that wrote it), its transaction id, and whether it counts toward the click's value, with the reason when it does not.
The table shows one line per conversion and ends with the click's value; --json and --ndjson return the API's rows unchanged, and --json adds the "click" summary (value, payout mode, whether the rows add up to what the reports show).
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands click conversions --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
{
"path": "p202 click conversions",
"use": "conversions <click-id>",
"short": "Explain a click's value: every conversion on it, whether it counts, and why not",
"long": "Lists every conversion recorded on the click — counted, unpaid, superseded,\ndeleted and reversals alike — with its amount, what produced it (source), what\nthat is (a goal and version, an upload, the conversion a reversal nets, the API\nkey that wrote it), its transaction id, and whether it counts toward the\nclick's value, with the reason when it does not.\n\nThe table shows one line per conversion and ends with the click's value; --json\nand --ndjson return the API's rows unchanged, and --json adds the \"click\"\nsummary (value, payout mode, whether the rows add up to what the reports show).",
"runnable": true
}