What is an opt-in prompt?
Used in a sentence: We're firing the opt-in prompt on first launch and losing most users, so let's wait until they set up their first price alert.
How it works
The app calls a system API, and the operating system shows a standard dialog with “Allow” and “Don’t Allow” options. The app controls only the timing and, on iOS, a short explanation string for some permissions.
On iOS, once a user declines, the app cannot ask again; the user must change the setting manually. Recent Android versions also require a runtime permission before an app can send notifications, with their own limits on repeated requests. Because the system prompt is a scarce, one-shot moment, teams decide carefully which screen and event should trigger it.
Example
A stock trading app used to request push permission on first launch, before users had done anything. The team moves the request to the moment a user sets their first price alert. An in-app soft prompt explains that alerts arrive as notifications, and only users who tap “Turn on alerts” see the system dialog. Users who tap “Not now” are asked again after their next alert is set.
OS opt-in prompt vs in-app soft prompt
| OS opt-in prompt | In-app soft prompt | |
|---|---|---|
| Who controls it | The operating system | The app team |
| Design and copy | Fixed | Fully customisable |
| Can be shown again | Limited, once on iOS | As often as rules allow |
The soft prompt explains the value. The system prompt makes it official.
Best practices
- Trigger the request right after an action that notifications would support.
- Use a soft prompt first and show the system dialog only after a yes.
- Never ask on first launch before the user has seen any value.
- Give users who decline an easy path to settings later.
How to do this with Digia Engage
A growth team builds the soft prompt in Digia’s no-code builder and triggers it from events in CleverTap, MoEngage or WebEngage, such as a first order or first alert. A tap on the positive button can hand off to the app’s system permission request, and users who decline can be targeted again later with a separate campaign. The prompt and its timing change without an app release. See the formats on the Nudges product page.
Frequently asked questions
- When should you ask for push permission?
- Ask when the user can see a clear benefit, usually right after an action that notifications would support, such as placing an order, setting a reminder or following a team. Avoid asking on first launch, before the user understands the app. A soft prompt first lets you explain the value in your own words.
- What happens if a user declines the iOS prompt?
- The app cannot show the system prompt again. The user has to open the device settings and enable notifications manually. That is why many apps use an in-app soft prompt first and trigger the system dialog only for users who say yes, keeping the one chance for people likely to accept.
Related terms
Read more
Part of the In-app engagement glossary.