p202 ppc-account pixel

Manage the pixels a traffic source account fires on a conversion

Aliasppc-account pixelsNew in 1.9.77
All commands

p202 CLI reference

Back to the docs

01How it works

An account's pixels report its conversions back to the traffic source. Types (--type-id): 1 Image, 2 Iframe, 3 Javascript, 4 Postback (server to server), 5 Raw (markup as given), 6 Bot202 Facebook Pixel Assistant. For every type except Raw the code is the URL (several separated by spaces), with tokens such as [[subid]], [[payout]] or [[transactionid]] filled in when it fires.

A Postback pixel can also take a correction URL (--correction-url), where corrections go when a conversion it announced is replaced; one per code URL, in the same order.

Setup > Traffic Sources > an account's Advanced edits the same pixels. Needs a role with access_to_setup_section and a key with ppc-accounts scope.

02Commands

4 under p202 ppc-account pixel.

p202 ppc-account pixel createAdd a pixel to a traffic source accountp202 ppc-account pixel deleteRemove a pixel from a traffic source account (with its correction URL)p202 ppc-account pixel listList a traffic source account's pixelsp202 ppc-account pixel updateChange a traffic source account's pixel

03For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands ppc-account pixel --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.
p202 commands ppc-account pixel --json
{
  "path": "p202 ppc-account pixel",
  "use": "pixel",
  "short": "Manage the pixels a traffic source account fires on a conversion",
  "long": "An account's pixels report its conversions back to the traffic source. Types\n(--type-id): 1 Image, 2 Iframe, 3 Javascript, 4 Postback (server to server),\n5 Raw (markup as given), 6 Bot202 Facebook Pixel Assistant. For every type except\nRaw the code is the URL (several separated by spaces), with tokens such as\n[[subid]], [[payout]] or [[transactionid]] filled in when it fires.\n\nA Postback pixel can also take a correction URL (--correction-url), where corrections\ngo when a conversion it announced is replaced; one per code URL, in the same order.\n\nSetup > Traffic Sources > an account's Advanced edits the same pixels. Needs a role\nwith access_to_setup_section and a key with ppc-accounts scope.",
  "aliases": [
    "pixels"
  ],
  "runnable": false
}