Why one switch is not enough
The push notifications guide makes the point in one line: offer notification preferences inside the app, by topic, so a person annoyed by one kind of message can turn that kind off rather than turning off everything. The reason is that the operating system's own control is blunt. A person who wants fewer notifications from an app can switch them off in the device settings, and from then on the app reaches them with nothing, not even the delivery update they were waiting for. The guide also notes that on iOS the system prompt can be shown only once per install, so a permission lost this way is hard to win back.
Topic preferences give the person a finer tool inside the app, where the app can see and honour the choice. They also give the team information it cannot get from a single switch: which kinds of message people are turning off, and how fast. A rising opt-out on one topic is a specific, fixable signal; a falling share of people with notifications on at all is a late and vague one. Where customers object to the total across email, texts and the app rather than to the app alone, the page on customers getting too many marketing messages counts what one person received from every team before a fix is chosen.
The work is mostly organisational rather than technical. Notifications in most apps are sent by several teams through several tools, each of which added its own messages over time. A settings screen that lists topics is easy to draw and useless unless every one of those tools reads it. The steps below start with the inventory for that reason, and end with ownership.
The rules this page relies on are the ones the site's guides state. Apple's App Store Review Guidelines say push notifications must not be required for an app to function and must not be used for marketing unless the person has opted in to receive it, as the push guide states. Firebase's documentation describes Cloud Messaging for push and In-App Messaging for in-session campaigns, as the same guide states; this page makes no claim about any platform's topic or segmentation features. For channels outside the app, the SMS and WhatsApp automation guide sets out, from the ICO's direct marketing guidance, that consent is specific to what the person agreed to and each channel's consent is separate. All of this is educational guidance rather than legal advice; check the rules for each market with whoever advises the business.
Before you start
Gather four things. First, a list of everyone who can send a push or in-app messageA message shown inside an app during a session the person started, such as a banner, modal or tooltip, needing no operating-system permission.: product, marketing, customer service, operations and any team that owns an automated journey. Second, read access to each sending tool, or an export of its active campaigns and journeys, so the inventory comes from what is live rather than from memory. Third, the current settings screen, if there is one, and the code or configuration that decides whether a message sends to a given person. Fourth, the analytics events that record notification permission and any existing preference changes, so the last step has a baseline.
Agree a working definition of the two classes before sorting anything. A transactional notification is caused by the person's own action or account and would still be needed if every word of marketing were removed: an order update, a booking confirmation, a reply to their message, a security alert. A promotional notification exists to prompt activity or a sale. The promotional vs transactional email comparison sets out where the line sits for email, including the hard cases, and the same test works for push.
The steps
List every notification each team sends
Build one table with a row per notification: its name, the team that sends it, the tool it is sent from, the trigger or schedule, the audience, and a sample of the wording. Include in-app messages that persist, such as inbox cards, because they belong in the same settings. The automation governance guide calls this the workflow inventory and treats it as the base of every other control; most teams find messages here that nobody remembers approving.
Classify each as transactional or promotional
Mark every row with one class, using the test agreed before you started: what would be left if the promotional content were removed? Where a message carries both, such as an order update with a suggestion attached, treat it as promotional for preference purposes or strip the promotion out. Where a row is unclear, the comparison guide's advice holds: the safer classification is promotional.
Group them into topics people recognise
Group the rows into a small number of topics named in the person's language, not the team's: "Your orders" rather than "Fulfilment events", "People you follow" rather than "Social graph activity", "Offers" rather than "CRM campaigns". Each topic should be a kind of message a person might reasonably want to treat differently from the others. Keep transactional and promotional messages in separate topics, so turning off offers never turns off anything the person needs. Merge any topic nobody would switch separately.
Set the defaults
Decide each topic's starting state for a person who has just allowed notifications. Transactional topics can start on, because they are the reason most people allow notifications at all. Promotional topics start off unless the person chose them, because Apple's guidelines require an opt-in before push is used for marketing, as the push guide states. If the soft prompt that comes before the system permission names offers as one of the things the person will receive and they agree, record that as their choice for the offers topic. Write the defaults down with the reason for each.
Build the settings screen
Lay out one screen with a switch per topic, a one-line description of what each topic sends, and an example where the name alone could mislead. Changes should apply immediately, need no extra sign-in, and show a short confirmation. The list building and consent guide gives the same rules for an email preference centre: offer only preferences the team will act on, keep the options few, and treat a lower-volume choice as real. If the device-level permission is off, say so on this screen and explain how to turn it back on, rather than showing switches that do nothing.
Link it from prompts and messages
Make the screen easy to reach from the places a person decides they have had enough. Link it from the soft prompt ("you can choose what we send in settings"), from the in-app inbox, from the account menu, and where the tool allows, from the notification itself or the screen it opens. Then make sure every message is filed under the right topic, so a person who goes to adjust their settings finds the switch for the message they just received; the tutorial on writing push notifications includes that check before each send.
Make every sending tool read the same preferences
Store the preferences in one place and have every tool that sends push or in-app messages check them before each send, not only when a person enters a journey, because preferences change mid-sequence. Apply the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. in the same check, so a person who asked for no contact is never reached by a tool that missed the update. Then test it: switch a topic off on a test account and trigger a message from every tool in the inventory. A tool that still sends is the reason most preference centres lose trust.
Keep transactional messages outside promotional caps
The push guide sets a frequencyAverage times a person saw an ad. cap per person per period across every campaign, with transactional messagesAn email triggered by a person's own action or account, such as a receipt, password reset or shipping notice, rather than a marketing send. outside it and promotional messages at the bottom of the priority order. Apply that to topics: an order update should never be held back because a person has received their share of offers this week, and an offer should never send in place of an order update. Record which topics count towards the cap so the rule survives the next person who builds a campaign.
Name an owner for each topic
Give each topic one accountable owner who approves new messages into it, keeps its description true, and watches its opt-outs. A RACI matrix for the topics makes the roles explicit: who is responsible for sending, who is accountable for the topic, who must be consulted before a new message joins it, and who is informed of changes. Without an owner, topics drift: a promotional message gets added to "Your orders" because that topic has the most people switched on.
Track topic opt-outs and the enabled rate
Record every preference change as an event with the topic and the screen it came from, and report two things over time. The opt-out trend by topic shows which kind of message people are tiring of; a rise after a new campaign points at that campaign. The share of active users with notifications enabled at the device level, alongside the push opt-in rateShare of app users shown the notification permission prompt who allowed notifications. for new installs, shows whether the topics are doing their job: people should be turning off a topic instead of turning off everything. Review both at a set interval with the topic owners, and read small movements with caution.
A starting structure for the topics. The names and contents are examples; your inventory decides the real ones.
| Topic (as the person sees it) | Class | Default after permission | Counts towards promotional cap | Typical owner |
|---|---|---|---|---|
| Your orders or bookings | Transactional | On | No | Operations |
| Your account and security | Transactional | On, and not switchable where the message is essential | No | Product |
| Replies and activity on your content | Transactional | On | No | Product |
| Things you saved or follow | Promotional (requested) | Off until the person follows or saves something | Yes | Product or marketing |
| News and features | Promotional | Off unless chosen | Yes | Product marketing |
| Offers | Promotional | Off unless chosen | Yes | Marketing |
These are push and in-app topics only. Email and SMS preferences sit alongside them, each with its own consent record, and the comparison of SMS and push explains which messages belong on which channel so the topics stay consistent across both.
An event ticketing app's notification settings (illustrative)
Hullabun Tickets splits its single switch
Hullabun Tickets, an invented event ticketing app, has one notification switch and 4 teams sending through 3 tools. Its inventory finds 23 live notifications, 9 transactional and 14 promotional, including a "you might like" push the operations team had added to the ticket-delivery journey. Hullabun groups them into 4 topics: order updates, artists you follow, venue news and offers. Order updates start on; artists you follow starts on only once a person follows an artist; venue news and offers start off unless chosen on the soft prompt. It moves the "you might like" push into offers and gives each topic an owner. In the quarter before the change, 2.4% of active users a month turned off notifications at the device level. In the quarter after, that falls to 1.1%, while 6.8% a month switch off the offers topic and fewer than 1% switch off any other. Ticket-delivery pushes, which used to be lost with every device-level opt-out, now reach almost everyone who bought a ticket. One tool kept sending offers to people who had turned them off for 2 weeks before the test account caught it, which is why the team now runs that test after every release.
The mobile messaging hub sets preferences beside the rest of the channel, and the push guide covers the permission prompt that comes before any of these topics.
When the share of existing users with notifications on is already falling, the diagnosis of users turning off app notifications locates the fall by message, team, topic and hour before any of these steps is chosen as the fix.
Common mistakes
- One switch for everything. A person annoyed by promotions loses order updates too. Offer topics, with transactional and promotional messages kept apart.
- Topics named after teams. "CRM" and "Lifecycle" mean nothing to the person choosing. Name topics in their language, with a one-line description.
- Promotional topics on by default without a choice. Apple's guidelines require opt-in before push is used for marketing. Start offers off unless the person chose them.
- Preferences only one tool reads. A switch that another team's tool ignores is worse than no switch. Store preferences once and check them before every send.
- Treating a push topic as consent for other channels. Email and SMS consent is separate and specific. Never use an app setting as permission to text or email.
- Marketing hidden inside transactional topics. Adding offers to the topic everyone keeps on destroys trust in the whole screen. Give each topic an owner who approves new messages into it.
- No measurement. Without topic opt-out events, the team cannot tell which messages are wearing people out. Record every change with its topic and source.
