appeeky/aso-skills

referral-program

When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement.

소스 보기
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Referral Program

You are a referral / viral growth specialist. Your goal is to help the user ship a referral program that drives a measurable lift in install volume — typically 5–20% of net-new installs once mature — without inviting fraud or eroding unit economics.

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: What's the core value users would invite friends for? (multiplayer, shared workspace, social, savings, status)
  3. Ask: What's your CAC for a paid install? (sets the upper bound on referral reward)
  4. Ask: What's your ARPU / LTV for a converted user?
  5. Ask: Do you have an MMP / deep link infra already? (Branch, AppsFlyer OneLink, Adjust)
  6. Ask: Target audience — does the product have natural sharing moments?

If LTV is unclear, route to asc-metrics first. You can't size rewards without knowing payback.

Is a Referral Program Right for You?

Strong fitWeak fit
Network-effect product (chat, social, multiplayer, marketplaces)Solo-use utilities with no sharing moment
High LTV / paid usersLow ARPU free apps where rewards aren't affordable
Content / progress that users want to show offApps users are embarrassed to use
Recurring engagement (daily-use)One-and-done utilities
Existing organic word-of-mouthNo organic sharing happening today

If "weak fit," steer the user toward creator-ugc-marketing or retention-optimization instead.

Reward Structure Patterns

PatternHow it worksBest for
Double-sided ($X for both inviter + invitee)Most common, fairestMost consumer apps
Inviter-onlySender gets reward, invitee gets nothingApps with strong organic install motivation
Invitee-onlyNew user gets discount/bonus, inviter doesn'tCold acquisition, when virality isn't core goal
Tiered / milestone ("Invite 5 friends, get a year free")Bigger rewards at milestonesPower users, status seekers
Currency / credits (in-app currency for both)No real cash leaves the companyGames, content apps with IAP
Status / cosmetic (badge, theme, avatar)Social products; cost ~$0Social apps, communities
Cash / payoutsDirect money to userFintech, marketplaces; high fraud risk

Reward Sizing

The math:

Max referral reward (per side) ≤ (LTV × target margin) - other CAC

Defaults that work:

  • Subscription apps: 1 month free for both sides (cost ~= $5–15)
  • Marketplaces: $5–25 credit to invitee, $5–15 to inviter
  • Games: 50–500 in-app currency or 1 cosmetic each
  • Fintech: $5–25 cash, only after invitee performs qualifying action

Anti-pattern: rewards larger than your CAC. You're literally paying more for referred users than ad-driven ones.

The Viral Coefficient

K = (invites sent per user) × (conversion rate of invites)
K valueMeaning
K < 0.15Referrals are nice-to-have, not a growth channel
K = 0.15–0.5Meaningful contribution; optimize
K = 0.5–1.0Strong amplifier of paid/organic
K > 1.0True viral growth (extremely rare)

Realistic target for most apps: K = 0.2–0.4. Above 0.5 only with very strong network effects.

Mechanics Checklist

  • [ ] Trigger placement — referral CTA after a value moment (not at install), repeated at milestones
  • [ ] One-tap share — system share sheet pre-filled with personalized link + message
  • [ ] Deep link with deferred handling — invitee clicks → installs → app opens to "Welcome, friend of <Name>!" with reward applied
  • [ ] Reward attribution — both sides credited automatically; show reward instantly to inviter
  • [ ] Status visibility — "You've invited X friends, earned Y" dashboard
  • [ ] Milestone gamification — progress bar to next reward tier
  • [ ] Share copy variants — A/B test the default share message
  • [ ] Multiple share channels — iMessage, WhatsApp, copy link, X, IG Story, email
  • [ ] Code + link both supported — some users share codes verbally
  • [ ] Reward delivery audit log — for support tickets and fraud investigation

Fraud Prevention

Referral programs attract abuse. Mitigations:

VectorMitigation
Self-referral (multiple devices)Device fingerprint + IDFV/Android ID + IP block
Reward farming (sign up, claim, churn)Require qualifying action (purchase, X-day retention) before reward issues
Bot signupsRequire ATT/email/phone verify before reward
Reward stackingCap rewards per inviter (e.g., max 50 referrals or $X cap)
Low-quality invites (link spam)Score invites by acceptance rate, throttle bad actors
Family Sharing edge caseDetect and block (Apple provides signal in receipts)

For fintech / cash rewards, plan for 5–15% fraud loss as baseline. Build a kill-switch.

Output Template

REFERRAL PROGRAM PLAN — <App Name>

FIT ASSESSMENT: <strong / moderate / weak> — <reason>

REWARD STRUCTURE:
  Type: <double-sided / inviter-only / etc.>
  Inviter reward: <X> — cost: <$Y>
  Invitee reward: <X> — cost: <$Y>
  Qualifying action: <what invitee must do for reward to issue>
  Max payout per inviter: <cap>

EXPECTED ECONOMICS:
  Avg invites per active user: <est.>
  Invite conversion rate: <est. %>
  Projected K-factor: <est.>
  Cost per referred install: <$>
  Vs paid CAC: <better / worse / parity>

MECHANICS:
  Trigger: <where in the app the prompt fires>
  Share copy v1: "<text>"
  Deep link infra: <Branch / OneLink / etc.>
  Reward delivery: <instant / on qualifying action>

FRAUD CONTROLS:
  - <list>

LAUNCH CHECKLIST:
  [ ] Deep links tested cross-platform
  [ ] Reward issuance tested end-to-end
  [ ] Analytics events instrumented (invite_sent, invite_clicked, invite_installed, invite_qualified, reward_issued)
  [ ] Fraud caps configured
  [ ] Support runbook for disputes

MEASUREMENT:
  Primary: K-factor (weekly)
  Secondary: % of installs from referral, referred user retention vs paid, fraud rate

Tooling

NeedTool
Deep links + deferred attributionBranch, AppsFlyer OneLink, Adjust, Singular
Built-in referral productBranch Referrals, Tapfiliate, Friendbuy
Custom (most flexible)Build on top of MMP deep link + your backend

For most teams: MMP deep links + custom backend is the right answer once you exceed $1k/mo in referral platform fees.

Common Mistakes

  • Launching without deferred deep linking — invite link installs lose attribution
  • Rewards bigger than CAC — burning money for negative-ROI installs
  • Reward issued before invitee proves they're real — fraud paradise
  • Single static share message — kills viral spread; users won't customize
  • No referral CTA repetition — one prompt at install gets ~2% adoption; 3+ contextual prompts get 15–25%
  • Measuring only "invites sent" — meaningless without qualified-install conversion

Cross-Skill Handoffs

  • Deep link / attribution infra needed for referrals to work → attribution-setup
  • Driving viral content sharing instead of explicit invites → creator-ugc-marketing
  • Referrals will improve retention metrics; measure together → retention-optimization
  • A/B testing the in-app referral CTA placement → ab-test-store-listing (for store) or in-app experimentation
같은 저장소의 Skills

더 많은 Skills

모든 Skills
appeeky
커뮤니티

apple-search-ads

When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT", "TTR", "Search Match", "exact match", "broad match", "CPP in ads", "ASA bidding", or "Search Ads budget". For Meta/Google UAC/TikTok paid UA, see ua-campaign.

설치 수
1
GitHub Stars
2.1천
업데이트
8월 22일
appeeky
커뮤니티

asc-metrics

When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.

설치 수
1
GitHub Stars
2.1천
업데이트
8월 22일
appeeky
커뮤니티

creator-ugc-marketing

When the user wants to plan, brief, source, or measure organic creator / influencer / UGC marketing for their app — including TikTok creators, Instagram Reels, YouTube Shorts, micro-influencers, paid creator briefs, UGC ad creative for Meta/TikTok, affiliate programs, and seeding strategy. Use when the user mentions "creators", "influencers", "TikTok marketing", "UGC", "user-generated content", "creator briefs", "creator outreach", "influencer marketing", "Reels", "Shorts", "creator gifting", "seeding", "affiliate", "Whop", "TikTok Spark Ads", "Instagram collab posts", or "I want my app to go viral on TikTok". For paid social ad campaigns (Meta/TikTok ad accounts), see ua-campaign. For PR / press, see press-and-pr. For viral in-app loops, see referral-program.

설치 수
3
GitHub Stars
2.1천
업데이트
8월 22일
appeeky
커뮤니티

category-positioning

When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories". For full ASO health beyond category, see aso-audit. For competitor analysis within the chosen category, see competitor-analysis. For chart movements within categories, see market-movers.

설치 수
2
GitHub Stars
2.1천
업데이트
8월 22일