p202 conversion match-methods

Conversions by campaign and by how their click was found (click id, cookie, same IP)

New in 1.9.79
All commands

p202 CLI reference

Back to the docs

01Jobs it does

Each one is a real command line. Copy it, or open it in the builder below to change it.

how conversions were matched

Also: conversions matched by ip, guessed conversions, cookie conversions, conversions without a subid

p202 conversion match-methods

02What you get

Pick the shape you need. People get a table. Add --json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 conversion match-methods

Set flags below; the command updates as you type.

04Flags

4 flags, plus the global flags every command takes.

FlagWhat it does
--aff-campaign-idstringOnly this campaign (an id from p202 campaign list)
--periodstringRange of conversion times: today, yesterday, last7, last14, last30, last90, thismonth, lastmonth, thisyear, lastyear, alltime
todayyesterdaylast7last14last30last90thismonthlastmonththisyearlastyearalltime
--time-fromstringStart: unix seconds, a date (2026-10-01, from its first second in the account's timezone) or a time with its offset (2026-10-01T09:30:00Z)
--time-tostringEnd, inclusive: unix seconds, a date (2026-10-01, through its last second in the account's timezone) or a time with its offset

05How it works

Counts each campaign's conversions by how the click they credit was found: click_id (the postback, pixel, API call or upload named it), cookie (a tracking cookie did), visitor_id (the landing-page script's visitor id), same_ip (nothing named a click: the latest click from the visitor's address, a guess) or unknown (recorded before 1.9.79). conversions excludes reversals, counted is how many count toward their click's value, and income is what those add up to. The window is the conversion time's; the table ends with every method's totals.

p202 conversion match-methods --period last30
p202 conversion list --match-method same_ip --aff-campaign-id 3

06For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands conversion match-methods --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure, 6 no Pro licence on the install.
p202 commands conversion match-methods --json
{
  "path": "p202 conversion match-methods",
  "use": "match-methods",
  "short": "Conversions by campaign and by how their click was found (click id, cookie, same IP)",
  "long": "Counts each campaign's conversions by how the click they credit was found: click_id (the\npostback, pixel, API call or upload named it), cookie (a tracking cookie did), visitor_id (the\nlanding-page script's visitor id), same_ip (nothing named a click: the latest click from the\nvisitor's address, a guess) or unknown (recorded before 1.9.79). conversions excludes\nreversals, counted is how many count toward their click's value, and income is what those\nadd up to. The window is the conversion time's; the table ends with every method's totals.\n\n  p202 conversion match-methods --period last30\n  p202 conversion list --match-method same_ip --aff-campaign-id 3",
  "runnable": true,
  "tasks": [
    {
      "run": "p202 conversion match-methods",
      "phrases": [
        "how conversions were matched",
        "conversions matched by ip",
        "guessed conversions",
        "cookie conversions",
        "conversions without a subid"
      ]
    }
  ],
  "flags": [
    {
      "name": "aff-campaign-id",
      "type": "string",
      "default": "",
      "usage": "Only this campaign (an id from `p202 campaign list`)",
      "required": false
    },
    {
      "name": "period",
      "type": "string",
      "default": "",
      "usage": "Range of conversion times: today, yesterday, last7, last14, last30, last90, thismonth, lastmonth, thisyear, lastyear, alltime",
      "allowed_values": [
        "today",
        "yesterday",
        "last7",
        "last14",
        "last30",
        "last90",
        "thismonth",
        "lastmonth",
        "thisyear",
        "lastyear",
        "alltime"
      ],
      "required": false
    },
    {
      "name": "time-from",
      "type": "string",
      "default": "",
      "usage": "Start: unix seconds, a date (2026-10-01, from its first second in the account's timezone) or a time with its offset (2026-10-01T09:30:00Z)",
      "required": false
    },
    {
      "name": "time-to",
      "type": "string",
      "default": "",
      "usage": "End, inclusive: unix seconds, a date (2026-10-01, through its last second in the account's timezone) or a time with its offset",
      "required": false
    }
  ]
}