ConvertKit’s visual automation builder lets you add delays between steps—wait 3 days, then send an email; wait 1 hour, then tag the subscriber. But the delay feature doesn’t work the way most operators expect, and misunderstanding it can break onboarding sequences, drip campaigns, and time-sensitive offers.
How ConvertKit measures delay duration
When you set a delay of “3 days,” ConvertKit waits exactly 72 hours from the moment the subscriber enters that delay step. It’s not “3 business days” or “3 days at 9 a.m.” It’s a rolling 72-hour timer that starts the instant the previous action completes.
If someone subscribes at 2:37 p.m. on a Tuesday and your automation includes a 3-day delay before the welcome email, that email sends at 2:37 p.m. on Friday. If you have 200 subscribers enter the automation throughout the day, you’ll have 200 different send times spread across the clock.
This matters most when you’re running time-sensitive promotions or trying to align emails with specific days of the week. A “launch on Monday” automation that uses a 7-day delay from sign-up will send on different days depending on when people joined.
Delay minimums and processing lag
ConvertKit’s shortest delay is 1 hour. You can’t set a 15-minute or 5-minute delay. If you need tighter timing—say, sending a lead magnet immediately followed by a second email 10 minutes later—you’ll need to use two separate broadcasts or handle the second email outside ConvertKit.
There’s also a processing window. ConvertKit doesn’t guarantee that a 1-hour delay fires at exactly 60 minutes. In practice, most delays resolve within a few minutes of the target time, but during high-traffic periods (big launches, Black Friday campaigns), you might see 5–10 minute lag on short delays. Longer delays (24+ hours) tend to be more precise.
One operator I spoke with runs a 5-day product launch sequence and noticed emails sometimes landed 8–12 minutes late during a coordinated launch with affiliates. For most content sequences, that’s irrelevant. For a flash sale ending at noon, it’s a problem.
Stacking delays vs. using date-based rules
If you want emails to send on specific days regardless of sign-up time, don’t use delay steps alone. ConvertKit’s automation builder includes a “Wait until a specific day/time” condition. You can set a rule like “wait until next Wednesday at 10 a.m.” instead of “wait 3 days.”
This batches subscribers. Everyone who enters the automation between Wednesday at 10:01 a.m. and the following Tuesday at 11:59 p.m. will receive the next email on Wednesday at 10 a.m. It’s cleaner for weekly digest-style sequences or coordinated launches.
The tradeoff: if someone subscribes on Tuesday, they wait 8 days instead of 7. If they subscribe on Wednesday at 9 a.m., they wait 7 days minus 1 hour. The timing variance shifts from send time to wait duration.
I use day-based rules for anything tied to external deadlines (webinar reminders, cart-close emails) and rolling delays for evergreen onboarding where the calendar date doesn’t matter.
One non-obvious trick: buffer delays before conditional splits
If your automation includes a conditional split—”if they opened the last email, send A; if not, send B”—add a short delay before the condition checks. ConvertKit needs time to register the open event. If you check immediately after sending, most subscribers won’t have opened yet, and your condition will route everyone to the “didn’t open” branch.
A 6-hour or 12-hour buffer before checking open/click conditions gives the data time to populate. I’ve seen operators skip this and wonder why 95% of their list is routed to the “low engagement” path when open rates are actually 40%+. The timing was the issue, not the engagement.
ConvertKit doesn’t surface this in the UI. The delay step just says “wait X hours”—it doesn’t explain why you might need it before a condition. But once you know, it’s an easy fix.
Want more breakdowns like this? Subscribe to One Two Three Send for weekly deep-dives on the tools that run online businesses.