# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/subscription-offer-code-type-by-campaign-scale/
- Source: [developer.apple.com](https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-subscription-offer-codes/)
- GrowthDex source hub: [App Store Connect Help](/sources/app-store-connect-help-developer-apple-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: App Store, Lifecycle, Mobile
- Stages: offer distribution, campaign design, subscription growth, reactivation


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where subscription offer code type by campaign scale can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the App Store and Lifecycle channel.
3. Use the evidence from developer.apple.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Subscription offer codes by lifecycle state](/growth-ideas/subscription-offer-codes-by-lifecycle-state/) - same source, 2 shared channels, 2 shared stages
- [Win-back eligibility report for reactivation prioritization](/growth-ideas/win-back-eligibility-report-for-reactivation-prioritization/) - same source, 2 shared channels, 1 shared stage
- [App Store locale map before metadata rollout](/growth-ideas/app-store-locale-map-before-metadata-rollout/) - same source, 2 shared channels
- [Keyword-triggered custom product pages in App Store search](/growth-ideas/keyword-triggered-custom-product-pages-in-app-store-search/) - same source, 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The App Store route should be judged after the install](/blog/the-app-store-route-should-be-judged-after-the-install/) - mobile growth, analytics, retention

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.