IAP offer codes campaign checklist
Offer codes are not just promotion mechanics; they create entitlement, support, and revenue evidence that must reconcile after redemption.
Before creating in-app purchase offer codes, map the product, audience, code limits, redemption journey, entitlement activation, and support plan. Apple documents offer codes for in-app purchases. AppReviewReady interpretation: campaign success is measured by clean redemption and retained value, not only by codes distributed.
Choose the campaign product
Pick a product whose value is easy to understand after redemption. Offer codes work poorly when the user needs hidden setup, a special account state, or a long explanation before the entitlement becomes visible.
Confirm the product type, price, availability, and current review status before generating codes. A campaign should not expose a product that the app no longer sells or support cannot explain.
AppReviewReady interpretation: offer code campaigns should be tied to acquisition, retention, support recovery, or partnership goals. Random code distribution produces weak learning and messy entitlement questions.
Define audience and limits
- Record who receives the codes and why.
- Set expiration, quantity, region, and distribution channel rules.
- Prepare separate codes for press, partners, support, and experiments.
- Avoid sharing reusable code lists without ownership.
- Keep campaign copy consistent with product value and eligibility.
Test redemption paths
Test redemption from the App Store, from inside the app if supported, from a fresh install, from an existing account, on a second device, after cancellation, and after the code has expired or already been used.
The app should immediately show the unlocked value or explain the next step. A redeemed code that appears to do nothing creates support cost and weakens campaign trust.
If codes are used for support recovery, keep the support case linked to the code batch. That makes it possible to detect whether codes solve the problem or hide a deeper entitlement bug.
Support and reconcile
- Give support a code lookup and entitlement verification path.
- Track distributed, redeemed, expired, failed, and refunded outcomes.
- Separate paid revenue from promotional access in reports.
- Review abuse or resale signals for broad campaigns.
- Close the campaign with a revenue and support summary.
Offer code campaign ledger
The ledger keeps campaigns from becoming orphaned code batches. It also helps future operators understand why a user received access without a normal purchase event.
Review campaign performance after the entitlement window, not immediately after distribution. A code that is redeemed but never used may be a poor acquisition channel or a confusing product promise.
For AppReviewReady itself, this pattern informs future partner or agency promotions: codes should create measurable qualified usage, not merely inflate activation numbers.
Expire campaign materials with the codes. Old partner pages, emails, or screenshots that keep advertising dead codes create support work and can make the product feel neglected.
Offer code record: Product ID: [id] Audience: [segment] Quantity: [count] Expiration: [date] Distribution: [channel] Entitlement check: [signal] Support owner: [team] Outcome: [summary]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check offer code campaign
Review product selection, audience limits, redemption paths, support, and revenue reconciliation.
Open the tool