Pre-registration rewards: cap, date and store-page match

Pre-registration rewards must match the store page and be deliverable. Google’s pre-registration help states you can create one pre-registration reward for the lifetime of an app/game’s pre-registration campaign; after creation it cannot be edited or deleted; only active one-time products (not subscriptions) qualify; failure to deliver may risk suspension; campaigns are subject to a 90-day country window. Apple’s pre-order page documents regional release dates, 2–180 days for brand-new apps (2–365 for existing apps into new regions), and the preorder_date receipt field for unlocking rewards such as gems.

Operator checklist

1. Platform split: Play pre-registration ≠ Apple pre-order — separate checklists.
2. Play: One reward SKU; create before campaign start; T&Cs URL on listing; 90-day country clock.
3. Play listing: Reward badge/copy matches the managed product you will grant.
4. Apple: Expected release date hygiene; avoid putting a fragile date in paid ads if it may slip (Apple warns buyers are not notified of date changes by Apple).
5. Apple reward: Implement preorder_date grant path before promising gems/items.
6. UA copy: Do not advertise a second Play pre-reg reward if Console only allows one.
7. Delivery QA: Test grant on launch cohort; name the owner.

Facts vs limits

Download the evidence table.

Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.