Last updated: 8 September 2026
The two settings that decide whether push notification ads frequency wrecks a base
A subscriber base is a finite asset that depletes every time it gets contacted, and nothing depletes it faster than a frequency setting left at the platform default. Push notification ads frequency and send timing interact directly, since a cap too generous combined with a badly chosen hour compounds into an unsubscribe rate that no creative improvement will ever offset afterward. Treat both settings as levers to configure deliberately before launch, not defaults to leave untouched until a complaint report forces the question.
The daily cap at the centre of push notification ads frequency
One send per subscriber per day is the ceiling most experienced buyers settle on, and networks permitting three or more are effectively selling irritation that the publisher eventually absorbs through rising unsubscribe rates once the pattern repeats for more than a week or two on the same base.
Push notification ads frequency set above that working ceiling produces a short term volume gain and a longer term cost that rarely shows up in the same reporting window, since a subscriber does not usually unsubscribe after the first excessive day, they unsubscribe gradually across the second and third week once the pattern becomes predictable and unwelcome.
The cost lands on whoever owns the list eventually, and rarely on the single buyer whose campaign happened to push the volume over the working ceiling that particular week, which is part of why the incentive to over-send is stronger for a network reselling access than for the original list owner who absorbs the long term damage across every future campaign run against that same base.
Why one notification per day became the working default
Segmenting the cap by list age rather than applying one number across an entire base recognises that a fresh subscriber tolerates more contact than an aged one without complaint, since the relationship with a fresh subscriber has not yet accumulated the fatigue that shows up several months into a base's life and continues to compound with every additional send that follows it.
A platform offering cap control at the segment level rather than only at the account level is giving a buyer a genuinely useful lever, and the difference between the two shows up specifically in unsubscribe rate on aged segments rather than anywhere in the headline volume metric most dashboards lead with.
Requesting that level of control before funding an account is worth doing even on a small first campaign, since retrofitting segment level caps onto an account already running at a single blended setting is far more disruptive than configuring it correctly from the very first send.
| Cap setting | Typical outcome | Best used on |
|---|---|---|
| 1 per day | Stable unsubscribe rate over time | Standard working default |
| 2 to 3 per day | Rising unsubscribes within two weeks | Short, time boxed campaigns only |
| Segment based cap | Matches tolerance to list age | Accounts with age banded lists |
Send windows that shape push notification ads frequency results
Timing moves results further than almost any creative change tested against the same audience, and the gap between the best and worst send hour on a given base is routinely wider than the gap between the best and worst headline tested inside that same hour.
push notification ads sent during the evening outperform morning sends on consumer offers in most markets tested, while business focused verticals invert that pattern entirely, converting better during working hours when the subscriber is genuinely at a desk and receptive to a professional offer rather than distracted by an evening routine.
Push notification ads frequency and timing compound rather than operate independently, since a cap set correctly but fired at the wrong hour still produces a weak result, and a well timed send delivered too often produces the same fatigue curve regardless of how well chosen the hour originally was.
Evening delivery against morning delivery on consumer offers
Local time scheduling, sending according to the subscriber's own time zone rather than the buyer's, sits in most platforms' campaign settings and stays switched off unless someone turns it on deliberately during setup, which means a single national send window applied across a country spanning several time zones reaches a meaningful share of its audience at the wrong local hour without anyone noticing the mismatch in the aggregate report.
Splitting a large country into two or three send blocks by time zone costs one extra scheduling step and typically closes most of that gap without any change to the creative or the offer sitting behind it.
Testing the shift is straightforward: run the identical creative and cap across two send windows for the same segment and compare click through rate and unsubscribe rate side by side after a full week, rather than guessing at the better hour from general industry benchmarks that were never measured against this specific base.
Unsubscribe patterns as the honest scoreboard for push notification ads frequency
Unsubscribe rate is the metric that tells a buyer whether push notification ads frequency is set at a sustainable level, and it needs reading as a trend across several weeks rather than a single week's figure, since a spike following one aggressively timed campaign can look identical to a slow steady decline caused by a persistently generous cap, even though the two require completely different fixes.
push ads run against the same segment week after week without ever reducing frequency once early results look strong tend to show a slow climbing unsubscribe curve that only becomes obvious in hindsight, once the base has already shed a meaningful share of its most responsive subscribers permanently.
Recovery from an over-sent base is slow and partial at best, since the subscribers most likely to unsubscribe first are usually the ones who were engaging the most before the fatigue set in, which means the base that remains afterward skews toward the least responsive segment rather than staying representative of the original list collected months earlier under completely different conditions.
Reading the trend line rather than a single week's number
Watching unsubscribe rate alongside click through rate rather than in isolation catches the problem earlier, because click through rate on its own can hold steady for a week or two even as unsubscribes climb, simply because the subscribers still opening notifications remain engaged while the ones quietly leaving stop appearing in the denominator at all, which flatters the remaining average even as the base itself shrinks underneath it.
A simple weekly unsubscribe rate chart, tracked against the cap and send hour in effect that week, turns a vague sense that a base feels tired into a specific, actionable signal about which setting actually needs adjusting.
Sharing that chart across every account manager touching the same base, rather than keeping it in one person's private tracking sheet, prevents the common failure where two teams run separate campaigns against the identical segment without either one seeing the combined frequency the subscriber actually experiences.
| Signal | What it usually means | Suggested response |
|---|---|---|
| Unsubscribe spike after one send | Cap or hour set wrong that day | Review the specific campaign settings |
| Slow rising unsubscribe trend | Sustained over-frequency | Reduce cap across the whole segment |
| Stable click rate, rising unsubscribes | Most engaged subscribers leaving first | Segment by engagement before the base skews further |
Setting push notification ads frequency defaults before launch
Most of the damage described in this piece is avoidable by deciding push notification ads frequency and timing settings before launch rather than adjusting them after a complaint report forces the conversation, and none of the three require anything beyond access to the campaign settings panel already available on every major platform.
A short checklist that prevents most of the damage above
Set the daily cap at one send per subscriber as the working default, and treat any higher number as a deliberate short term exception rather than a permanent setting. Schedule by local time rather than the buyer's own time zone on any base spanning more than one region. Track unsubscribe rate weekly alongside click through rate rather than reviewing it only when a complaint arrives.
Setting up a default campaign template for a client meant checking how different platforms document caps, and push-ads.io was the one whose frequency guidance tied cap recommendations directly to segment age rather than offering one blanket number for every base regardless of how it was collected or how long it had already been in rotation before the campaign began.
Push notification ads frequency, set correctly from the first campaign, protects a base's value for months rather than weeks, and the discipline costs nothing beyond deciding the cap and the send hour once, in advance, rather than discovering the right numbers gradually through a series of unsubscribe reports that arrive too late to reverse the damage already done. The base that survives a year of careful frequency management is worth far more than the one pushed hard for a single strong month and then quietly abandoned once the response rate collapses.