Send-Time Optimisation Explained

Send-time optimisation (STO) is a way of deciding when to release an email, either to an audience as a whole or to each individual subscriber. Its premise is simple: an email has a better chance of being noticed when it arrives at a time the recipient is usually receptive.

The useful part is not the promise of a universally perfect hour. There is no such hour. The value lies in replacing a habit such as “we always send at 9am on Tuesday” with evidence about audience behaviour, campaign purpose and operational constraints.

For permission-based marketing and lifecycle programmes, STO can be worthwhile. It can also be over-applied. A password-reset email should be immediate; a time-limited sale may need to arrive at one coordinated moment; and a sender with a fragile reputation may need to prioritise controlled delivery over an algorithm’s preferred release window.

What send-time optimisation actually does

Most STO features use historical engagement data to estimate when a contact is most likely to interact with an email, then distribute a campaign over a defined period. The exact inputs and rules vary by platform. For example, Mailchimp’s Send Time Optimization documentation describes selecting a time within 24 hours of a chosen date when contacts are most likely to open, based on available engagement data.

In practical terms, a campaign scheduled for Wednesday may reach one recipient in the morning, another at lunchtime and another in the early evening. The email is the same; the delivery time differs.

This is distinct from:

• Scheduling: releasing the whole campaign at one specified time.
• Time-zone sending: delivering at the same local clock time for recipients in different locations. This is a geographical rule, rather than an individual behavioural prediction. Mailchimp, for instance, describes its Timewarp feature as batching recipients by time zone.
• Send-time testing: deliberately comparing selected days or times to learn which performs better for a segment or future campaign.
• Delivery pacing: controlling the rate at which messages leave the sending platform, often to manage mailbox-provider deferrals, reputation risk or website capacity.

These approaches can complement one another, but they solve different problems. Treating them as interchangeable is a common source of muddled reporting and poor operational decisions.

The data behind an STO decision

A platform may infer timing preferences from opens, clicks, site activity, purchases, app events or previous message interactions. A mature in-house programme may build its own model from event data. In either case, the output is a probability, not knowledge of a person’s attention.

That distinction matters because email activity data is incomplete. A subscriber may read a message in a preview pane, act later through another channel, share it internally, or simply have a busy week. Someone’s past click at 7.15pm does not establish that 7.15pm is their permanent best time.

Open data deserves particular caution. Apple’s Mail Privacy Protection can hide whether a recipient opened a message; on supported Apple Mail setups, remote content may be downloaded in the background rather than when the message is viewed. This makes the apparent time of an open unreliable for affected recipients. Apple’s Mail Privacy Protection guidance explains both behaviours.

That does not make STO useless. It means a model based mainly on opens may be less precise than its interface implies. Stronger signals usually include meaningful clicks, signed-in product activity, purchase or booking events, completed forms, and explicit preference-centre choices. Their usefulness still depends on the campaign. A click on a weekly editorial newsletter and a completed purchase may say very different things about when a person wants promotional mail.

Start with the question the email needs to answer

Before enabling STO, decide what success means for this specific message. An optimisation method cannot compensate for an unclear objective.

For a retail campaign that ends at midnight, an algorithm may reasonably identify 10pm as a likely engagement time for some contacts. That can still be the wrong business decision if it gives them too little time to consider the offer, seek support or complete a purchase. Set a latest acceptable delivery time before allowing personalisation within the remaining window.

Send time is not a deliverability lever on its own

Timing can affect how people respond, but it does not override the fundamentals that determine whether marketing mail is trusted and accepted. Authentication, recipient consent, relevance, complaint handling, list quality, content, reputation and sending patterns remain more consequential.

Google’s sender guidance explicitly advises bulk senders to maintain a consistent rate, avoid sudden volume spikes, start new or expanded traffic with engaged recipients, and watch SMTP responses, spam rate and sending reputation as volume grows. It also says that a change in message format or sending infrastructure should be introduced gradually. See Google’s email sender guidelines.

This has an important implication for STO: spreading a campaign across a day is not automatically healthier than a fixed send. A poorly targeted campaign can generate complaints and weak engagement over a longer period. Conversely, a well-targeted campaign delivered in controlled batches may be entirely appropriate.

Mailbox providers also assess sending identity and audience response, not merely one campaign’s apparent engagement rate. Gmail’s Postmaster Tools reports spam rate, authentication, reputation and delivery errors for qualifying traffic, although it is not real-time and may omit low-volume data. Google’s Postmaster Tools dashboard documentation is a useful reference for what those measures do and do not show.

For promotional mail, easy opt-out is part of the operational picture. Google requires qualifying bulk senders to support one-click unsubscribe for marketing and subscribed messages. Yahoo similarly requires a functioning list-unsubscribe mechanism for bulk senders and says unsubscribe requests should be honoured within two days. Yahoo’s sender best practices also recommends setting clear frequency expectations and promptly removing invalid recipients.

If a campaign needs sophisticated timing to prevent people from becoming annoyed by its frequency, the underlying pressure strategy may need attention first.

How to evaluate whether STO is working

Do not judge the feature from one campaign or by open rate alone. Compare a meaningful run of comparable sends against a control group that receives the normal schedule. Hold as much else constant as possible: audience rules, offer, creative, subject line, sender identity, day of week and campaign duration.

A sensible evaluation asks four questions.

Did the campaign produce more valuable actions?

Choose the metric closest to the programme’s purpose: qualified clicks, completed registration, purchase, retained usage, booked appointment or another clearly defined event. Revenue can be useful for retail, but it may be too delayed or noisy for an editorial or product-adoption programme.

Did the result hold across segments?

An overall gain can conceal a poor result for new subscribers, customers in a particular market, recipients using a specific product, or a less-engaged cohort. Review enough volume to avoid reacting to random variation, then look at segments where the timing decision materially differs.

What happened to negative signals?

Track unsubscribes, spam complaints, hard bounces, deferrals and delayed delivery. Yahoo’s Complaint Feedback Loop can report spam complaints for enrolled DKIM-signed domains, enabling senders to suppress the reporting recipient from later campaigns. Yahoo’s CFL documentation explains the domain-based process.

Do not dismiss an increase in complaints because clicks rose. A tactic that extracts a little more immediate activity while eroding willingness to receive future email is rarely a durable improvement.

Did it create an operational problem?

An STO system can move large numbers of recipients into a similar predicted window. Check whether it creates delivery bursts, strains the destination website, clashes with other journeys, or makes customer-support demand harder to manage. The stated send time is not necessarily the moment every recipient receives the email: queueing, provider responses and throttling can all affect final delivery timing.

When simpler methods are better

STO needs sufficient, relevant history. A new programme, a small segment, a recently cleaned database or an audience that seldom clicks may not provide enough signal. In such cases, a well-considered default schedule is preferable to false precision.

Time-zone sending is often the clearest first improvement for an international audience. It prevents an email intended for 9am local time from landing at 4am elsewhere, without pretending to know every recipient’s preferred moment. Location data can also be imperfect, so define a sensible fallback for contacts whose time zone is unknown.

Controlled tests are another sound option. Test a small number of practical time windows over repeated comparable campaigns, then use clicks and downstream outcomes to guide a standard schedule. This approach is transparent, easier to explain internally and less dependent on opaque vendor modelling.

It is also reasonable to retain a fixed time for habitual publications. If subscribers expect a digest every Friday morning, consistency can be part of the product. Changing the delivery time in pursuit of marginal engagement may weaken that habit.

Practical guardrails for using send-time optimisation

Use STO as one decision layer in a responsible sending programme, rather than letting it make all the decisions.

• Exclude messages that must be immediate. Transactional and security communications should not wait for predicted engagement.
• Define a delivery window. Set an earliest and latest sensible arrival time, especially for offers, events and communications that need support coverage.
• Respect contact-pressure rules. An “optimal” moment is irrelevant if the person has already received several marketing messages that day or is due to receive a higher-priority journey email.
• Use engagement carefully. Prefer meaningful clicks and first-party actions where available. Treat opens as an imperfect signal, not proof of attention.
• Keep infrastructure and message categories separate. Promotional messages should not share timing logic or operational identity with receipts, alerts and other service mail.
• Build a control group into the process. Without one, normal seasonal changes, audience changes and campaign differences can be mistaken for an STO benefit.
• Watch provider-level feedback during large sends. Slow, pause or adjust delivery when SMTP responses or reputation indicators show a genuine issue; do not blindly force a planned distribution curve.

For organisations already seeing delivery problems, the sequence matters. Confirm authentication and alignment, consent and suppression handling, complaint processing, engagement quality and send-rate behaviour before making send-time optimisation a priority. Email Foundry’s work is relevant at this point where timing and contact-pressure decisions need to sit alongside provider-level pacing, audience verification and deliverability monitoring. It is not a substitute for permission, relevance or a clean sending programme.

The sensible view of send-time optimisation

Send-time optimisation is best understood as a controlled experiment in convenience and attention. It may help an established, permission-based programme reach some people at more useful moments. It cannot make weak content wanted, turn unengaged addresses into an active audience, or repair a damaged sender reputation.

Start with a clear campaign objective and a safe delivery window. Use the strongest behavioural data available, test against a control, and measure outcomes that matter beyond opens. If STO produces a repeatable improvement without worsening complaints, unsubscribes or delivery behaviour, keep it. If it does not, a consistent schedule, time-zone delivery and better audience decisions may be the more valuable optimisation.