Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Countly: A guide to using push notifications

625 views

Published on

This guide shows what push notifications is, how to use push notifications, and things to avoid when sending push notifications for better and targeted marketing campaigns

Published in: Data & Analytics
  • Be the first to comment

Countly: A guide to using push notifications

  1. 1. A guide to using push notifications Getting the most out of messaging Countly
  2. 2. Getting Started web: count.ly twitter: @gocountly 2 This guide will give you information about following items: 1. What is a push notification? 2. Why should I use it? 3. What are the newest trends? 4. How do I make sure I benefit from push fully? 5. What are some mistakes done when sending push?
  3. 3. What is a push notification? web: count.ly twitter: @gocountly 3 ● It’s a one-way method of sending (almost any data) to a 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 ● A Countly server is required to send a push notification
  4. 4. So what does a push notification do? web: count.ly twitter: @gocountly 4 ● It can send an alert, e.g showing user that there is something to be acted upon. ● It can send a reminder, e.g there is a todo item waiting. ● It can show user that app has an update. ● It can be used to remind that there is an opportunity, e.g discounted coupon. ● It can be used to tell user that there is a new app feature to check.
  5. 5. Push statistics around the world web: count.ly twitter: @gocountly 5 Number of average opt-ins for push notifications 50% Of people find push notifications are valuable when personal and relevant 70% Faster response time compared to sending email 3X Number of average push notifications opened when sent (iOS) 1-7%
  6. 6. Opting in for push web: count.ly twitter: @gocountly 6 • For iOS, you need a user permission for an app to send them push notifications • For Android, user can receive push notification by default • Later, user can opt-out of getting notifications • iOS device first receives push notification, and then when it’s opened, corresponding application handles it • When Android device receives a push, it’s directly sent to application. • Opt-in rates differ among verticals (e.g 35% for games, 70% for business apps, 50% for charity apps).
  7. 7. iOS vs Android web: count.ly twitter: @gocountly 7 Feature iOS Android Permissions Opt-in required No opt-in Character limits 4 lines for alerts, 2 lines for banners Depends on the device, usually expandable to 8 lines Rich push support Yes Yes Sound support Yes Yes Payload size 2 KB (256B for iOS 7 and lower) 2 KB (using UTF-8) Message queuing Yes (for iOS 10 and later) Yes Interaction buttons At most 2 At most 3
  8. 8. What does Countly push provide? web: count.ly twitter: @gocountly 8 • Send highly targeted push notifications with detailed personal segmentation • Schedule pushes so they are sent at a later time • Preview a push notification before sending • Send a payload (data) so device receives and then does whatever developer intends • Send rich push notifications with text and image • Send a push notification to users at a predefined geolocation • Send actionable push notifications • Analyze all push notifications sent
  9. 9. Best practices for sending push (1) web: count.ly twitter: @gocountly 9 • Push Notifications with Immediate Importance Get the Highest Engagement • Examples: • Updates on road closures, accidents on regular commute routes, etc. (e.g. Waze) • Financial notifications detailing account activity and balances/budgets (e.g. most of today’s banking and credit card apps) • Coupon/limited-time sales offers sent to carefully targeted users (e.g. Groupon)
  10. 10. Best practices for sending push (2) web: count.ly twitter: @gocountly 10 • Don’t Let Your Push Frequency Shove Users Away • Examples: • Periodic recap notifications instead of real-time updates (e.g. SigFig’s weekly stock portfolio updates) • Summaries of social activity tailored to user preferences (e.g. TweetCaster’s customizable notification settings) • Score/challenge updates based on individual user frequency of game play (e.g. Clash of Clan’s updates)
  11. 11. Best practices for sending push (3) web: count.ly twitter: @gocountly 11 • Send timely messages • Examples: • Entertainment notifications during the last hour of the workday (e.g. Netflix) • Weekend event promotions sent out on Thursday or Friday afternoons (e.g. museum and zoo apps) • Travel deal opportunities 4–8 weeks before holiday weekends (e.g. Marriott)
  12. 12. Best practices for sending push (3) web: count.ly twitter: @gocountly 12 • Notify People, Not Devices • Important notes to consider: • Your goal is communicating with people • Personalize your push notifications based on human needs, desires and priorities • Don’t send push based on hoped-for levels of engagement Your goal is to form a fairly intimate connection with your users, such that you’re always in reach no matter where they are or what they’re doing
  13. 13. Best practices for sending push (4) web: count.ly twitter: @gocountly 13 Best time to send a push notification varies by time © Segment.com
  14. 14. web: count.ly twitter: @gocountly 14 DO THIS DON’T DO THIS Send messages timely Send messages when user is sleeping Send spammy messages Send carefully crafted messages Target users by segmenting Bulk send messages to users Limit your messages to 2-3 times a week Send push everyday Send personalized messages Send general messages Obvious mistakes when sending push
  15. 15. Countly https://count.ly

×