Push Notification Delivery Time
Overview
When you send a push notification to your customers, you naturally want to know how quickly they'll receive it. Understanding push notification delivery helps you set realistic expectations and plan your engagement strategy effectively.
Key facts about delivery:
Typical delivery time: 20-30 seconds under normal conditions
Can be as fast as 5 seconds with optimal connectivity
May take up to 30 minutes in poor conditions
Delivery is handled by Apple (APNS) and Google (FCM), not by Perkstar
Both systems operate on a "best effort" basis without guaranteed delivery times
Push notifications are designed for timely communication, but they're not instant messaging. Several factors beyond Perkstar's control can affect when (or if) customers receive your messages.
Typical Delivery Times
Optimal Conditions
When everything is ideal:
5-30 seconds - Most common delivery window
Customer's device is on and connected to Wi-Fi or mobile data
Device has good signal strength
Customer is not actively using the loyalty card app
Device battery is not in power-saving mode
This represents the majority of notifications you send to an engaged customer base with modern devices and reliable connectivity.
Real-World Conditions
Average delivery time across all scenarios:
20-30 seconds - Typical real-world performance
Accounts for varying network conditions
Includes customers on mobile data vs. Wi-Fi
Considers different device states and settings
Extended delivery scenarios:
Up to 30 minutes - Can occur with poor connectivity or device limitations
Delayed indefinitely - If device is offline, notification queues until device reconnects
When Notifications May Be Delayed
Push notifications can experience delays due to:
Network issues:
Poor mobile signal strength
Unstable Wi-Fi connection
Network congestion during peak hours
Firewall restrictions blocking notification ports
Device state:
Phone in power-saving or battery optimization mode
Device in Do Not Disturb mode (may silence but still deliver)
App or browser in deep sleep state
Device storage nearly full
Platform load:
High volume periods on Apple or Google's notification servers
Regional server maintenance
System updates affecting notification services
How Apple and Google Handle Push Notifications
Push notification delivery is managed entirely by Apple Push Notification Service (APNS) for iOS devices and Firebase Cloud Messaging (FCM) for Android devices. Perkstar sends the notification to these services, which then handle delivery to customer devices.
Apple Push Notification Service (APNS)
How it works:
Perkstar sends notification to Apple's servers
APNS queues the notification for delivery
APNS attempts to deliver to the customer's iPhone
If successful, notification appears on device
If device is offline, APNS holds the notification temporarily
APNS characteristics:
"Best effort" delivery - No guaranteed delivery time
Single notification storage - Only stores the most recent notification per app
Time-limited queuing - If device doesn't come online within a certain timeframe, notification is discarded
Priority levels - High-priority notifications attempt immediate delivery; lower priority may batch with others
Apple's control over delivery:
When notifications appear on lock screen
Whether notifications trigger while card is open
Battery optimization affecting delivery timing
Background app refresh settings
Firebase Cloud Messaging (FCM) - Android
How it works:
Perkstar sends notification to Google's servers
FCM processes and routes the notification
FCM delivers to the customer's Android device
Notification appears in notification panel
If device is offline, FCM queues for later delivery
FCM characteristics:
"Best effort" delivery - Similar to APNS, no guarantees
Time-to-live settings - Notifications can be set to expire after a certain period
Device battery optimization - Android's Doze mode can delay notifications
Adaptive delivery - May batch low-priority notifications to save battery
Google's control over delivery:
Background data restrictions
Battery optimization policies
Doze mode behaviour
App standby buckets (frequency limits for inactive apps)
What This Means for Your Business
You cannot control:
❌ Exact delivery timing to customer devices
❌ Whether notification appears while customer has card open
❌ Apple and Google's battery optimization behaviours
❌ Customer device settings that affect delivery
❌ Network connectivity issues on customer's end
You can control:
✅ When you send notifications from Perkstar
✅ Message content and relevance
✅ Notification frequency to avoid overwhelming customers
✅ Timing strategy (send during likely-online hours)
✅ Segmentation to target engaged customers
Checking if Notifications Were Delivered
You can verify whether a customer's device received and processed a push notification, even if you don't know exactly when they saw it.
Using Latest Updates Section
To check delivery status:
Navigate to the Customers section in your Perkstar dashboard
Open the specific customer's profile
View their loyalty card
Scroll to the "Latest Updates" section on the card
What you'll see:
If the notification was delivered and processed:
✅ Your message appears in the Latest Updates section
✅ Shows the timestamp when the device processed it
✅ Indicates the notification reached the customer's phone
If the notification hasn't been processed yet:
❌ Message doesn't appear in Latest Updates
❌ Device may be offline or experiencing delivery delays
❌ Notification may be queued by APNS or FCM
Important: The Latest Updates section shows when the device processed the notification, not necessarily when the customer viewed or acted on it. A customer may receive the notification but not open or read it.
Understanding Latest Updates Timestamps
The timestamp indicates:
When the customer's device received and acknowledged the notification
When the card data was updated on the device
Successful delivery through APNS or FCM
The timestamp does NOT indicate:
When the customer saw the notification on their lock screen
Whether the customer opened or read the notification
When the customer took action based on the notification
Card Preview Limitations
Push Notifications Don't Work in Preview Mode
Important: Card preview features are for design testing only and do not receive actual push notifications.
What card preview is for:
Viewing how your card design looks on mobile devices
Testing colour schemes, logos, and layouts
Checking text formatting and field placement
Previewing card appearance before finalizing
What card preview cannot do:
❌ Receive push notifications
❌ Test notification delivery
❌ Demonstrate notification timing
❌ Show real-time updates
Testing Push Notifications Properly
To test actual notification delivery:
Issue a real card to a test customer profile (yourself or a staff member)
Install the card on a physical device (iPhone or Android)
Enable notifications for the card
Trigger a notification (make a test transaction, send a manual push, etc.)
Wait for delivery and verify appearance on the device
Check Latest Updates on the customer's card in your dashboard
Do not rely on preview features for testing notifications—only real cards installed on actual devices will receive push notifications.
Factors Affecting Delivery Speed
Device Connectivity
Optimal connectivity:
Strong Wi-Fi connection (preferred)
Good mobile data signal (4G/5G)
No firewall restrictions
Low network congestion
Poor connectivity:
Weak or intermittent signal
Network switching (Wi-Fi to mobile data)
Public Wi-Fi with port restrictions
Airplane mode or offline status
Impact: Connectivity is the single biggest factor in delivery speed. A device with no internet connection cannot receive notifications until it reconnects.
Device State and Settings
Favourable states:
Device powered on and unlocked
Background app refresh enabled
Notifications enabled for Wallet (iOS) or browser (Android)
Battery sufficient (not in critical low-power mode)
Unfavourable states:
Device powered off
Extreme battery saver mode active
Background data restricted
App or browser closed and not allowed to run in background
Device in Doze mode (Android)
Impact: Devices in power-saving states may delay notification delivery significantly to conserve battery.
Customer Behaviour
Notification may not trigger when:
Customer is actively viewing their loyalty card
Customer is mid-transaction
Wallet app (iOS) or browser (Android) is in the foreground
Why: Both Apple and Google may suppress notifications for apps currently in use to avoid disrupting the user experience. This is by design and cannot be overridden.
Solution: The notification will appear when the customer closes the app or switches to a different screen. The information is still delivered; the visual notification is simply delayed.
Time of Day
Faster delivery periods:
Business hours (9am-5pm) when most customers are active
Early evening (6pm-9pm) when mobile usage peaks
Times when customers typically have strong connectivity
Slower delivery periods:
Late night/early morning when devices may be in deep sleep
Commute times when customers switch between networks
Peak usage hours when notification servers are under heavy load
Strategy: Schedule non-urgent notifications during high-connectivity periods for optimal delivery rates.
Geographic and Regional Factors
Variables by region:
Network infrastructure quality
Mobile carrier reliability
Internet penetration rates
Device age and update status
International considerations:
Roaming customers may experience delays
Different carriers have varying notification service agreements
Some countries have network restrictions that affect push services
Best Practices for Reliable Delivery
Optimize Sending Strategy
Timing recommendations:
Do:
✅ Send during business hours when customers are likely online
✅ Schedule birthday notifications during daytime hours
✅ Send reminders during high-activity periods
✅ Batch less urgent messages to avoid server congestion
Avoid:
❌ Sending notifications between midnight and 6am (poor connectivity, Do Not Disturb)
❌ Sending multiple notifications within minutes of each other
❌ Scheduling all notifications for the same time (creates server load)
Set Realistic Expectations
Communicate delivery timelines to your team:
Notifications typically arrive within 30 seconds
Some customers may experience delays up to 30 minutes
Offline devices won't receive notifications until they reconnect
Not all customers may receive notifications (device settings, connectivity issues)
Don't use push notifications for:
Time-critical communications requiring instant delivery
Security alerts or emergency notifications
Transactional confirmations that must be immediate
Any scenario where guaranteed delivery is essential
Do use push notifications for:
✅ Loyalty programme updates and reminders
✅ Marketing promotions and special offers
✅ Birthday wishes and milestone celebrations
✅ Encouraging repeat visits
✅ Reward availability notifications
Monitor and Respond to Delivery Issues
Track metrics:
Percentage of notifications delivered successfully
Average time between sending and Latest Updates timestamp
Customers who consistently don't receive notifications
Time periods with higher delivery delays
Take action:
Follow up with email or SMS for important announcements
Investigate customers who never receive notifications (check their card installation status)
Adjust sending times if you notice patterns in delivery delays
Offer alternative communication channels for time-sensitive information
Why Guaranteed Instant Delivery Isn't Possible
Technical Limitations
Apple and Google's approach:
Both platforms prioritize device battery life over instant delivery
Notifications are intentionally delayed during low-battery states
Background processes are restricted to improve performance
Networks may batch notifications to reduce bandwidth usage
Infrastructure constraints:
Millions of devices receiving notifications simultaneously
Server capacity limits during peak times
Network routing and congestion
Distance between notification servers and customer devices
Privacy and User Experience Design
Platform priorities:
Preventing notification spam and harassment
Giving users control over when and how they're interrupted
Balancing timely delivery with battery conservation
Protecting user privacy by not forcing always-on connectivity
By design:
Users can disable notifications entirely
Devices can enter Do Not Disturb mode
Battery optimisation can delay notifications
Apps in use may suppress incoming notifications
"Best Effort" Service Model
What "best effort" means:
Platforms attempt to deliver as quickly as possible
No service-level agreements or guaranteed delivery times
Delivery prioritised based on device state and notification importance
Some notifications may never be delivered if conditions prevent it
This is industry standard across all push notification services, not unique to loyalty programmes or Perkstar.
Alternative Communication Strategies
When to Use Email Instead
Email is better for:
Detailed programme announcements
Information customers need to reference later
Content requiring more than a sentence or two
Communications to customers who disabled push notifications
Important updates where delivery confirmation is needed
Email delivery characteristics:
More reliable delivery (less dependent on device state)
Customers can read at their convenience
Easier to include detailed information and links
Better for archived reference materials
When to Use SMS Instead
SMS is better for:
Urgent communications requiring faster attention than push
Customers without cards installed
Critical account or transaction confirmations
Two-factor authentication or security alerts
Higher open rates than push for time-sensitive offers
SMS delivery characteristics:
Generally more reliable than push notifications
Works even when data/Wi-Fi is unavailable (if voice service is active)
Higher visibility and open rates
More expensive than push notifications
Multi-Channel Approach
For maximum reach:
Tier 1 - Most important messages:
Send via push notification + email + SMS
Example: Birthday offers with limited validity
Tier 2 - Important but not urgent:
Send via push notification + email
Example: Monthly programme updates, new rewards available
Tier 3 - Routine updates:
Send via push notification only
Example: Transaction confirmations, progress updates
This ensures critical messages reach customers even if push notifications are delayed or not received.
Troubleshooting Delivery Issues
"Customer says they never received notification"
Check these factors:
1. Card installation status:
Is the card actually installed on their device?
Have they removed it since it was issued?
2. Notification settings:
iOS: Did they enable Wallet notifications?
Android: Did they enable notifications in the card menu?
3. Latest Updates section:
Does it show the notification was processed?
If yes, the notification was delivered but customer may have dismissed it
4. Device connectivity:
Was their device online when notification was sent?
Check if they received other notifications around the same time
5. Customer device settings:
Do Not Disturb enabled?
Battery saver mode active?
Notifications globally disabled?
"Notifications are consistently delayed for specific customers"
Possible causes:
Device-specific issues:
Older device models with aggressive battery management
Outdated iOS or Android version
Low storage space affecting app performance
Carrier or network issues:
Specific mobile carriers with poor connectivity
Geographic areas with weak signal
Wi-Fi networks with restrictive firewalls
User settings:
Extreme battery optimization enabled
Background data restricted
App refresh disabled
Recommendation: Suggest alternative communication methods (email/SMS) for these customers or encourage them to check device settings.
"Many customers not receiving notifications"
Systematic issues to investigate:
1. Perkstar platform status:
Check for any service announcements
Verify your notifications are configured correctly
Ensure your account is in good standing
2. Widespread platform issues:
Apple or Google experiencing outages (check status pages)
Regional network problems
Time of day affecting delivery rates
3. Recent changes:
Did you change notification settings recently?
Did you update message content that might trigger spam filters?
Are you sending more frequently than before?
4. Customer base characteristics:
Are many customers using older devices?
Is your customer base in an area with poor connectivity?
Have many customers disabled notifications?
FAQ
Q: Can I pay for faster or guaranteed delivery? A: No. Push notification delivery is handled by Apple and Google's infrastructure, which operates on a "best effort" basis. Neither Perkstar nor any other service can guarantee faster delivery times, as this is controlled entirely by the platform providers.
Q: Why do some customers receive notifications instantly while others wait minutes? A: Delivery speed depends on each individual customer's device state, connectivity, settings, and location. Two customers sitting next to each other may have different delivery times due to different devices, carriers, or settings.
Q: If a customer's phone is off, will they receive the notification when they turn it on? A: Maybe. APNS and FCM hold notifications for a limited time (typically a few hours to a day). If the device comes back online within that window, the notification will be delivered. If it stays offline too long, the notification may be discarded.
Q: Can I see exactly when each customer viewed their notification? A: No. You can see when the device processed the notification (via Latest Updates), but there's no way to know if or when the customer actually viewed, read, or acted on it. This information is not available to any push notification service for privacy reasons.
Q: Should I send notifications multiple times if customers don't respond? A: Use caution. If the Latest Updates section shows the notification was delivered, the customer received it—they may have chosen not to respond. Sending multiple notifications about the same topic can be perceived as spam. Consider following up via email instead.
Q: Are push notifications free or is there a cost per message? A: This depends on your Perkstar plan. Check your subscription details for information about included notification volume and any potential costs for high-volume sending.
Q: What's the maximum number of notifications I can send at once? A: This depends on your plan and the platform's rate limits. Sending to large customer bases (thousands) may take several minutes as notifications are batched and processed. Contact support for specific limits.
Q: Why don't notifications work in card preview? A: Card preview is a design tool only. It shows you how your card looks but doesn't function as a real card. Only cards that are properly issued and installed on actual devices can receive push notifications.
Q: Can customers opt out of specific types of notifications? A: The notification control is all-or-nothing at the card level. Customers can disable notifications entirely for a loyalty card, but they cannot choose to receive only certain types (e.g., rewards but not reminders). They control this through their device settings.
Q: Does sending during off-peak hours improve delivery speed? A: Not necessarily. While server load might be lower, many customers' devices will be in deep sleep or power-saving modes during off-peak hours (late night), which can delay delivery more than peak-hour server congestion would.
Related Articles
Push Notifications - How Automated Messages Work - Configuring notification types and timing
Push Notifications on iPhone (iOS) - How customers receive notifications on iOS
Push Notifications on Android - How customers receive notifications on Android
Email Delivery - Send Loyalty Cards via Personalised Links - Alternative communication method
Customer Profile Management - Managing customer contact information
Need help troubleshooting notification delivery? Contact support with specific examples (customer IDs, timestamps, notification content) for assistance diagnosing delivery issues.