Staying top-of-mind is an age-old advertising strategy to maintain brand awareness with target audiences. Historically, frequency has been a successful play. This includes running ads during peak drive times for radio, buying primetime ad placements on TV, and host-read ads that saturate segment breaks for podcasts. But with the advent of the smartphone, brand awareness reached a new level of engagement. Brands can nudge users with push notifications to stay top of mind with a scheduled cadence.
In a world where brands compete for attention everywhere, from Amazon to the Olympics, strategy is key. So plan your push notifications thoughtfully and ladder them up to broader marketing goals. Here are some best practices for push notifications, along with some common missteps to avoid.
As with any strategic rollout, it’s critical to take a tailored approach to your push notifications. Know your audience and dig for insights to create the most effective messages.
1. Get the message right.
Send notifications for a specific objective and hit all the high notes. Personalize your message by addressing your users by their names, and include contextual information when appropriate. Just be careful not to overdo it. Annoying your users is a one-way ticket to app uninstallation.
It’s also important to keep your notification content on-brand. For example, if your app is a Gen Z-targeted budgeting tool, light humor is appropriate and likely well received by your audience. On the other hand, if your offering is an investment app for brokers, that tone is probably all wrong. Just remember your push notifications are a personal, almost intimate engagement with both your brand and your user. It’s one they will pay attention to, so be sure it’s hitting the right notes.
2. Segment your audience for improved value.
Segmenting users based on need, engagement, and activity ensures your notifications land in front of the right eyeballs at the right time with the right message attached. In addition, segmentation with tailored messaging helps drive personalization. When users receive your notification, they should think, “This is for me.” They are more inclined to open the notification and interact with your brand when they do.
A 2016 study by Econsultancy noted that personalization could improve push notification open rates by an astonishing 800%. Consumers have gotten savvier in the years since, but so have brands. Similar data published in early 2021 show more modest numbers, though no less impressive, with personalization estimated to increase open rates by 400%. Without segmentation, you eliminate personalization and risk losing out on this powerful opportunity.
3. Be punctual.
Timing is everything when it comes to push notifications. Again, if you’re bothering your target audience, you not only risk being ignored but also being deleted. We’re all human here (we think), and looking at the human experience can go a long way in determining the ideal time to send push notifications. What are people doing at the time you are sending your nudge? One study by NotifyVisitors shows that click-through rates were highest for notifications sent in the afternoon until 6:00 p.m., although it also noted different industries have different peak send times. This again highlights the importance of personalization and keeping the human experience in mind.
With a smart plan in place, you will set yourself up for the best chances for success. But, a few missteps can derail even well-organized strategies. Here are a few key ones to avoid.
1. Don’t send too many notifications.
Pestering users will incite action, but it’s not necessarily the kind you want. According to Statista, 39% of users who feel they’ve received too many notifications will turn off notifications from that sender altogether. Push notifications are a gateway to direct interaction with your customers. Don’t blow it by inundating them.
2. Don’t send generic content.
Generic content is typically useless and downright irritating in some cases. Remember, notification content should be personalized, valuable and timely. Sending the same message to everyone about using your app — for no other reason than to have them literally open the app — offers nothing of value. Push sales. Push key communications, Push personal discounts and cart abandons. Don’t push a daily reminder to “Rise and shine and open our app!” Nobody will appreciate that.
3. Don’t create dead-ends.
When you get the click, don’t waste it. If you’re advertising a discount, send users to the sale page. If you’re offering limited-time items, send them directly to product pages. Nothing is more infuriating than opening a notification for a sweet 20% off, only to be taken to the homepage. Instead, create a cohesive journey that leads users down a path you design.
Push notifications are a unique opportunity to be within arm’s reach of your target audience at almost any time of day. But, remember that this access is not unconditional. Customers trust you to treat your relationship with care and consideration; respect their time boundaries and send only information they’ll find valuable.
Need help designing your brand’s push notification strategy? Let’s talk about it.
Featured image by Photo by Robert Katzki on Unsplash.
Get industry insights and news directly to your inbox.
Thank you. Check your email for details on your request.
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
checkForPermission | 10 minutes | This cookie is set by Beeswax to determine whether the user has accepted the cookie consent box. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
__lotl | 5 months 27 days | This cookie is set by Lucky Orange to identify the traffic source URL of the visitor's orginal referrer, if any. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_lo_uid | 2 years | This cookie is set by Lucky Orange as a unique identifier for the visitor. |
_lo_v | 1 year | This cookie is set by Lucky Orange to show the total number of visitor's visits. |
_lorid | 10 minutes | This cookie is set by Lucky Orange to identify the ID of the visitors current recording. |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
IR_gbd | session | Impact Radius sets this cookie to store a unique ID which is used to identify the user's device, when they return to the websites that used the same network. |
Cookie | Duration | Description |
---|---|---|
__qca | 1 year 26 days | The __qca cookie is associated with Quantcast. This anonymous data helps us to better understand users' needs and customize the website accordingly. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_mkto_trk | 2 years | This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo. |
B | 1 year | This Cookie is used by Yahoo to anonymously store data related to user's visits, such as the number of visits, average time spent on the website and what pages have been loaded. This data helps to customize website content to enhance user experience. |
bito | 1 year 1 month | This cookie is set by Beeswax for advertisement purposes. |
bitoIsSecure | 1 year 1 month | Beeswax sets this cookie for targeting and advertising. The cookie is used to serve the user with relevant advertisements based on real time bidding. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
mc | 1 year 1 month | Quantserve sets the mc cookie to anonymously track user behaviour on the website. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
tuuid | 2 years | The tuuid cookie, set by BidSwitch, stores an unique ID to determine what adverts the users have seen if they have visited any of the advertiser's websites. The information is used to decide when and how often users will see a certain banner. |
tuuid_lu | 2 years | This cookie, set by BidSwitch, stores a unique ID to determine what adverts the users have seen while visiting an advertiser's website. This information is then used to understand when and how often users will see a certain banner. |
Cookie | Duration | Description |
---|---|---|
__pdst | 1 year | No description available. |
_an_uid | 7 days | No description available. |
_dc_gtm_UA-61749619-1 | 1 minute | No description |
_dlt | 1 day | No description |
_hjSession_1771567 | 30 minutes | No description |
_hjSessionUser_1771567 | 1 year | No description |
_nx-nocache | session | No description available. |
6suuid | 2 years | No description available. |
A3 | 1 year | No description |
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ | session | No description |
AnalyticsSyncHistory | 1 month | No description |
BIGipServerab44web-nginx-app_https | session | No description |
bounceClientVisit3783c | 30 minutes | No description |
bounceClientVisit3783v | 30 minutes | No description |
dgzsdl08v4 | 10 minutes | No description |
IR_11658 | session | No description |
li_gc | 2 years | No description |
tableau_locale | session | No description available. |
tableau_public_negotiated_locale | session | No description available. |
test | 1 year | No description available. |