# Guideline 4.5.4 - Design: Push Notifications Required to Function or Used for Marketing Without Opt-In

**Guideline:** 4.5.4 · **Store:** Apple App Store · **Severity:** medium · **Fix difficulty:** easy · **Typical turnaround:** 2-8 hours

Canonical URL: https://appstorereject.com/rejections/apple/4/guideline-454-design-push-notifications-required-to-function-or-used-for-marketing-without-opt-in

## Description

Apple is rejecting your app because it either requires push notifications to function (gating core features behind the notification permission) or uses push notifications for marketing without proper consent. Guideline 4.5.4 states that push notifications must not be required for the app to function and must not be used for marketing without opt-in. The most common trigger is apps that show a blocking screen if the user declines push notification permission — 'Enable notifications to continue using the app.' Apple considers this coercive. Users must be able to fully use your app regardless of their notification preference. The second trigger is sending marketing or re-engagement push notifications to users who only consented to transactional notifications. Just because a user tapped 'Allow' on the iOS notification prompt doesn't mean they agreed to receive your weekly deals blast. The fastest compliant path is to make push notifications entirely optional — the app must work fully without them — and to implement separate opt-in for any marketing or promotional notification content.

## Common variations

- App requires push notifications to function
- Core features gated behind notification permission
- User cannot proceed without enabling notifications
- Push notifications used for marketing without explicit consent
- App blocks functionality when notifications are declined

## Example rejection email

```
Guideline 4.5.4 - Design - Apple Sites and Services

Your app requires users to enable push notifications in order to access its core features. Push notifications should not be required for an app to function, and users who decline push notification permission must still be able to use the app's full functionality.

Additionally, push notifications must not be used for marketing purposes without the user's explicit consent.

Next Steps:
Please revise your app so that:
- Push notifications are not required to use the app
- All core features remain accessible if the user declines notifications
- Any marketing notifications have a separate, explicit opt-in mechanism
```

## Resolution steps

## Quick Assessment
- **Risk level:** Medium
- **Resolution path:** Remove notification gating and add marketing opt-in
- **Typical turnaround:** 2-8 hours

## The Fix

01. **Remove notification gating** — Delete any blocking screen, modal, or flow that prevents the user from using the app if they decline push notifications. Users must reach all core functionality regardless of notification permission.

02. **Make the permission request contextual** — Instead of requesting notification permission on first launch, request it when the user takes an action that would benefit from notifications (e.g., placing an order, setting a reminder). This is also better for opt-in rates.

03. **Provide fallback for notification-dependent features** — If certain features rely on push (like real-time alerts), provide an in-app alternative: polling, in-app notification center, or badge-based updates.

04. **Separate marketing consent** — Create a distinct opt-in for marketing notifications that is separate from the iOS system notification permission. Don't treat system-level 'Allow' as blanket consent for promotional content.

05. **Handle the declined state gracefully** — If the user declined notifications, don't repeatedly nag them. Show a non-blocking, dismissible banner at most once per session explaining what they're missing.

## Prevention
- Never gate any feature behind notification permission
- Request notification permission contextually, not on first launch
- Implement an in-app notification center as a fallback
- Separate transactional and marketing notification consent
- Test the full app experience with notifications disabled

## Appeal guidance

Appeal only if the reviewer misidentified optional notification prompts as mandatory gating. Show that users can dismiss the prompt and access all features. If the app truly blocks functionality without notifications, fix and resubmit.

## Before / after examples

**Before:** App shows a full-screen modal on first launch saying 'Enable notifications to get started' with only an 'Enable' button — no way to skip or dismiss
**After:** App opens directly to the main screen; notification permission is requested after the user places their first order ('Get updates on your order?') with a clear 'Not Now' option that proceeds to the full app experience
**Why it works:** Push notification permission must be optional and contextual. The app must be fully functional without it.

## Common questions

**Can you appeal a 4.5.4 rejection?**

Appeal only if the reviewer misidentified optional notification prompts as mandatory gating. Show that users can dismiss the prompt and access all features. If the app truly blocks functionality without notifications, fix and resubmit.

**How long does this typically take to fix?**

Typical turnaround is 2-8 hours (difficulty: easy). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-454-design-push-notifications-required-to-function-or-used-for-marketing-without-opt-in*