Key Points
Time-based email automation sends emails on fixed schedules — day one, day three, day seven — regardless of what the contact is doing; event-based automation sends emails in response to specific contact actions
Neither approach is universally superior — the best choice depends on the programme's analytics capability, the product's adoption complexity, and the commercial stakes of each contact in the sequence
Most B2B email programmes use time-based automation by default because it requires no behavioural analytics integration — but they would produce better outcomes with event-based automation for the highest-intent contacts
Database Providers supports both approaches through the verified contact data that ensures any automated email — time-based or event-based — reaches an active, role-current contact with accurate personalisation
Analyze this article with
Time-based and event-based email automation represent two fundamentally different theories about when a contact should receive an email. Time-based automation assumes that time is the best predictor of readiness — a contact who received email one yesterday is ready for email two in three days. Event-based automation assumes that behaviour is the best predictor of readiness — a contact who visited the pricing page today is more ready for a commercial conversation than a contact who received email three two days ago without having demonstrated any high-intent behaviour.
Both assumptions are partially correct. Time-based automation correctly recognises that a consistent cadence maintains the relationship and prevents the programme from disappearing from the contact's awareness. Event-based automation correctly recognises that a contact's specific behaviour is more relevant to their current readiness state than the passage of time.
Time-Based Automation — How It Works and When It Works Best
Time-based automation sends emails on a fixed schedule after a triggering entry event. The schedule is defined at sequence creation and applied uniformly to every contact who enters the sequence regardless of their engagement behaviour. Email one on day zero, email two on day three, email three on day seven, and so on.
Time-based automation is appropriate for: programmes with limited behavioural analytics capability (where detecting specific contact actions is technically impractical), early-stage nurturing where content delivery rather than intent detection is the primary objective, and newsletter programmes where a consistent publishing cadence is more important than individual subscriber behaviour responsiveness.
Time-based automation's primary limitation is its uniform treatment of contacts at different stages of consideration. A contact who opened every email and clicked through to three resources in the first two weeks is treated identically to a contact who opened nothing. Both receive email four at the same time, with the same content. The high-intent contact's readiness for a more direct commercial message is unaddressed.
Event-Based Automation — How It Works and When It Works Best
Event-based automation sends emails in response to specific contact events rather than on a fixed schedule. The event can be an engagement action (pricing page visit, resource download), a non-engagement event (inactivity for 21 days), a commercial action (demo request, trial sign-up), or a milestone completion (first product use, onboarding step completion).
Event-based automation is appropriate for: programmes with strong behavioural analytics (where contact actions can be detected and associated with CRM records in real time), high-value contact portfolios where the commercial stakes of each contact justify the additional personalisation and responsiveness, and products with variable adoption complexity where contact progress varies significantly.
Event-based automation's primary limitation is technical complexity — it requires integration between the behaviour detection system (website analytics, product analytics) and the email platform, and it requires the CRM contact record to be accurate at the point the event fires.
Combining Time-Based and Event-Based Approaches
The most effective B2B email automation programmes combine both approaches: time-based automation as the default cadence that maintains the relationship for all contacts, and event-based automation that overrides the time-based sequence for contacts who demonstrate specific high-intent behaviours.
The combination produces: consistent relationship maintenance for the majority of contacts who do not demonstrate specific high-intent behaviour (time-based), and precisely timed commercial responses for the minority who demonstrate specific high-intent behaviour (event-based). The event-based override pauses the time-based sequence temporarily, sends the intent-responsive email, and then either returns the contact to the time-based sequence or routes them to a more advanced stage based on their response.
The email marketing guide from Database Providers covers the time-based versus event-based automation decision framework. For the verified contact data that supports both automation approaches — SMTP freshness for time-based delivery reliability and role accuracy for event-based personalisation precision — Database Providers provides targeted mailing lists for sale contacts and buy email list database verified segments with the accuracy standards that automated email performance depends on.
FAQ's
Website cookie-based contact identification (HubSpot tracking, Google Analytics with CRM integration, or Salesforce Beacon) connected to the CRM, plus a basic CRM workflow that fires when the identified contact visits a specific page. This minimum configuration enables the most valuable event-based trigger (pricing page visit) without requiring complex analytics infrastructure.
Implement event-based automation for one trigger at a time, starting with the highest-priority trigger (demo abandonment or pricing page visit). Run the event-based trigger alongside the existing time-based sequence for three months, measure the conversion uplift, and use the data to justify the next trigger's implementation investment.
Yes — time-based automation requires only a schedule configuration in the email platform. Event-based automation additionally requires behavioural event detection, contact identification at the point of event, CRM workflow logic that evaluates the event and fires the trigger, and an email platform that can receive the trigger signal and send the response immediately. Each of these components must be tested independently before the full trigger is activated.
Yes — this is the recommended hybrid approach. The time-based schedule continues as the default. Event triggers are added as override conditions: when the specified event fires, the time-based schedule is paused and the event-based email is sent. If no response is received within the trigger's designated window, the time-based schedule resumes.
Time-based automation's primary data quality requirement is SMTP freshness — the email must be deliverable at the scheduled send time. Event-based automation adds the role accuracy requirement — the event-triggered email's personalisation must reference the contact's current role, which requires the CRM record to be current at the moment the event fires. Both requirements are met by Database Providers' standard verification and enrichment services, applied at the appropriate intervals for each automation type.
