01Run it
Straight from the command's own help.
p202 ppc-network variable update 3 7 --placeholder '{{ad.id}}'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 formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 ppc-network variable updateSet flags below; the command updates as you type.
04Flags
3 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --namestring | The variable's name in reports |
| --parameterstring | The link's parameter, e.g. adid (no spaces, &, #, ?, =) |
| --placeholderstring | What the traffic source fills in, e.g. {ad_id} (no spaces, &, #, ?) |
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands ppc-network variable update --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-network variable update",
"use": "update <ppc_network_id> <variable_id>",
"short": "Change a traffic source's custom variable",
"runnable": true,
"example": "p202 ppc-network variable update 3 7 --placeholder '{{ad.id}}'",
"flags": [
{
"name": "name",
"type": "string",
"default": "",
"usage": "The variable's name in reports",
"required": false
},
{
"name": "parameter",
"type": "string",
"default": "",
"usage": "The link's parameter, e.g. adid (no spaces, &, #, ?, =)",
"required": false
},
{
"name": "placeholder",
"type": "string",
"default": "",
"usage": "What the traffic source fills in, e.g. {ad_id} (no spaces, &, #, ?)",
"required": false
}
]
}