App Push Timing Modifiers

Rescheduling is a Silent Hours feature (Sent At/Send After). STO never picks a "second-best hour" by itself. So with the Default option, a time that lands in the quiet window is simply dropped; choose Send After or Sent At if you'd rather shift it.

1. STO picks each shopper's best hour without steering around Silent Hours.

2. For Jane, that's 23:00, inside the quiet window.

3. The message is dropped; she doesn't receive it. STO does not retry at another hour, and the Launch screen warns you in advance: "The Send Time of your campaign is in the Silent Hours."

4. A TTL does not rescue it; the panel note is explicit: the message is dropped once Silent Hours starts, even within the TTL period.

Set the Send Time so the whole STO window falls outside your Silent Hours, and treat the "Send Time is in Silent Hours" launch warning as a blocker. Keep the STO window away from the edge of your quiet hours, and don't rely on TTL to recover dropped users.

1. At 12:00, the campaign is launched, but nothing is sent to John yet; STO is holding him for his best hour.

2. The TTL clock does not start at 12:00. It starts only when the message is actually sent out.

3. At 20:00, STO sends John's push. The 3-hour TTL starts now, so the message stays valid until 23:00.

4. The time STO spent waiting (12:00→20:00) is not subtracted from the TTL; John gets a full, fresh 3 hours.

5. 23:00 is before the offer ends at midnight, so the reward can never arrive after it's gone.

Set your STO window so that even its latest possible hour, plus the TTL, finishes before the deadline. Example: if the offer ends at midnight and TTL is 3h, an STO window ending at 20:00 is safe (20:00 + 3h = 23:00); a window ending at 22:00 would risk 22:00 + 3h = 01:00, past the deadline.

1. The panel lets you turn on both, so it looks like they'll work together.

2. But Throttling releases the audience in waves, pulling players in no particular order across a long stretch of time.

3. Alex's best hour is 13:00, but his turn in the wave queue may not come up until later. He can be sent at 15:00, two hours past his best hour.

4. The bigger the audience and the smaller each wave, the longer the whole send takes, and the further players drift from their best hour. In effect, STO stops doing its job.

Decide what matters more for this campaign. Choose STO when reaching each user at their best hour is the goal (personalized offers, engagement). Choose Throttling when protecting your systems during a huge one-time send is the goal (a launch or announcement). For a very large personalized send, split it into separate campaigns rather than stacking both on one.

1. There's no "hold and resume"; the system decides once, at the send moment.

2. If that moment were already inside the quiet window, the system would drop the message immediately.

3. Here it's outside the window (21:50), so the system compares two numbers: time left until the window opens (10 min) and the campaign TTL (30 min), and uses the smaller one → an effective TTL of 10 minutes.

4. The message is handed to Apple/Google/Huawei with that 10-minute life. It will not survive into the quiet window, and it never carries over to the next day.

For strict quiet-hour compliance, a short TTL is your friend; it guarantees a message can't linger and arrive stale. If reach matters more, a longer TTL helps, but remember it's still capped by the start of the quiet window and never crosses into the next day.

1. Each wave's TTL is set when the wave goes out, not when the campaign started.

2. Wave 1 sends at 10:00 and is valid until 11:00. Wave 40 sends at 13:00 and is valid until 14:00, a full, fresh hour.

3. Time spent waiting in the throttling queue does not count against the TTL.

4. So late waves are not expired just because the campaign began 3 hours earlier.

Start large throttled sends early, so even the last waves land inside your offer window and before any quiet hours. Use TTL to guard freshness, and lean on timing (start time + Silent Hours) to guard the window.

1. Throttling releases the audience in waves over time, so each wave goes out at its own moment.

2. A wave that goes out before Silent Hours is delivered; a wave that goes out inside the quiet window is dropped, user by user, not held for later.

3. Silent Hours is actually checked twice for each wave, so a user who moves into their quiet hours mid-send is still caught.

4. The wave order doesn't change, and no make-up wave is added for the dropped users.

For sends that may run into the night, either schedule so the waves finish before the quiet window, or set the Silent Hours option to Send After so late-wave users are delivered when their window ends instead of being dropped.

1. STO picks each shopper's best hour and schedules it; this step never drops anyone.

2. At that moment, Silent Hours checks the time. If it's inside the quiet window, the shopper is dropped (or rescheduled, if you set Send After / Sent At). This is the only step that can drop a user.

3. For everyone who passes, TTL keeps the message from arriving stale.

4. The real risk isn't TTL; it's STO landing a shopper's best hour right inside Silent Hours, which drops them before TTL even matters.

STO (picks the hour) → Silent Hours (allows or drops) → TTL (limits freshness for those allowed). Only Silent Hours can drop a message; STO and TTL never do.

Same as use case 1: if you can't afford dropped users, use a Silent Hours reschedule option (Send After / Sent At), and keep the STO window away from the edge of your quiet hours.

1. All three can be turned on. STO assigns each player an hour; when that hour arrives, those players are written into a wave and released at your throttling rate (e.g., 50,000 / 5 min).

2. Silent Hours is checked both when the wave is written and when it's sent, so quiet-window users are dropped at either point.

3. The flow is: STO (schedules) → Silent Hours (first check, may drop) → Throttling (releases in waves) → Silent Hours + TTL (final check when the wave is sent).

4. The only setting that drops a user is Silent Hours. STO and Throttling only affect timing; TTL only limits freshness.

Silent Hours and Throttling work well together for a big overnight-safe send. If precise per-user best-hour timing also matters, don't rely on STO in the same campaign; pick STO or Throttling (see use case 3) and use Silent Hours alongside whichever you choose.