Best Time to Send Push Notifications (Backed by Real Data, 2026)

The myth that needs killing

The "7 PM is the best time" rule comes from a real observation: consumer apps in the early smartphone era saw peak engagement in the early evening because that was when people stopped commuting and started scrolling. That data was largely correct in 2013. By 2026, several things have changed:

• Work-from-home flattened the evening peak. Without a commute, people check their phones throughout the day. The sharp "lean-back" window that used to appear at 6–8 PM has spread out across multiple smaller peaks.
• Notification volume at peak hours has tripled. When every app sends at 7 PM, users get 12–20 notifications in a 90-minute window. The math works against you: more competition means lower open rate, even if the timing is theoretically right.
• App categories behave differently. A fintech app and a gaming app share nothing in terms of user intent at 7 PM. Lumping them into one timing rule is what produces mediocre results across the board.
• Global audiences make a single send time nonsensical. If your users span three time zones, "7 PM" is simultaneously rush hour, dinner, and midnight. A single blast will hit two of those three segments at a bad time.

The goal of this post is to replace the single-number rule with a framework that accounts for category, day of week, timezone, and volume context, because all four interact.

What the data actually shows

Industry reports from OneSignal, Braze, and CleverTap, plus aggregated send data from PushPilot campaigns across 2025 and early 2026, consistently show the following:

Three insights stand out as most actionable and least obvious:

1. Midday is consistently underrated. The 12–1 PM window performs within 5% of the 7–8 PM peak in most consumer categories, with significantly less competition. If your entire audience gets a notification at lunchtime and your competitors are all waiting for evening, you are operating in a much less crowded channel.
2. 9–10 AM is quietly the worst morning window. Most timing guides say "morning works well." That is true, but 9–10 AM is when work notifications (Slack, email alerts, calendar reminders) peak sharply. Your push competes directly with high-urgency work messages. Users in a work context will dismiss low-urgency app notifications without reading them. 7:30–8:30 AM, before that work wave hits, outperforms 9–10 AM by roughly 20% CTR in PushPilot's data.
3. Saturday outperforms every weekday for consumer apps. This contradicts most email marketing wisdom (Tue–Thu is king for email). For push, Saturday users have more discretionary time, are more likely to be in a browsing or shopping mindset, and receive fewer work-related notifications, which means less competition. Sunday drops off compared to Saturday, likely because of the Sunday anxiety effect (people mentally preparing for Monday).

Time of day: the real windows

Rather than picking one time, think in terms of four distinct windows, each with a different user mindset and competitive dynamic:

Weekday vs weekend: not what you think

Email marketing gospel says Tuesday through Thursday are the highest-performing days. That rule comes from B2B email, where your audience is at work, using their work inbox, during work hours. Push notifications are a consumer channel, and the dynamics are different.

The Saturday advantage is not marginal. In our data, Saturday sends for consumer e-commerce apps consistently outperformed Tuesday sends by 15–20% on CTR. The mechanism is simple: users have more discretionary time, are more likely to be in a browsing or shopping mindset, and receive significantly fewer work-related interruptions, which means your push notification competes with leisure rather than with Slack.

The Sunday drop-off relative to Saturday is also consistent. Our best explanation is the "Sunday anxiety" phenomenon: users mentally shifting back into work mode on Sunday afternoons, which reduces receptivity to non-urgent commercial messages. Sunday mornings, however, remain strong for content and media apps (the long-form reading and podcast mindset).

The exception: B2B SaaS and productivity apps follow email logic more closely. For these, Tuesday–Thursday outperforms weekends because users are engaged with work-related tasks and your product is part of that workflow. Sending a productivity tool push on Saturday is an interruption; sending it on Tuesday morning is a useful nudge.

Timing by app category

Aggregate timing data is interesting. Category-specific data is what you actually need to act on. Here is the breakdown by app type, with the reasoning behind each pattern.

The timezone trap (the biggest mistake)

This is the most impactful and most commonly ignored variable in push notification timing. Most teams send at a time that works in their timezone, inadvertently sending at midnight, 4 AM, or mid-workday for a significant portion of their audience.

Consider a US-based team that schedules a campaign for 7 PM Eastern. What actually happens:

The fix is not complicated. Every major push provider, including OneSignal, Firebase Cloud Messaging (via delivery wrappers), and campaign platforms like PushPilot, supports timezone-aware delivery. When you set "deliver at 7 PM in the user's local time," each user gets the notification at 7 PM their time. The campaign takes longer to complete (24 hours if your audience spans the globe), but the CTR improvement is consistent: 20–35% higher compared to a single-time blast.

If your platform does not support per-user timezone delivery natively, the minimum viable approach is timezone bucketing:

1. Segment users into timezone buckets (US Eastern, US Central/Mountain, US Pacific, Europe, Asia-Pacific)
2. Schedule separate sends for each bucket at the equivalent local time
3. Use the bucket with the most users as your baseline, and stagger the others by the hour difference

This is manual and error-prone. But it is infinitely better than a single blast. For teams with more than 20% of their audience outside a single timezone, timezone bucketing should be treated as a non-negotiable foundation, not a future optimization.

Notification volume matters too

Timing optimization does not happen in a vacuum. The time you choose determines how many other notifications your push is competing with, from other apps on the same device. This is called the device-level crowding effect, and it is measurable.

Research from Braze and CleverTap both show that notification open rates decline as device notification load increases. A user who receives 3 notifications in a 30-minute window opens more of them than a user who receives 12. This is the hidden cost of the 7 PM "best time": not just your push, but every app using the same playbook, arriving at the same time.

Two strategies reduce crowding impact:

• Off-peak sends with high-quality content. A genuinely useful notification at 12:15 PM competes with 2–3 other pushes instead of 15–20. The CTR might be similar, but the brand impression quality is higher (users are less likely to feel overwhelmed and batch-dismiss your message).
• Frequency capping. Sending fewer notifications total raises the signal-to-noise ratio of each one. The counterintuitive insight from frequency data: apps that send 2–3 targeted pushes per week consistently outperform apps sending 7+ pushes per week on CTR, not just per-push, but in aggregate engagement. Volume works against you past a threshold that most teams cross without realizing.

AI adaptive timing vs fixed scheduling

Everything above applies to fixed scheduling, which means choosing a time based on category, day, and timezone logic. It is significantly better than "7 PM for everyone." But it still makes a population-level bet: the average user in your e-commerce app is most engaged at noon on Saturday.

Averages hide outliers. Your most valuable users (your habitual openers, high-LTV purchasers, and vocal advocates) may engage at completely different times from your average user. Fixed scheduling optimizes for the center of the distribution while potentially sending to your best users at the wrong moment.

AI adaptive timing takes a different approach: instead of asking "when is the best time for our category," it asks "when has this specific user historically engaged with our notifications?" It builds a per-user engagement model and delivers each send at the individual optimum.

The gains from AI adaptive timing are largest for apps with diverse audiences, including global user bases, mixed demographics, or highly variable use patterns. If your app has a very homogeneous user base (e.g., all US East Coast, all in the same age cohort, same daily routine), category-optimized fixed scheduling will capture most of the available lift.

The practical reality: most teams should implement timezone-localized delivery and category-optimized windows first. These two steps are low-effort, available on most platforms, and will capture 30–45% CTR improvement with minimal ongoing work. AI adaptive timing is the ceiling-raiser, worth implementing once the fundamentals are right.

A practical timing framework

If you take nothing else from this post, use this decision tree before scheduling your next campaign:

One important note on measurement: when you change timing, give the new configuration at least 4–6 sends (2–3 weeks at typical frequency) before evaluating. Single-send comparisons are influenced too heavily by content and external factors. Timing effects only become reliable in aggregate.

FAQ

Bottom line

The "7 PM rule" is not wrong. It is incomplete. For many consumer apps, the evening window is still strong. The problem is using it as a universal default without accounting for category, day, timezone, or competitive crowding.

The highest-leverage changes, ranked by impact and effort:

1. Enable timezone-localized delivery: immediate 20–35% CTR lift, one setting change
2. Apply category-specific timing: stop using one window for all content types
3. Test Saturday for consumer apps: consistently underused and overperforms
4. Avoid 9–10 AM: high competition from work notifications kills open rates
5. Add AI adaptive timing: the ceiling-raiser once fundamentals are right

None of these require more notification volume. They require sending the same content at better moments for each user, which is exactly where an AI push notification platform like PushPilot earns its value.