How to Send Custom Push Notifications

1. Overview

Custom Push Notifications let you send real-time, personalized messages directly to your BrandChamps. These messages appear as native push alerts on mobile or desktop, helping you drive instant action for new activities, reward drops, community posts, referral pushes, and more.

This is the fastest way to re-engage active ambassadors, without relying on email or inboxes.


2. Who Can Use This

Requirements:

  • Only BrandChamps who have enabled push notifications through your PWA (Progressive Web App) will receive notifications.
  • Your program must have "Enable app installation prompt for users" toggled on from Settings -> Branding.
  • BrandChamps must have:
    • Installed your PWA
    • Opted into push notifications via browser/device
    • Logged in to the app

📘 Need help setting up PWA? -View the guide on enabling your BrandChamp Mobile App

🔒 Note: This feature is only available on the Pro Plan or higher.


3. What You Can Do With It

  • Send custom messages with a title and body
  • Use dynamic tokens like {{FIRST-NAME}} for personalization
  • Target specific segments using tag filters
  • Redirect users to specific destinations inside your program
  • Preview how the push will look before sending

4. Step-by-Step: Sending a Push Notification

Step 1: Go to the Push Notifications Section

  • Navigate to Communications > Push Notifications
  • Click the Compose button


Step 2: Choose Recipients

  • Click the Recipients dropdown
  • Select one of the following filters:
    • All BrandChamps with push enabled
    • BrandChamps with any of selected tags
    • BrandChamps with all of selected tags
    • BrandChamps with push but without specific tags

💡 Only BrandChamps who have push enabled will appear in the eligible recipient count.

Step 3: Select Navigation Target

  • Use the Navigate To field to select where the user lands when they tap the push
  • Supported destinations include:
    • Home
    • Available Activities
    • Rewards Catalog
    • Pending Rewards
    • Issued Rewards
    • Community Posts
    • Featured Content
    • Referrals
    • User profile
    • Balance & Transaction History

Step 4: Add Title and Message Body

  • Both fields support dynamic tokens like:
    • {{FIRST-NAME}}
    • {{LAST-NAME}}
  • Character limits:
    • Title: 50 characters max
    • Body: Up to 500 characters (we recommend keeping it under 120 for clarity)

💡 Use short, action-oriented copy for best results.


Step 5: Preview the Notification

  • A real-time preview appears as you type
  • Click the “Replace tokens with sample data” checkbox to see how the message will look to recipients

Step 6: Send the Notification

  • Double-check your message and targeting
  • Click Send Notification

⏱️ The notification will be delivered to all eligible BrandChamps who have push enabled on their device.


5. Sent Notification Log

You can view past notifications from the Sent tab.

Each notification includes:

  • To = Number of recipients
  • Targeting = Tag-based targeting criteria
  • Title = Message title
  • Sent At = Sent timestamp
  • Sent by =Admin user

This is useful for auditing campaigns and troubleshooting delivery scope.


6. Best Practices & Tips

  • Use tokens like {{FIRST-NAME}} to personalize content, it improves click-through significantly
  • Keep your messages short and clear
  • Avoid linking to generic destinations like “Home” unless no better option exists
  • Use tag filters (any tag, all tags, without tag) to narrow recipients and reduce noise
  • Push is best used for time-sensitive campaigns like:
    • Limited-time rewards
    • Flash challenges
    • Referral leaderboard pushes

7. Additional Notes & Troubleshooting

  • BrandChamps who haven’t enabled push will not receive the notification
  • Some devices may delay delivery after extended inactivity (varies by OS/browser)
  • Push is only available if your program has PWA enabled with install prompt active
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us