Google Chrome has announced new rate limits for web push notifications, and we want to make sure you have all the details. The short version: this is a positive change for the push notification ecosystem, it will not impact the vast majority of senders, and Aimtell is actively monitoring this for all of our users. In this post, we’ll break down exactly what’s changing, why it’s good news, and how Aimtell’s built-in tools like frequency capping, segmentation, and predictive sending already position you to thrive under these new guidelines.
Starting in January 2026, Chrome will begin enforcing rate limits on the Push API for websites it identifies as “disruptive.” The goal is simple: prevent bad actors from flooding users with excessive, low-value notifications that degrade the overall push notification experience.
Here are the key details:
For the full technical details, you can read Chrome’s official announcement.
We know “rate limits” might sound alarming at first glance, but this change is genuinely a win for everyone who uses push notifications responsibly — which includes the vast majority of Aimtell users.
Here’s why:
It protects the channel. Push notifications are one of the most powerful direct communication tools available to website owners. But when spammy senders abuse the channel by flooding users with irrelevant notifications, it gives push a bad reputation. Users start associating all browser notifications with spam, which leads to higher opt-out rates across the board — even for brands sending quality content. Chrome’s rate limits specifically target those bad actors, preserving the trust and effectiveness of push for everyone else.
It encourages better practices. These limits reward exactly what good push notification strategy looks like: timely, relevant, and engaging messages sent to the right audience. If you’re already following best practices — which Aimtell makes easy to do — you have nothing to worry about.
Nearly all websites will be unaffected. Chrome has stated explicitly that the vast majority of sites will never encounter these limits. The threshold of 1,000 messages per minute is generous, and the “disruptive” classification targets only sites with extreme sending patterns relative to their user engagement. If you’re sending relevant, valuable notifications to engaged subscribers, you’re in the clear.
As your push notification platform, we take this seriously. Our team is actively monitoring Chrome’s rate limit rollout and its impact across all Aimtell-powered sites. We’re tracking delivery metrics, watching for any 429 responses, and staying in close contact with browser vendors to ensure our users are never caught off guard.
If we detect any changes in delivery behavior that could affect your campaigns, we’ll notify you proactively. You don’t need to worry about manually monitoring this — that’s our job.
That said, the best defense is a great offense. Aimtell already provides several tools that help you send smarter, not harder. Let’s walk through the three most relevant ones.
Aimtell’s Frequency Cap feature lets you set a maximum number of push notifications any single subscriber can receive in a day. If you set a cap of 5, for example, no subscriber on your site will ever receive more than 5 notifications in a 24-hour period — regardless of whether they come from manual campaigns, triggered notifications, or API sends.
This is one of the most effective ways to prevent notification fatigue and keep your subscribers engaged over the long term. To set it up:
When a subscriber hits their daily limit, Aimtell automatically skips them for additional sends. You can track how many notifications were skipped in your campaign details under “Skipped (Frequency Cap)” — giving you full visibility into how the cap is working.
Sending the same notification to your entire subscriber base is one of the fastest ways to trigger notification fatigue — and potentially fall on Chrome’s radar. Aimtell’s segmentation tools let you target specific groups of subscribers based on behavior, attributes, and engagement levels.
With segmentation, you can:
The more targeted your sends, the higher your engagement — and the further you stay from any rate limit threshold. Segmented push campaigns consistently deliver better results than bulk blasts.
Aimtell’s Predictive Sending feature uses Intelligent Delivery technology to analyze each subscriber’s individual engagement patterns and deliver notifications at the moment they’re most likely to interact. Instead of blasting all subscribers simultaneously (which creates a large spike in sends), predictive sending distributes delivery across a 24-hour window based on each person’s optimal time.
This serves double duty in the context of rate limits:
Enable it in the Schedule tab when building any campaign. It’s one of the smartest ways to send push notifications in 2026.
Even though most Aimtell users will never encounter Chrome’s rate limits, here are some general best practices to ensure your push notification strategy stays in great shape:
Chrome’s new push notification rate limits are designed to clean up the web push ecosystem by targeting sites that abuse the channel with spammy, excessive notifications. For responsible senders — the kind of businesses that use Aimtell — this is nothing but good news. It means your subscribers will have a better overall experience with browser notifications, which translates to more trust, higher engagement, and better results for your campaigns.
Aimtell is monitoring this closely and has your back. And with tools like frequency capping, segmentation, and predictive sending, you’re already equipped to send smarter, not harder.
Questions about how these changes affect your account? Reach out to our support team — we’re happy to help.