Skip to main content
Push notifications deliver real-time messages directly to customers’ devices. They’re ideal for time-sensitive alerts, re-engagement, and driving app usage.

​
Push Capabilities

FeatureSupported
Title and body✅
Custom icons✅
Deep links✅
Rich mediaLimited
Action buttons✅
Silent push✅

​
Understanding Push Notifications

​
How Push Works

  1. Your app registers for push notifications
  2. Device provides a push token
  3. Token is sent to RevBridge AI
  4. Campaigns target tokens with messages
  5. Push service delivers to device

​
Push Services

PlatformService
iOSApple Push Notification service (APNs)
AndroidFirebase Cloud Messaging (FCM)
WebWeb Push (via service workers)

​
Setting Up Push

Navigate to Settings → Channels and click Configure next to Push.

​
Prerequisites

  • Mobile app with push notification support
  • Firebase project (for Android)
  • Apple Developer account (for iOS)
  • Server key and credentials

​
Configuration Steps

1

Configure Firebase

Add your Firebase server key for Android
2

Configure APNs

Upload your Apple push certificate or key
3

Integrate SDK

Add RevBridge SDK to your mobile app
4

Register Tokens

Ensure app sends push tokens to RevBridge
5

Test Delivery

Send a test push notification

​
Firebase Setup (Android)

  1. Go to Firebase Console
  2. Navigate to Project Settings → Cloud Messaging
  3. Copy Server Key
  4. Paste in RevBridge Push settings

​
APNs Setup (iOS)

Option 1: Push Certificate
  1. Generate in Apple Developer portal
  2. Download .p12 file
  3. Upload to RevBridge
Option 2: Auth Key (Recommended)
  1. Generate Key ID in Apple Developer portal
  2. Download .p8 key file
  3. Upload to RevBridge with Team ID and Key ID

​
Push Notification Structure

​
Components

ComponentPlatformLimits
TitleBoth~50 characters visible
BodyBoth~150 characters visible
IconAndroidApp icon default
ImageBothRich notification
SoundBothCustom or default
BadgeiOSNumber on app icon

​
Example Notification

{
  "title": "Flash Sale: 50% Off",
  "body": "24 hours only! Shop now before it's gone.",
  "icon": "sale_icon",
  "data": {
    "deep_link": "myapp://sale"
  }
}

​
Push Best Practices

​
Crafting Effective Notifications

ElementBest Practice
TitleClear, action-oriented, under 50 chars
BodySpecific value, urgency, under 150 chars
TimingRelevant to user’s time zone and activity
FrequencyDon’t overwhelm (1-3 per day max)

​
Title Tips

  • Front-load important information
  • Use action verbs
  • Create urgency when appropriate
  • Avoid clickbait
Examples:
  • ✅ “Your order shipped!”
  • ✅ “Flash sale ends in 2 hours”
  • ❌ “You won’t believe this deal!”
  • ❌ “Tap to see amazing news”

​
Body Tips

  • Expand on the title
  • Include specific details
  • Clear call to action
  • Personalize when possible

​
Timing and Frequency

GuidelineRecommendation
Daily limit1-3 notifications
Weekly limit5-10 notifications
Best timesMid-morning, early evening
AvoidLate night, early morning
Excessive push notifications are the #1 reason users disable notifications or uninstall apps.

​
Deep Linking

Always include deep links to:
  • Take users directly to relevant content
  • Reduce friction between notification and action
  • Track conversion accurately
myapp://products/123
myapp://cart
myapp://offers/flash-sale

​
Permission and Opt-In

​
iOS Permission

iOS requires explicit permission to send notifications:
  • Prompt at the right moment (not immediately at install)
  • Explain the value of notifications
  • Respect user’s choice
Wait until users experience app value before requesting notification permission. Cold prompts have low acceptance rates.

​
Android Behavior

Android 13+ requires explicit permission (similar to iOS). Earlier versions allow by default but users can disable.

​
Managing Preferences

Allow granular control:
  • Promotional notifications
  • Order updates
  • Reminders
  • Social notifications
Respecting preferences improves retention.

​
Notification Types

​
Transactional

Non-promotional, expected notifications:
  • Order confirmations
  • Shipping updates
  • Appointment reminders
  • Security alerts

​
Marketing

Promotional notifications:
  • Sales and offers
  • New products
  • Re-engagement
  • Recommendations
Some platforms treat transactional and marketing notifications differently. Transactional typically has higher priority.

​
Silent Push

Background updates without visible notification:
  • Refresh content
  • Update badges
  • Sync data

​
Analytics

Track push performance:
MetricDescription
SentNotifications dispatched
DeliveredReached device
OpenedUser tapped notification
DismissedUser swiped away
ConvertedCompleted goal action

​
Platform Differences

MetriciOSAndroid
Delivery confirmation✅✅
Open tracking✅✅
Dismiss tracking❌✅

​
Use Cases

​
Price Drop Alert

Title: Price Drop Alert 📉
Body: Sony headphones just dropped to $79 (was $149). Limited stock!
Deep Link: myapp://products/sony-headphones

​
Abandoned Cart

Title: Still thinking it over?
Body: Your cart is waiting with {{item_name}}. Complete checkout now!
Deep Link: myapp://cart

​
Back in Stock

Title: It's back! ✨
Body: {{product_name}} is back in stock. Get it before it sells out again!
Deep Link: myapp://products/{{product_id}}

​
Order Update

Title: Your order is out for delivery 🚚
Body: Order #{{order_id}} arriving today by {{time}}
Deep Link: myapp://orders/{{order_id}}

​
Re-engagement

Title: We miss you! 👋
Body: It's been a while. Here's 20% off your next purchase.
Deep Link: myapp://offers/comeback

​
Troubleshooting

​
Notifications Not Delivering

  1. Verify push credentials
  2. Check token registration
  3. Confirm user has notifications enabled
  4. Review platform-specific issues

​
Low Open Rates

  1. Review notification content
  2. Check timing and frequency
  3. Ensure relevance
  4. Test different approaches

​
High Opt-Out Rate

  1. Reduce frequency
  2. Improve content relevance
  3. Allow preference management
  4. Survey users for feedback

​
Token Issues

Push tokens can become invalid when:
  • App is uninstalled
  • User disables notifications
  • Device is factory reset
  • Token expires (rare)
Regularly clean invalid tokens to maintain delivery accuracy.