A series of automated emails triggered by user actions or time-based rules, onboarding, nurture, re-engagement.
An email sequence is a set of automated messages sent in a planned order, triggered by something a person does or scheduled across a stretch of time. The point is to move someone along: from new subscriber to active user, from trial to paid, from quiet to re-engaged.
Automated sequencing arrived with the first marketing automation platforms. Eloqua, founded in 1999 and later acquired by Oracle in 2012, is widely credited as the first modern platform, introducing lead scoring and drip marketing that let companies respond to the signals leads were sending across web and email. Marketo and HubSpot followed and pushed the same mechanics down-market to smaller teams.
The word "drip" captures the original idea: deliver value in small doses over time to build familiarity before asking for anything. The model has split into two shapes. A scheduled sequence sends on fixed intervals after a single trigger, such as five emails over ten days following signup. A trigger-based sequence reacts to behaviour as it happens, firing on a trial start, a revisited pricing page, or a sudden drop in activity. Behavioural triggers tend to outperform fixed schedules because they meet the person while the problem is live.
Cialdini's account of persuasion offers a framework for why the drip structure works at all. His six principles — reciprocity, commitment and consistency, social proof, authority, liking, and scarcity — map cleanly onto sequence design: early emails that deliver useful information before making any request activate reciprocity, while a series of small progressive asks ("connect your first data sourceData SourceData & AnalyticsA data source or integrationView reference →", then "invite a teammate") exploits commitment and consistency, where each completed step raises the probability of the next. By that reading, a well-ordered sequence is not just a delivery schedule but a staged application of influence mechanics.
The constraintConstraintStrategyA limit, requirement, or ceiling the product must respect, whether a self-imposed principle or an externally imposed boundaryView reference → that governs all of it is deliverability. A sequence is worthless if it lands in spam, and inbox placement is decided by sender reputation, which high bounce rates and low engagement erode. Mailbox providers read engagement as the signal of whether a sender is wanted. A sequence that keeps mailing disengaged contacts does not just waste sends; it poisons the reputation that the rest of the programme depends on. Discipline about pruning and frequency is part of the design, not an afterthought.
A SaaS team builds a trial-onboarding sequence. The trigger is account creation. Email one, sent immediately, points to the single action that predicts retention: connecting a data source. The sequence then branches on behaviour. Users who connect a source get a featureFeatureProduct SpecificationA product capability or featureView reference →-discovery track. Users who do not get a different track that troubleshoots the blocker. A user who stays inactive for five days receives one re-engagement email; if that goes unopened, the sequence stops mailing them rather than dragging the sender score down. Trial-to-paid conversion rises from 9 percent to 14 percent, and because dormant contacts are suppressed early, inbox placement for the active cohortCohortGrowthA group of users sharing a common characteristicView reference → holds steady.
In the Unified Product Graph, an email sequence sits in the marketing region as a concrete execution beneath a campaign. A campaign plan sends it (Marketing Campaign PlansendsEmail Sequencehierarchy), which places the sequence as a child of the coordinated effort that owns its goal and audience. Holding the sequence as its own node, rather than folding it into the campaign, lets a team reuse and reason about a sequence across campaigns and trace which automated track moved which cohort.marketing_campaign_plan_sends_email_sequence
Type-specific fields on BaseNode
sequence_typeenumPurpose of the email sequence
email_countnumberNumber of emails in the sequence
open_ratenumberAverage open rate across the sequence (0-1)
click_ratenumberAverage click-through rate across the sequence (0-1)
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases, initial: planning · template: OPERATIONAL
1 edge type connected to this entity.
marketing_campaign_plan_sends_email_sequence