Subscription introductory offer readiness checklist
Introductory pricing can improve conversion, but unclear first-period promises create churn and review risk.
Before enabling an introductory subscription offer, reconcile eligibility, paywall claims, subscription group behavior, renewal pricing, and restore states. Apple documents introductory offers for auto-renewable subscriptions. AppReviewReady interpretation: the first paid period should be a promise ledger, not a generic discount badge.
Define eligibility before copy
Write who should see the offer: new subscribers, first-time users in a subscription group, users in selected regions, or users entering from a specific campaign. The paywall should not promise a trial to users who cannot redeem it.
Eligibility also affects support. If a returning user asks why an introductory price is unavailable, support needs a precise answer that matches StoreKit behavior and App Store subscription rules.
Do not make the introductory offer the only explanation of value. The user should understand the normal subscription, renewal price, and cancellation route before the discounted period becomes the main visual hook.
Align paywall and renewal terms
- Show what the user receives during the introductory period.
- State the renewal price and cadence clearly.
- Keep eligibility, duration, and region claims consistent across locales.
- Verify screenshots and App Store metadata do not overstate the offer.
- Prepare a no-offer version for ineligible users.
Test first-period states
Test eligible new user, ineligible returning user, canceled trial, upgrade, downgrade, billing issue, restore, and no-network purchase states. The goal is to prove the entitlement state, not only that the sheet appears.
AppReviewReady interpretation: introductory offers are review-relevant because they affect the truthfulness of subscription disclosure and the reviewer path to paid value.
Connect test results to analytics carefully. Introductory users may convert well on day one and churn later if the renewal promise was unclear. Measure activation, renewal, refund, and support signals together.
Prepare support and rollback
- Create support answers for eligibility, cancellation, renewal price, and restore behavior.
- Monitor refund requests mentioning trial, intro price, or unexpected renewal.
- Pause campaign traffic if paywall confusion appears.
- Keep a normal-price paywall path ready.
- Review App Review feedback before expanding the offer.
Introductory offer ledger
The ledger makes the offer auditable across product, growth, support, and finance. It also prevents old campaign language from surviving after the offer terms change.
Use the ledger before creating screenshots, social ads, or landing pages. A paid acquisition campaign that advertises a first-month price must match the App Store purchase surface exactly enough that users do not feel tricked.
After the first cohort renews, compare refund and cancellation language with the ledger. If users mention surprise, fix disclosure and targeting before raising spend.
Do not judge an introductory offer only by trial starts. The more useful signal is whether eligible users reach the core paid value before renewal. A generous first period can still be a poor offer if onboarding hides the benefit.
Intro offer record: Subscription group: [group] Offer type: [trial/pay-up-front/pay-as-you-go] Eligibility: [rule] Renewal price shown: [yes/no] Locales: [list] Support macro: [link] Monitor: [metric]
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 intro offer readiness
Review eligibility, paywall terms, first-period testing, and support readiness.
Open the tool