Time-based automation sends emails on a fixed schedule after a starting event, like a five-day welcome series. Trigger-based automation sends in response to a specific behaviour, like a pricing page visit. Time-based is predictable and simple to run. Trigger-based is more relevant but needs behaviour tracking. The best programs don't choose. They use a time-based spine for consistency and layer triggers on top for the high-intent moments.
Key Takeaways
- Time-based sends fire on a schedule. Trigger-based sends fire on behaviour. That single distinction drives everything else.
- Time-based automation is simpler to build and guarantees a baseline of contact. Trigger-based automation arrives when intent is highest and converts harder.
- Trigger-based needs behaviour tracking to work. If you can't see what subscribers do, you can't respond to it.
- Mature lifecycle programs run both in parallel: a scheduled foundation plus behavioural layers.
- From what I've seen, teams that skip the time-based spine end up with relevant emails that never reach the people who went quiet.
What is the difference between trigger-based and time-based email automation?
Time-based automation sends emails on a fixed schedule after a starting event, like a five-day welcome series. Trigger-based automation sends in response to a specific behaviour, like a pricing page visit. Time-based is predictable and simple. Trigger-based is more relevant but needs behaviour tracking.
Lead with the comparison, because the choice gets clearer once you see them side by side:
| | Time-Based Automation | Trigger-Based Automation | |---|---|---| | Sends when | A set time after a start event | A subscriber takes an action | | Example | Day 1, 3, 5 welcome series | Email after a pricing page visit | | Strength | Predictable, simple, guaranteed contact | Relevant, arrives at peak intent | | Requires | A start event and a schedule | Behaviour tracking and event data | | Risk | Can feel generic if untargeted | Gaps if a subscriber takes no action | | Best for | Onboarding, education, nurture rhythm | Cart abandons, key pages, re-engagement |
Time-based automation is the older, sturdier of the two. You define a start event, like a signup, and the sequence rolls out on a clock regardless of what the subscriber does. HubSpot's automation guidance treats this as the backbone of most programs, and for good reason: it's reliable, easy to reason about, and it guarantees that every new subscriber gets the same well-designed introduction. The trade-off is that a pure schedule can't react. It sends day three's email whether the subscriber is fired up or completely checked out.
Trigger-based automation flips that. Nothing fires until the subscriber does something, and then the right message arrives because they just signalled intent. Salesforce's best-practice material is consistent on the payoff here: behaviour-driven sends land when relevance is highest, which is why they reliably outperform scheduled sends in the moments that matter most. The catch is that triggers depend on data. If your platform can't see the page visit, the cart abandon, or the drop in engagement, there's no event to respond to.
When should I use trigger-based email automation?
Use trigger-based automation when the timing of your message should respond to what the subscriber does, such as abandoning a cart, visiting a key page, or going quiet. Behaviour-driven sends arrive when intent is highest, which is why they consistently outconvert scheduled sends for high-intent moments.
The clearest signal that a moment wants a trigger is when timing is the whole point. A cart abandon email is worthless on a schedule and powerful within an hour of the abandon. A pricing page visit means something today and nothing next week. These are the moments where intent spikes and then fades, and a fixed schedule will always miss them. Reach for triggers when:
- Intent is time-sensitive. Cart abandons, demo requests, and pricing page views all decay fast. Respond while the interest is live.
- Behaviour reveals a stage change. A subscriber who suddenly visits your case studies has moved closer to deciding. Meet the new stage.
- Disengagement needs catching. When someone goes quiet, a re-engagement trigger reaches them before they're gone for good.
- The action implies a need. Downloading a specific guide tells you what they care about. Trigger content that matches it.
Can you combine trigger-based and time-based automation?
Yes, and the best programs do. Use a time-based welcome sequence as the foundation, then layer trigger-based sends on top for high-intent behaviours. The schedule provides consistency while the triggers add relevance. Most mature lifecycle programs run both in parallel.
This is where the false choice dissolves. You're not picking a philosophy. You're assigning each job to the mechanism that does it best. The time-based spine handles the work that should happen for everyone on a dependable rhythm: the welcome series, the education arc, the steady nurture that keeps you present. Litmus's automation guidance frames this as building a reliable baseline first. Then the triggers handle the exceptions, the spikes, the behavioural moments that a schedule can't predict. A subscriber moving through your time-based nurture can still get pulled into a trigger flow the instant they visit your pricing page, then return to the nurture afterwards.
The reason this matters for a lean team is that it compounds. The scheduled layer means no subscriber ever falls through the cracks for lack of contact. The trigger layer means the high-intent moments get caught while they're hot. Together they close the two leaks that kill most lifecycle programs: silence and bad timing. Run only triggers and the quiet subscribers vanish. Run only a schedule and the ready buyers slip past unnoticed. Run both and the system underneath your email catches both.
Frequently Asked Questions
What is the difference between trigger-based and time-based email automation?
Time-based automation sends emails on a fixed schedule after a starting event, like a 5-day welcome series. Trigger-based automation sends in response to a specific behaviour, like a pricing page visit. Time-based is predictable and simple. Trigger-based is more relevant but needs behaviour tracking.
When should I use trigger-based email automation?
Use trigger-based automation when the timing of your message should respond to what the subscriber does, such as abandoning a cart, visiting a key page, or going quiet. Behaviour-driven sends arrive when intent is highest, which is why they consistently outconvert scheduled sends for high-intent moments.
Can you combine trigger-based and time-based automation?
Yes, and the best programs do. Use a time-based welcome sequence as the foundation, then layer trigger-based sends on top for high-intent behaviours. The schedule provides consistency while the triggers add relevance. Most mature lifecycle programs run both in parallel.
Read Next
- Email Drip Campaign vs Automation
- Event-Triggered Email Automation Guide
- Complete Guide to Lifecycle Email Automation
If your automation is all schedule and no behaviour, you're likely missing the high-intent moments where conversions actually happen. A free audit will show you where your program leaks and which triggers would close the gap fastest.