p202 ltv

Customer lifetime value — realized LTV, per-customer detail, product/acquisition breakdowns, MRR/churn, and predictive LTV

All commands

p202 CLI reference

Back to the docs

01How it works

Customer lifetime value: the reads (summary, customers, breakdown, cohorts, mrr, predict, abm, engagement, subscriptions, companies, products) and the writes the API offers — customer and company records (ltv customer, ltv company), revenue, engagement events, subscriptions and products pushed from other systems, custom fields, outbound webhooks and integrations.

LTV writes cannot be staged: under --staged they are refused before anything is sent.

02Commands

21 under p202 ltv.

p202 ltv abmABM account view — companies ranked by engagement with scores, depth metrics, revenue and MRRp202 ltv breakdownLTV by acquisition source (campaign, ppc_account, landing_page) or by productp202 ltv cohortsLTV maturation by acquisition month — each cohort's revenue by months since first seen (m0..m4, m5_plus)p202 ltv companiesCompany (ABM account) entities with live contact/revenue rollups (writes: `p202 ltv company`)p202 ltv companyWrite company (ABM account) records: create, update, merge, delete (reads: `p202 ltv companies`)p202 ltv customerWrite customer records: upsert, update, merge, erase (anonymize), aliases (reads: `p202 ltv customers`)p202 ltv customersList customers with LTV rollups, or show one customer in full (CRM, aliases, custom fields, recent revenue)p202 ltv engagementOne customer's engagement — browsing, instrumented events, and the suggested next offerp202 ltv engagement-eventRecord server-side ABM engagement events on a customer (not `p202 event send`, which reports a click's web events to its goals)p202 ltv fieldsCustomer custom-field definitions: list, create, update, deletep202 ltv integrationsInbound integration records (an ESP, membership or billing system pushing LTV data): list, create, deletep202 ltv mrrSubscription economics — active MRR/ARR, status counts, monthly churn with its inputsp202 ltv next-offerReport that you delivered a customer's next-offer recommendation (read it with `p202 ltv engagement`)p202 ltv predictPredictive LTV — deterministic projection with guards; every number ships with its inputsp202 ltv productCatalog products: upsert by your product id, update or delete by id (reads: `p202 ltv products`)p202 ltv productsThe product catalog revenue line items and `ltv product upsert` write to, newest firstp202 ltv revenueRecord clickless revenue (an ESP order, a membership charge) on a customer's ledgerp202 ltv subscriptionCreate or update a subscription, and record its renewals, refunds and cancellation (reads: `p202 ltv subscriptions`)p202 ltv subscriptionsAccount-wide subscription list joined to customers, filterable by lifecycle statusp202 ltv summaryRealized LTV totals — customers, revenue, avg LTV, AOV, repeat rate, MRRp202 ltv webhooksOutbound LTV webhooks (customer, revenue, subscription, conversion, engagement events): list, create, deliveries, delete

03For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands ltv --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 --json
{
  "path": "p202 ltv",
  "use": "ltv",
  "short": "Customer lifetime value — realized LTV, per-customer detail, product/acquisition breakdowns, MRR/churn, and predictive LTV",
  "long": "Customer lifetime value: the reads (summary, customers, breakdown, cohorts, mrr, predict, abm,\nengagement, subscriptions, companies, products) and the writes the API offers — customer and\ncompany records (`ltv customer`, `ltv company`), revenue, engagement events, subscriptions and\nproducts pushed from other systems, custom fields, outbound webhooks and integrations.\n\nLTV writes cannot be staged: under --staged they are refused before anything is sent.",
  "runnable": false
}