p202 ltv engagement

One customer's engagement — browsing, instrumented events, and the suggested next offer

All commands

p202 CLI reference

Back to the docs

01Run it

Replace the <placeholders> with your own values, or use the builder below.

p202 ltv engagement <customer-id>

02What you get

Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.

p202 ltv engagement 1
$ p202 ltv engagement 1
browsing:  [{"campaign_id":3,"campaign_name":"Standing Desk Launch / UK","clicks":1,"conversions":"1","landing_page":null,"last_seen":1790583838}]
events:    []
campaign_id:  5
name:         Free Trial to Paid / CA
url:          https://app.example.com/signup?plan=trial
why:          {"basis":"account_top_recent","window_days":180}
Real output · p202 1.9.77 · demo dataexit 0

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 ltv engagement

Set flags below; the command updates as you type.

04Flags

1 flag, plus the global flags every command takes.

FlagWhat it does
--days, -dstringEngagement window in days (default 90, max 365)

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands ltv engagement --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 ltv engagement --json
{
  "path": "p202 ltv engagement",
  "use": "engagement <customer-id>",
  "short": "One customer's engagement — browsing, instrumented events, and the suggested next offer",
  "runnable": true,
  "flags": [
    {
      "name": "days",
      "shorthand": "d",
      "type": "string",
      "default": "",
      "usage": "Engagement window in days (default 90, max 365)",
      "required": false
    }
  ]
}