p202 app install

Android installs: list, inspect, mint a click's install token, simulate the SDK

Aliasapp installs
All commands

p202 CLI reference

Back to the docs

01How it works

Android installs reach the server from the SDK (POST /apps/installs); each is classified into a match state (attributed, organic, bad_token, …) with its reason.

p202 app install list 3 --match-state attributed
p202 app install token 3 --click 1042
p202 app install simulate 3 --click 1042

02Commands

4 under p202 app install.

p202 app install getGet one install: its referrer, timestamps, match state, reason and trustp202 app install listList an Android registration's installs, newest first, with their match state and reasonp202 app install simulatePost an SDK-shaped install for a real click, as a device wouldp202 app install tokenShow the install token and Google Play store link for one click

03For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands app install --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 app install --json
{
  "path": "p202 app install",
  "use": "install",
  "short": "Android installs: list, inspect, mint a click's install token, simulate the SDK",
  "long": "Android installs reach the server from the SDK (POST /apps/installs); each is\nclassified into a match state (attributed, organic, bad_token, …) with its reason.\n\n  p202 app install list 3 --match-state attributed\n  p202 app install token 3 --click 1042\n  p202 app install simulate 3 --click 1042",
  "aliases": [
    "installs"
  ],
  "runnable": false
}