Apple's rules and rejected referral programs
the reward mechanics Apple rejects under guideline 3.2.2, why referral rewards trip review, and designing incentives that pass.
last updated 18 November 2026
Apple rejects referral programs that look like paying for installs, ratings or store actions, which is App Store guideline 3.2.2 territory. the mechanics that pass frame rewards as feature unlocks inside your product’s own economy, trigger on activation rather than install, and avoid anything money-shaped. and because review is applied by humans, you test the flow through review before you bet the quarter on it.
What guideline 3.2.2 actually covers
guideline 3.2.2 is Apple’s list of unacceptable business behavior, and the parts that matter for referrals are the ones about artificially manipulating the store: incentivizing installs, incentivizing ratings and reviews, and schemes where the money flows in ways Apple reads as gaming placement or as a pyramid shape. the language is broad on purpose, and reviewers apply it broadly. the practical consequence is that Apple is not evaluating your growth strategy, it is pattern-matching your reward flow against shapes it has seen abused, and your job is to not have those shapes.
The reward mechanics that trip review
the recurring rejection patterns are consistent enough to list. cash, gift cards or anything convertible to money as a referral reward reads as paying for installs. rewards contingent on the friend leaving a rating or review is close to an automatic rejection. rewards granted on the install event itself, rather than on anything the friend does inside the app, look like chart manipulation, because installs are the unit the charts run on. and multi-level structures, where a user earns from the people their invitees invite, read as pyramid mechanics regardless of how small the amounts are.
two things make this trickier than a rules list. reviewer variance is real: the same mechanic can pass one submission and fail the next, so a pass is evidence, not a guarantee. and rejections often cite the guideline without naming the exact mechanic, which is why you design conservatively instead of litigating each review.
the expensive version of this lesson is the team that builds the full program, buys the launch creative, briefs the influencers, and then meets the rejection with two weeks left in the quarter. at that point every option is bad: appeal and wait, strip the rewards and launch a hollow flow, or slip the date. all three were avoidable, because the rejection risk was knowable months earlier for the cost of one quiet submission.
Designing incentives that pass
the framing that survives review keeps the entire reward economy inside your product. a month of pro for you and your friend reads as product generosity. credits and generation limits read as product features. currency symbols, dollar values and “earn” language read as payouts, even when the underlying grant is identical, so the copywriting is part of the compliance. trigger the reward on the friend activating, reaching first real value inside the app, which both passes review more cleanly and happens to be the honest event to reward anyway. feature unlocks over monetary framing is the whole doctrine in five words, and it costs you almost nothing, because product rewards are what a freemium app should be granting regardless.
Test the flow before you bet the quarter
treat your first referral release as an experiment on review, not a launch.
- ship the flow behind a remote flag in an ordinary release, described plainly in your review notes, and keep it off for users. you are buying information about review, not growth yet.
- if it passes, turn it on for a small cohort and watch the reward accounting and the abuse surface before any announcement.
- keep a de-fanged fallback built: the identical flow with sharing and no reward. if a later submission gets rejected, you swap the flag, the release train keeps moving, and you appeal or redesign without a deadline on fire.
- only after a clean pass and a clean cohort do you spend on creative, announce, or plan the quarter around the numbers.
the store is the other half of this surface: a referral link lands on your product page before it lands in your app, and the ASO playbook covers making that page convert the trust a friend’s link arrives with.
review risk is one more reason the incentivized program sits last in the product-led growth playbook, behind loops Apple has no opinion about. want your reward flow sanity-checked against the rejection patterns before you submit? the breakdown call is free. Let’s talk Growth.
this page is part of the Product-led growth & viral loops playbook.
More in this playbook
Why nobody used your referral program
the post-mortem of the bolted-on referral tab: missing motive, wrong timing, friction, rewards nobody wants, and what to fix before rebuilding.
Product-led growth & viral loopsShareable outputs: the AI-native viral loop
how to design outputs people want to post, make export native per platform, and why share rate times conversion beats invite programs.
Product-led growth & viral loopsWatermarks: growth vs user experience
a watermark converts viewers of shared outputs, but too loud and sharing stops. the subtle-but-legible rules and when to sell removal.
Product-led growth & viral loopsWhen to add a referral program: pre or post PMF
add referral after retention flattens, not after launch. the readiness checklist, and why referral amplifies love it cannot create.
Product-led growth & viral loopsReferral incentives that work for freemium AI apps
credits, generation limits, early features and cosmetics: rewards a freemium AI app can afford, with accounting too simple to farm.
Product-led growth & viral loopsK-factor math that isn't fantasy
the real k-factor formula, why k above 1 is almost mythical, and how sub-1 k still discounts your paid CAC if you measure honestly.
Product-led growth & viral loopsOnboarding as a growth surface
time to first output is the retention lever. how removing onboarding steps compounds every channel, and why activation beats signups.
Product-led growth & viral loopsRetention before referral: the order of operations
loops multiply retention, they never replace it. the honest sequence of activation, habit, then loops, and how to read your curve.