App Store Marketing Weekly – Week 11 (2026)
This week: age assurance is spreading, promo-code workflows are changing, and retention UX is now getting reviewed like a store page.
Summary
This week’s theme: operational details are becoming growth constraints.
- Age assurance requirements are no longer a “somewhere else” problem. They can change who can download, and when.
- Apple’s shift from promo codes to offer codes is a reminder that store tooling changes can break your partnerships and support playbooks if you ignore them.
- Retention and monetization UX is getting treated like a policy surface (and review risk is real).
The useful stuff (with sources)
1) Texas SB2420: age assurance requirements (and why privacy-preserving implementation matters)
Primary source:
- Apple Developer News: https://developer.apple.com/news/?id=btkirlj8
What it changes:
- If you distribute in Texas, “under 18” accounts are pushed into Family Sharing, and parents/guardians provide consent for downloads and IAP.
- Developers are expected to adopt new capabilities (Declared Age Range, “significant change” flows) as laws roll through multiple states.
2) App Store Connect marketing ops: offer codes overtake IAP promo codes
Primary source:
- Apple Developer News: https://developer.apple.com/news/?id=gf6mgrs6
What it changes:
- March 26, 2026: you can’t create IAP promo codes anymore. If you rely on them for partner promos, influencer kits, or “make good” support, you need a migration plan.
- CPP scale and discoverability keeps improving, which means “store ops” is now a real iteration cadence, not occasional admin.
3) Exit offers: conversion lever, but iOS App Review can flag it as manipulation
Good practitioner coverage:
What it changes:
- Exit offers can work, but iOS rejections referencing Guideline 5.6 are being reported.
- Treat the UX as something you may have to defend (honest copy, clear choice, no dark patterns).
4) Lifecycle in 2026: channel complexity is not an excuse for noisy messaging
Good practitioner coverage:
What it changes:
- RCS/SMS richness and consent realities push teams toward fewer, higher-intent moments.
- The best lifecycle programs behave like systems (signals → orchestration → measurement), not calendars.
What we’d do next (tiny wins)
- Distribution/policy: list your “download eligibility” risks by market (Texas, AU/BR/SG 18+ flows, EU terms), then assign one owner + one checklist per risk.
- Store ops: inventory every place you generate promo codes today (support, partnerships, PR), and decide what becomes offer codes vs another workaround.
- Retention: if you want to test exit offers, start Android-first, then write your iOS “review defense” note before you ship.
Editor: App Store Marketing Editorial Team
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.