Subscription offer code type by campaign scale
Use one-time App Store offer codes for controlled distribution and custom codes for broad campaigns instead of pushing the same code format into every motion.
Why this can grow a startup
Offer-code campaigns get messy when the team ignores how the codes are meant to travel. Apple's one-time-use codes are built for restricted distribution, while custom codes are built for larger campaigns and can keep running without a required end date. Picking the code type to match the route keeps a private win-back push from leaking too widely and keeps a large campaign from turning into a brittle spreadsheet exercise.
Source-backed example
Apple says one-time-use offer codes are useful for small-scale distribution or restricted access, while custom codes are ideal for large campaigns that require mass distribution.
Source-reported evidence
Source: App Store Connect Help · Browse App Store Connect Help tactics
Apple lets teams create custom codes with redemption limits up to 25,000 at a time and supports up to 1 million offer-code redemptions per app per quarter.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when App Store, Lifecycle, Mobile is relevant to offer distribution, campaign design, subscription growth and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to App Store and Lifecycle, using evidence from App Store Connect Help as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from App Store Connect Help
Explore related GrowthDex examples and evidence connected to App Store Connect Help.
Open App Store Connect Help source hub