Best practices on push notifications

Posted on by


Push notifications are one of the most valuable things we offer our customers. Instead of having to send expensive SMS messages to reach people, push notifications are free, relevant (users opt in first by downloading the app, and then by accepting to receive push), and geo targeted down to a mile radius around any address in the world.

Here’s how to make the most of them:

Location, location, location.

You’ve heard “location” a million times as the killer mobile feature, and it is. Don’t just reach your audience when you want to. Reach them where it’s relevant for them. For musicians, this could be during a show. For a conference, perhaps right before the big keynote starts. For a hotel, as a guest enters the building.

push notifications by map

We give our customers three ways to send targeted push notifications:

Blasting your entire audience can be useful when you have a general announcement. Using an address/radius is useful when you want to target people around a specific venue. And using our Map feature, you can draw a box around an area – a city block or an entire country.

Don’t be shy.

Customers many times are worried about “bothering” their audience. Don’t be. They downloaded your app for a reason. They want to hear from you, especially offers that give them exclusive content, a discount, or exclusive access. We recommend sending a relevant message at least once a week.

Use our rewards system.

Don’t just message your users – offer them things in exchange for interacting. Using our rewards system, you can message users, challenge them to do something (virtual or real) and get a reward (virtual or real). For example, you could tell fans to post a photo at a show and unlock a free track from the artist. Or, you could instruct hotel patrons to “check in” using Foursquare or Facebook Places and get a coupon for a free coffee. The possibilities are limitless.

Deep link to content.

When sending a push, users will see the message along with “slide to view” to open the app. Don’t waste this call to action – link it to content that’s relevant to the push message. For example, if you’re trying to sell tickets to a show in Los Angeles, deep link the push message to the exact page in the app for the show – this will open the app directly on that page. Fans won’t have to search to find the show, resulting in a higher conversion.

Some don’ts.

Don’t put a link to a website within the push. User’s can’t copy and paste it, and the whole point of a push is to draw them into the app. If you want to link to a website, use our URL system to “target” the push to a link. It will open the link inside the app.

Don’t just reference offline events. It’s great to tell fans to “watch a show on TV” or “vote for an award” but it’s better to pull them into the app to do the action or view a news post on the event. Remember to connect push notifications to content in the app.

In conclusion.

Send relevant, targeted push notifications often and engage with your audience. Smart use of this system results in higher engagement, retention, and virality, not to mention – transactions!

6 thoughts on “Best practices on push notifications

  1. Thanks for this blog. It really keeps your mind on track with my app on what i can and should do. I’ve added the moro rss feed to my island in PARADISE World. Now i can check the latest post whenever i log in.

    Keep the news coming.

  2. Pingback: Consejos de Mobile Roadie para el iPhone .:. Aliado Digital

  3. How can my audience communicate exactly their position if I have to send target push notification? through the CAP? or through their last shared position?

  4. Hi Kikko,

    In response to your question: When you need to send targeted push notifications, your audience can communicate their position through their last shared position. Hope that helps! If you have any more questions, don’t hesitate to ask.

  5. Hey Conrad,

    Thanks! Glad you’re enjoying the blog so far. More blog posts to come!

Leave a Reply

Your email address will not be published. Required fields are marked *