Measurement: one store campaign link per platform and account
The iOS campaign link format with the provider token and a 40-character ct tag, the Android Play referrer, where installs show up, and the rule to judge a format after a week on installs, not views.
Build the campaign link table for {app name}. One link per platform and account. iOS (App Store Connect campaign link): https://apps.apple.com/app/apple-store/id{APP_ID}?pt={PROVIDER_ID}&ct={platform}-{account}&mt=8 - APP_ID: the numeric id from the store URL. - PROVIDER_ID: the provider token from App Store Connect (App Analytics, Sources, campaign links). - ct: the campaign name, platform-account, 40 characters max, lowercase, hyphens. - Installs per campaign: App Store Connect, App Analytics, Sources. Android (Play referrer): https://play.google.com/store/apps/details?id={PACKAGE}&referrer=utm_source%3D{platform}%26utm_medium%3D{account}%26utm_campaign%3D{series} - The referrer value is URL-encoded once; the app reads it through the Install Referrer API and logs it. Table: platform, account, ct value (count the characters), full iOS link, full Android link, where the link sits (bio / pinned comment / creator brief). Rule: judge a format after a week of posts on installs per campaign, not on views.
In Claude Code, paste the prompt as a message, or run /creator-growth which does this end to end.
Steps
- Create the links before the first post; a post without a link is a view you cannot attribute.
- Put the iOS link in the bio and the Android one in a pinned comment or a link page; one link per account, never per video, or the table outgrows the week.
- Read the Sources report weekly, same weekday, and paste installs per campaign into the review sheet.
Tips
- ct is limited to 40 characters; count it before you print it anywhere.
- Views are attention, installs are the result. Only per-campaign installs separate a format that went viral from one that converted.
| works with | By hand: No tool needed: a checklist or a technique. · Claude Code: Runs as a skill or a prompt in the terminal; can read your files and write the result. · Any LLM: Model-agnostic: Gemini, Mistral, a local model. |
| skill | npx skills add fortunto2/solo-factory --skill solo-creator-growth · skill page · source |
| cost | Free. No API, no key. |
| status | Unverified: written from the technique, not yet run end to end by us. |
| license | CC BY 4.0 for the text here; skills are MIT. |
| updated | 2026-11-01 |
| for agents | campaign-links-per-platform-and-account.md |
Related
Weekly growth review: an agent reads the posts and the installs per campaign
Paste the week's posts and the installs per campaign link; the agent reports numbers first, then what worked by name, then 3-4 actions, judging by installs and by multiples, never by a 20 % swing.
2-3 niche accounts, one audience archetype each, one app per account
Why several small accounts beat one big one for an app: each speaks to one kind of viewer. A prompt that defines the archetypes and the account plan, and the clone trap that gets accounts suppressed.
A/B test hooks with campaign links: judge after a week on installs, not views
The creator-growth method: same video, different hook, one store campaign link per variant, installs per campaign read after a week. Includes the iOS ct= link shape and the noise rule.
The creator budget gate: can you afford a paid creator yet?
A fill-in prompt that divides a creator's monthly retainer by your net revenue per sale to get payback sales per month, then says whether you are in Phase 1 (founder-led, $0) or allowed to pay.
The download ask lives in the comments, not in every video
A hard sell in every video gives viewers a reason to scroll. Name the app in replies to 'what app is this?', keep the link in the bio, and write the replies before you need them.
Phase 1, founder-led: the four formats and what each one buys
Educational converts, POV and humor get reach, story builds trust, comparison works when the app replaces something expensive. A prompt that plans a week of founder videos across all four.