01How it works
Before 1.9.79, renaming a traffic source on Setup › Traffic Sources moved it into the account of
the user who saved the rename, whoever's it was; its traffic source accounts stayed behind. show
lists every source other users' accounts name, with the counts on each user's accounts; repair
moves one back, or every one the report names a user for; split gives each user whose accounts
name one a copy of their own, which clears a source accounts of more than one user name. Nothing is
moved by itself: the same rows also come from accounts the API put on another user's source before
1.9.77, or a move made on purpose, and the report marks those it cannot tell apart (ambiguous).
Needs an Admin or Super user key whose role has access_to_settings (as Account › Settings asks).
02Commands
3 under p202 system traffic-source-owners.
03For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands system traffic-source-owners --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, 6 no Pro licence on the install.
{
"path": "p202 system traffic-source-owners",
"use": "traffic-source-owners",
"short": "Traffic sources in one user's account that another user's traffic source accounts name (taken before 1.9.79): show, repair, split",
"long": "Before 1.9.79, renaming a traffic source on Setup › Traffic Sources moved it into the account of\nthe user who saved the rename, whoever's it was; its traffic source accounts stayed behind. `show`\nlists every source other users' accounts name, with the counts on each user's accounts; `repair`\nmoves one back, or every one the report names a user for; `split` gives each user whose accounts\nname one a copy of their own, which clears a source accounts of more than one user name. Nothing is\nmoved by itself: the same rows also come from accounts the API put on another user's source before\n1.9.77, or a move made on purpose, and the report marks those it cannot tell apart (ambiguous).\n\nNeeds an Admin or Super user key whose role has access_to_settings (as Account › Settings asks).",
"runnable": false
}