01Run it
Straight from the command's own help.
p202 ppc-account pixel delete 4 9 --dry-runp202 ppc-account pixel delete 4 9 --force02What 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 formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 ppc-account pixel deleteSet flags below; the command updates as you type.
04Flags
3 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --dry-runbool | Preview what the delete would remove (record + cascade counts) without deleting |
| --force, -fbool | Skip confirmation prompt |
| --idsstring | Comma-separated pixel IDs to delete in bulk |
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands ppc-account pixel delete --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.
- This command writes. Add
--stagedto record it as a proposal a person applies withp202 change apply.
{
"path": "p202 ppc-account pixel delete",
"use": "delete <ppc_account_id> <pixel_id>",
"short": "Remove a pixel from a traffic source account (with its correction URL)",
"runnable": true,
"example": "p202 ppc-account pixel delete 4 9 --dry-run\n p202 ppc-account pixel delete 4 9 --force",
"flags": [
{
"name": "dry-run",
"type": "bool",
"default": "false",
"usage": "Preview what the delete would remove (record + cascade counts) without deleting",
"required": false
},
{
"name": "force",
"shorthand": "f",
"type": "bool",
"default": "false",
"usage": "Skip confirmation prompt",
"required": false
},
{
"name": "ids",
"type": "string",
"default": "",
"usage": "Comma-separated pixel IDs to delete in bulk",
"required": false
}
]
}