A push notification is a message that pops up on a mobile device. App publishers can send them at any time; users don’t have to be in the app or using their devices to receive them. They can do a lot of things; for example, they can show the latest sports scores, get a user to take any action, such as downloading a coupon or let a user know about an event, such as a flash sale.
Push notifications look like SMS text messages and mobile alerts, but they only reach users who have installed your app. Each mobile platform has support for push notifications — iOS, Android, Fire OS, Windows, and BlackBerry all have their own services.
Why are they used?
Push notifications provide convenience and value to app users. For example, users can receive:
- Sports scores and news right on their lock screen
- Utility messages like traffic, weather, and ski snow reports
- Flight check-in, change, and connection information
For app publishers, push notifications are a way to speak directly to a user. They don’t get caught in spam filters, or forgotten in an inbox — click-through rates can be twice as high as email. They can also remind users to use an app, whether the app is open or not. They can also be used to drive actions, such as:
- Promoting products or offers to increase sales
- Improving customer experience
- Converting unknown app users to known customers
- Sending transactional receipts right away
- Driving users to other marketing channels, such as social networks
June 2009: Apple launches Apple Push Notification Service (APNs), the first push service.
May 2010: Google released its own service, Google Cloud to Device Messaging (C2DM).
May 2013: Google introduces “rich notifications”. Rich notifications can contain images, as well as action buttons. Action buttons let users take immediate action from a notification. For example, the user can play a song, open the app, or see more information.
September 2014: Apple added interactive buttons. These buttons allow users to send a response right away to the app publisher. Shortly after, Apple extended push notifications to the Apple Watch.
How do push notifications work?
Some of the actors in sending a push notification include:
- Operating system push notification service (OSPNS). Each mobile operating system (OS), including iOS, Android, Fire OS, Windows, and BlackBerry, has its own service.
- App publisher. The app publisher enables their app with an OSPNS. Then, the publisher uploads the app to the app store.
- Client app. This is an OS-specific app, installed on a user’s device. It receives incoming notifications.
Adding to an app
- The app publisher registers with the OS push notification service.
- The OS service provides an application programming interface (API) to the app publisher. The API is a way for the app to communicate with the service.
- The app publisher adds the SDK to the app. The SDK is a code library specific to the OS’ push notification service.
- The app publisher uploads the app to the app store.
- The user visits an OS app store, downloads, and then installs an app.
- The user opens the app. Unique identifiers (IDs) for both the app and the device, are registered with the OS push notification service.
- The unique identifiers are passed back to the app from the OS push notification service. They are also sent to the app publisher.
- The app publisher receives and stores these registration details, including the unique identifiers.
- The app publisher composes a manual message through a message composer user interface. Or, the publisher sets up an automated message to be sent via the API.
- The publisher defines the audience to whom the push notification will be sent.
- The publisher determines whether the message should be sent immediately or scheduled.
Push notifications can be targeted to segments of your user base, and even personalized for specific app users. This is a major advantage when compared to SMS text messaging. However, they also require the management of user identification data. And they need some kind of interface for writing messages, targeting them and sending them.
Publishers can build this infrastructure themselves, or they can hire a vendor such as Urban Airship to provide it. Increasingly, app publishers pay for these services instead of building them, so that they can focus on building a great app — building and maintaining a cross-platform push notification service takes significant resources and ongoing maintenance. Platform vendors also provide capabilities such as:
- Mobile marketing automation
- User attribute collection and segmentation
- Data management
- Cross-platform support
iOS apps require a user to grant permission for an app to send them to push notifications, while Android and Fire OS do not. Convincing users to opt-in is important for the success of apps on iOS.
The majority of iOS apps show a standard iOS alert when the app is first opened. A better approach is to show the value of opting in — for example, with a customized welcome series upon first open — then let the user opt-in later. Median opt-in rates for iOS range from 58% for charity apps to 33% for games.
High performing apps across all industry verticals (those in the 90th percentile) have opt-in rates above 50%. Travel, business, and charity app opt-in rates lead verticals with rates greater than 70%.
How do push notifications appear to users?
Mainly, users see a notification as a banner or pop-up alert as they are using their phone. This alert is shown no matter what the user is doing.
Most mobile operating systems also show push notifications together in a single view. On iOS, Apple has a Notification Center. The Notification Center is organized in chronological order, and users get to the Notification Center by swiping down from the top of the screen. Android devices show unread messages on the lock screen.
iOS lets users customize push notifications at an individual app level. Users can turn sounds on or off, and pick the style that iOS uses to show a notification. Users can also control the red “badge” showing the number of unread notifications on an app’s home screen icon. Android uses a standard banner approach that users cannot change at an OS level.
Using location with push notifications
All mobile operating systems ask users for their permission to share location information. iOS presents an opt-in alert to users. Android offers location opt-in as part of the app’s permissions setup during installation.
Publishers can deliver more relevant messages by using location data combined with behavioral data. Examples include:
- A home improvement app sends offers for cooling units during a regional hot spell.
- A specialty boutique invites users within 50 miles of an invite-only VIP trunk sale.
- A national sporting goods chain invites local shoppers in for local pro athlete autographs.
Push notifications are a direct path of communication with users. App publishers should treat the ability to communicate with users via push notifications as a privilege, not a right. App publishers must provide value; if they don’t, push notifications will be ignored or turned off. Some users will uninstall the app altogether.
Analytics and measurement are important tools for improving your app’s performance. But it’s important to write compelling push notifications that are valuable to users and that drive action.
Messaging strategies and tactics need to be measured and tested. Strategies such as maximizing opt-in rates, ensuring new users are properly onboarded, and reducing app user churn rates are all key to an app’s success. Other strategies include:
- Matching up each user’s data across channels (web, mobile, store, etc.) to better understand user behavior
- Making it easy for users to share content with their social networks
- Encouraging users to opt-in by offering them incentives and examples of the value your notifications will provide
- Optimize the app experience to keep customers engaged