ConvertKit gives you two ways to schedule a broadcast: pick a fixed time, or let the platform choose based on each subscriber’s past behavior. The second option—send-time optimisation—sounds smarter. It usually isn’t.
Most solo operators turn on send-time optimisation assuming it’s a free win. Sometimes it is. More often, it fragments your send window, dilutes your traffic spike, and makes your analytics harder to read. Here’s how to decide which method fits your business model.
Fixed scheduling: what you’re actually choosing
When you schedule a broadcast for 9:00 AM Eastern, every subscriber gets it at 9:00 AM Eastern. Simple. Predictable. Your entire list receives the email within a few minutes, your traffic spike is concentrated, and your open rate settles within an hour.
This matters if you’re driving traffic to a live event, a product launch with a deadline, or a piece of content where early engagement (comments, shares, replies) creates momentum. If fifty people hit your article in the first ten minutes, your server logs show a spike, your social proof builds fast, and your analytics are clean.
Fixed scheduling also makes troubleshooting easier. If your open rate tanks, you know exactly when the send happened and can cross-reference it with deliverability logs, spam complaints, or external factors (a news event, a holiday, a platform outage).
Send-time optimisation: what ConvertKit is actually doing
When you enable send-time optimisation, ConvertKit looks at each subscriber’s past open behavior and schedules delivery for the hour they’re statistically most likely to open. Someone who always opens at 6:00 AM gets it at 6:00 AM. Someone who opens at 11:00 PM gets it at 11:00 PM.
Your send window stretches across 24 hours. Your traffic arrives in a slow trickle instead of a sharp spike. Your open rate might climb a few percentage points—or it might stay flat, because the algorithm is working with limited data and guessing based on past behavior that may not predict future attention.
The feature works best if you have a large list (10,000+ subscribers), consistent send history (at least six months), and content that isn’t time-sensitive. A Sunday essay, a weekly roundup, or an evergreen tutorial can arrive anytime and still deliver value. A flash sale, a webinar reminder, or a breaking-news commentary cannot.
When send-time optimisation backfires
If you’re running a small list (under 2,000 subscribers), ConvertKit doesn’t have enough data to meaningfully optimise. The algorithm falls back to rough estimates, and you’re spreading your send across 24 hours for no measurable gain.
If you’re tracking referral traffic in Google Analytics, a 24-hour send window makes attribution messy. Your traffic graph looks flat instead of spiked, and it’s harder to isolate which traffic came from the email versus organic search, social, or other sources.
If you’re selling something with urgency—early-bird pricing, limited inventory, a countdown timer—send-time optimisation means some subscribers see the offer twelve hours after others. That’s not personalisation. That’s a coordination failure.
The non-obvious tip: test it by segment, not by broadcast
Don’t enable send-time optimisation across your entire account. Instead, create two segments: one for engaged subscribers (opened at least three of your last ten emails), one for cold subscribers (opened fewer than three). Send the engaged segment at a fixed time. Send the cold segment with send-time optimisation.
Your engaged readers already open reliably. They don’t need algorithmic coddling—they need consistency. Your cold subscribers might benefit from a delivery time that aligns with their past (limited) engagement. If send-time optimisation lifts their open rate by even two percentage points, you’ve re-engaged a slice of your list without sacrificing the predictability your core audience expects.
Run this for a month. Compare open rates, click rates, and unsubscribe rates across both segments. If the cold segment shows improvement, keep it. If the difference is negligible (under three percentage points), revert to fixed scheduling and simplify your workflow.
ConvertKit’s documentation sells send-time optimisation as a set-it-and-forget-it win. It’s not. It’s a trade-off: you sacrifice timing control and traffic concentration in exchange for a potential (but not guaranteed) uptick in open rate. For most solo operators, fixed scheduling is faster to manage, easier to analyse, and just as effective.
Want more tactical breakdowns like this? Subscribe to One Two Three Send and get one operator-focused deep dive every day.