p202 system traffic-source-owners show

List the traffic sources other users' accounts name: who has each now, whose accounts name it, and what a repair would do

New in 1.9.79
All commands

01Jobs it does

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

missing traffic source

Also: traffic source taken by another user, traffic source in the wrong account, move a traffic source back

p202 system traffic-source-owners show

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 system traffic-source-owners show

Set flags below; the command updates as you type.

04How it works

One row per source: the user it is in now, each user whose traffic source accounts name it (with their accounts, clicks and conversions), repair_to (the user repair moves it to without --to-user-id; blank when ambiguous) and why it is ambiguous: owner_has_accounts (its own user has accounts on it too), several_users, saved_after_rename (an account was saved after the source, or in its second: the shape the API made before 1.9.77), no_such_user, deleted_user (a source never moves into a deleted user's account; a switched-off user's is shown and still repaired). No move clears a source marked owner_has_accounts or several_users: another user's accounts still name it wherever it is. split does. --json carries the account ids and custom variables too.

Needs an Admin or Super user key whose role has access_to_settings (as Account › Settings asks), and system:read.

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands system traffic-source-owners show --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 system traffic-source-owners show --json
{
  "path": "p202 system traffic-source-owners show",
  "use": "show",
  "short": "List the traffic sources other users' accounts name: who has each now, whose accounts name it, and what a repair would do",
  "long": "One row per source: the user it is in now, each user whose traffic source accounts name it (with\ntheir accounts, clicks and conversions), repair_to (the user `repair` moves it to without\n--to-user-id; blank when ambiguous) and why it is ambiguous: owner_has_accounts (its own user has\naccounts on it too), several_users, saved_after_rename (an account was saved after the source,\nor in its second: the shape the API made before 1.9.77), no_such_user, deleted_user (a source\nnever moves into a deleted user's account; a switched-off user's is shown and still repaired).\nNo move clears a source marked owner_has_accounts or several_users: another user's accounts still\nname it wherever it is. `split` does. --json carries the account ids and custom variables too.\n\nNeeds an Admin or Super user key whose role has access_to_settings (as Account › Settings asks), and system:read.",
  "runnable": true,
  "example": "p202 system traffic-source-owners show\n  p202 system traffic-source-owners show --json",
  "tasks": [
    {
      "run": "p202 system traffic-source-owners show",
      "phrases": [
        "missing traffic source",
        "traffic source taken by another user",
        "traffic source in the wrong account",
        "move a traffic source back"
      ]
    }
  ]
}