01Run it
Straight from the command's own help.
p202 ltv customer alias add 42 --type esp_id --value 4821302What you get
Pick the shape you need. People get a table. Add
--json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 ltv customer alias addSet flags below; the command updates as you type.
04Flags
2 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --typestring | What kind of identifier (default custom): email_md5, email_sha256, esp_id, merchant_id, subid, customemail_md5email_sha256esp_idmerchant_idsubidcustom |
| --valuestringrequired | The identifier (required); email_md5/email_sha256 take the hex digest |
05How it works
Later events carrying this identifier resolve to the customer. An identifier that already belongs to another customer is refused (the two records are one person: merge them).
p202 ltv customer alias add 42 --type esp_id --value 48213
06For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands ltv customer alias add --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.
- This command writes and cannot be staged:
--stagedis refused before anything is sent. Have a person run it, or give the agent a key without write scope.
{
"path": "p202 ltv customer alias add",
"use": "add <customer-id> --value <identifier>",
"short": "Add an identifier that resolves to this customer from then on",
"long": "Later events carrying this identifier resolve to the customer. An identifier that already\nbelongs to another customer is refused (the two records are one person: merge them).\n\n p202 ltv customer alias add 42 --type esp_id --value 48213",
"runnable": true,
"flags": [
{
"name": "type",
"type": "string",
"default": "",
"usage": "What kind of identifier (default custom): email_md5, email_sha256, esp_id, merchant_id, subid, custom",
"allowed_values": [
"email_md5",
"email_sha256",
"esp_id",
"merchant_id",
"subid",
"custom"
],
"required": false
},
{
"name": "value",
"type": "string",
"default": "",
"usage": "The identifier (required); email_md5/email_sha256 take the hex digest",
"required": true
}
]
}