01How it works
A traffic source's custom variables are the extra parameters its tracking links
carry, each with the placeholder the traffic source fills in: parameter=placeholder,
e.g. adid={ad_id}. p202 tracker get-url writes the live ones into every link of the
source's accounts. A variable whose parameter is a built-in token (c1-c4, utm_*,
t202kw, t202ref, t202b) sets that token's default instead.
Setup > Traffic Sources > variables edits the same list. Needs a role with remove_traffic_source and access_to_setup_section (Super user or Admin; the page shows the variables dialog only to them) and a key with ppc-networks scope.
02Commands
4 under p202 ppc-network variable.
03For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands ppc-network variable --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.
{
"path": "p202 ppc-network variable",
"use": "variable",
"short": "Manage a traffic source's custom variables (the extra parameters its tracking links carry)",
"long": "A traffic source's custom variables are the extra parameters its tracking links\ncarry, each with the placeholder the traffic source fills in: parameter=placeholder,\ne.g. adid={ad_id}. `p202 tracker get-url` writes the live ones into every link of the\nsource's accounts. A variable whose parameter is a built-in token (c1-c4, utm_*,\nt202kw, t202ref, t202b) sets that token's default instead.\n\nSetup > Traffic Sources > variables edits the same list. Needs a role with\nremove_traffic_source and access_to_setup_section (Super user or Admin; the\npage shows the variables dialog only to them) and a key with ppc-networks scope.",
"aliases": [
"variables",
"var"
],
"runnable": false
}