01Run it
Straight from the command's own help.
p202 app link 7p202 app link 7 --campaign-id 12 --apply02What you get
--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 app linkSet flags below; the command updates as you type.
04Flags
2 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --applybool | Set the campaign's offer URL to the store link and, for Android, link it to the app (and turn URL rotation off when an alternate in rotation is not the app's link) |
| --campaign-idstring | Say whether this campaign sends its clicks to the store link (p202 campaign list) |
05How it works
Shows the store link for the app: for Android the Play link with [[p202_install_token]] in
its referrer (the redirect fills it per click; the SDK reads it back), for iOS the App Store
link and the SKAdNetwork/AdAttributionKit Info.plist setup. With --campaign-id it says whether
that campaign is ready — its offer URL is the store link and, for Android, the campaign is
linked to the app — and with --apply it makes it so (PUT /campaigns/{id}; honours --staged).
Then p202 tracker create --aff-campaign-id N gives the tracking link.
06For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands app link --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. Add
--stagedto record it as a proposal a person applies withp202 change apply.
{
"path": "p202 app link",
"use": "link <registration-id>",
"short": "The store link a campaign should send this app's clicks to, and whether a campaign does",
"long": "Shows the store link for the app: for Android the Play link with [[p202_install_token]] in\nits referrer (the redirect fills it per click; the SDK reads it back), for iOS the App Store\nlink and the SKAdNetwork/AdAttributionKit Info.plist setup. With --campaign-id it says whether\nthat campaign is ready — its offer URL is the store link and, for Android, the campaign is\nlinked to the app — and with --apply it makes it so (PUT /campaigns/{id}; honours --staged).\nThen `p202 tracker create --aff-campaign-id N` gives the tracking link.",
"runnable": true,
"example": "p202 app link 7\n p202 app link 7 --campaign-id 12 --apply",
"flags": [
{
"name": "apply",
"type": "bool",
"default": "false",
"usage": "Set the campaign's offer URL to the store link and, for Android, link it to the app (and turn URL rotation off when an alternate in rotation is not the app's link)",
"required": false
},
{
"name": "campaign-id",
"type": "string",
"default": "",
"usage": "Say whether this campaign sends its clicks to the store link (`p202 campaign list`)",
"required": false
}
]
}