Drip Campaign: Set Triggers, Delays, and Exits
Imagine someone signs up for a store’s welcome offer on Monday, places a first order on Tuesday, and receives a Thursday email asking them to make that first purchase. The schedule worked. The follow-up did not. A useful drip campaign has to respond to what has changed since the person entered, especially when the desired action has already happened.

A drip campaign is an automated path of messages and rules that begins when a contact meets an entry condition. The path may send an email, wait, check a condition, take another action, or remove the contact. Drip describes these parts as triggers, actions, delays, decisions, goals, and exits; Mailchimp describes a similar arrangement of triggers, rules, actions, and exit conditions in its marketing automation flows. Those are descriptions of the companies’ products, not a promise that every email platform behaves identically. Drip’s workflow guide and Mailchimp’s flow guide show the underlying idea: a contact’s next message depends on the path the rules allow them to take.
My starting point is the event that makes a follow-up useful, the action the reader of that email might take, and the event that should stop the sequence. Only then would I write the messages. This order costs some setup time, but it prevents a polished email from reaching someone whose situation has already changed.
A drip campaign follows each person from an entry event
A regular announcement can go to a selected audience at a chosen time. In a drip campaign, each person enters when a qualifying event happens, so the same sequence can begin at different times for different contacts. A Monday signup and a Friday signup would each move from their own entry event through the configured waits and decisions. Mailchimp’s example uses a signup, a one-week delay, and an email action to illustrate this event-relative timing. Mailchimp explains the trigger, delay, and action.
The word “drip” can suggest that all the thinking is in the spacing between emails. Spacing matters, but the decisions matter more. Drip’s workflow components include a trigger for entry, delays to hold a person, decisions that split a path, goals representing an intended outcome, and exits that remove a person. A campaign containing three carefully spaced emails can still be poorly designed if every entrant receives all three after buying, booking, or opting out. Drip’s component descriptions make clear that waiting and stopping are separate parts of the flow.
There is no useful minimum number of emails that turns a sequence into a good drip campaign. The design question is whether another message has a distinct job at that point in the contact’s journey. If a new subscriber needs only a requested resource and one relevant follow-up, adding four more emails to fill a template creates work for the sender and attention costs for the recipient. If a product decision genuinely involves several steps, a longer path may be justified. Neither conclusion follows from a universal cadence; it follows from what the contact has done and what remains useful to explain.
That distinction also helps separate the message from the machinery. An email is the content a person sees. The workflow decides who sees it, when, and under what conditions. Better copy cannot repair an entry rule that admits the wrong audience or an exit rule that fails to stop an obsolete pitch. Conversely, a precise workflow cannot make an email useful if its content does not answer the question raised by the entry event.
Choose a trigger that gives the next message a reason to exist
A trigger should identify a recognizable change: someone submitted a particular form, made an order, or took another recorded action that warrants follow-up. Drip lists form submissions, marketing engagement, orders, page browsing, and connected third-party actions among possible trigger sources in its own product. Mailchimp likewise describes an event or action that adds a contact to a flow. The available event and its reliability depend on the platform and the data connected to it, so choose from events you can actually record rather than from an ideal diagram. Drip’s trigger explanation and Mailchimp’s trigger explanation describe their respective implementations.
Suppose a shop offers a guide to choosing a product size. “Submitted the size-guide form” is a much clearer entry event than “is on the marketing list.” The form tells you what the person asked for. The first email can deliver the guide; a later email can answer a question that arises while using it. A general list membership does not, by itself, tell you why the person needs a size guide today. The narrower trigger gives the writer a concrete promise to keep.
The trigger is only the first gate. Eligibility filters can prevent an otherwise matching contact from entering a flow that no longer fits. Drip’s guide gives an example of excluding someone already in another workflow when setting up an entry trigger; Mailchimp describes filters that narrow who starts a flow. Drip’s trigger-filter example and Mailchimp’s filter description support a practical rule: decide which people should be excluded at entry, then check again later if their status can change.
A subtle timing issue matters when a campaign first goes live. Both Drip and Mailchimp say their workflow triggers apply to qualifying actions after activation. Turning on a flow today does not, by that trigger alone, enroll everyone who performed the action last month. If the job is to contact an existing group, establish how that platform handles those contacts before treating the new trigger as a backfill mechanism. Drip’s forward-looking trigger note and Mailchimp’s activation note make this a product behavior to check, not an assumption to carry across tools.
Finally, decide what a repeated event means. A second form submission or another order may be a legitimate reason for a new sequence, or it may cause redundant emails. In Drip, a person removed at an Exit can enter again if they later meet the trigger. Drip’s exit documentation states that reentry behavior. Before launch, write down whether your campaign should allow it, and configure the trigger and filters accordingly.
Define the goal and the stop event before drafting the sequence
A campaign needs a specific desired action. “Engagement” is too loose to settle the next step: an open, a click, a reply, and an order would each call for a different response. For an introductory store sequence, “first order placed” is a clearer goal. For a follow-up after someone requests a consultation, “consultation booked” would be clearer if that booking event is recorded. The point is to name an event the system can recognize and the business can act on.
The goal and the exit are related but distinct. A goal says what outcome the path is working toward. An exit removes a contact from the active workflow. Drip says its goal step can pull a person past messages that would be irrelevant after the goal, while its Exit step removes the person from the workflow. Mailchimp defines an exit condition as an event or action that removes a contact from a flow. Drip’s discussion of goals and exits and Mailchimp’s exit-condition definition show why “we have a goal” is not a complete answer to “when do emails stop?”
Return to the shopper who bought on Tuesday. If the campaign is intended to win a first order, the Thursday first-order reminder has lost its purpose. I would make the purchase event stop that sales path, provided the order event reaches the email system in time. If the event is unavailable or delayed, that is a real design limit: the workflow cannot act on information it does not have. The remedy is to connect the relevant event or remove the message whose appropriateness depends on knowing it, not to hope that careful wording will hide the mismatch.
There can be more than one valid finish. A contact might reach the intended goal, reach the end of the useful sequence without taking it, or choose to stop receiving marketing. These outcomes need different handling. An eventual non-buyer may simply leave the sequence without another pitch. A buyer may enter a separate post-purchase path if there is a new, specific purpose. A marketing opt-out must stop marketing messages. The exit map should say which of these cases applies at each point, rather than treating “the last email was sent” as the only possible end.
Drip’s exit documentation describes an easy mistake: a path with a goal but no reachable exit can leave people active while they wait for a later goal. Drip’s explanation of an exit-less path is a reminder to trace every route on the diagram to an actual end. A flow may look visually complete while one branch still holds contacts indefinitely.
Give each email a distinct job, then set the waits
Consider an illustrative three-email welcome path for people who request the size guide. The first email, sent after the form event, delivers exactly what was promised and explains where to start. After a chosen delay, the second email addresses a predictable obstacle, such as how to take the relevant measurements, and points back to the guide. A third email, only for someone who has not placed an order and still qualifies for marketing, answers one remaining purchase question. The delay lengths are design choices for this example, not recommended benchmarks.
The sequence works because each email answers a different question. Repeating “Here is your guide” three times would only change the date, not the value. Equally, a purchase appeal in the first message could crowd out the resource the person requested. I would make the promised resource easy to find first, then use later messages only when they add information the first could not reasonably carry.
A wait is useful when the recipient needs time to act or when the next message has value only after a reasonable interval. Drip describes delays that hold people for minutes, hours, or days; Mailchimp describes both a time delay and a rule that waits for a chosen trigger. Drip’s delay description and Mailchimp’s flow steps show two different ways a path can pause. A fixed delay says “continue after this much time.” A conditional wait says “continue when this event occurs,” subject to the tool’s available rules. Neither should be added just to make a flow look sophisticated.
The cost of a shorter sequence is that some contacts will not receive another reminder. The cost of a longer one is that more contacts may receive messages after their interest or circumstances change. I would begin with the shortest sequence that covers the actual decision, then add another email only when I can name the unanswered question and the people for whom it remains relevant. This is a content judgment, not a claim that a particular number of emails will perform best.
The wording must also fit the moment. If an email says “complete your first order,” the workflow should check whether an order has already happened. If it promises a limited offer, the offer must actually exist and still apply when the delayed email arrives. Scheduling makes a message easy to send later; it does not keep its claims current. The more time between entry and send, the more important the conditions just before that send become.
Branch when a recorded difference changes what you should say
A branch is valuable when two groups need materially different next steps. Drip says a decision splits the path based on criteria such as products bought or purchase count. Mailchimp says a conditional split sends contacts down one of two paths based on chosen conditions. Drip’s decision example and Mailchimp’s conditional-split description support a simple test: if both branches would receive essentially the same advice, the branch is adding complexity without changing the answer.
For the size-guide campaign, a purchase is a meaningful difference. A buyer should leave the first-purchase path. A non-buyer may receive the next explanation if the sequence still serves them. Another useful difference might be the product category recorded on the request form, if the categories genuinely require different instructions. But if the form never records that category, there is nothing dependable to branch on. A message that asks the recipient to pick a category may be more honest than pretending the system knows it.
Branches are evaluated against data and rules at particular points in a flow. That means a contact’s route depends on what the system knows when the decision is reached, not on the writer’s intent. Mailchimp describes paths based on recorded actions and configured rules. When drawing a branch, note the source of the field or event it reads and what happens if the expected data is absent. Without that fallback, “personalization” can turn into a confident email to the wrong person.
I would start with one branch that changes the message or ends the path. More branches multiply the number of routes to write and check. A separate path for every minor preference may sound considerate, but it also creates more opportunities for stale content, missing data, and accidental overlap. Add a branch when you can finish the sentence “because this person did X, the next useful action is Y instead of Z.” If you cannot finish it, keep the path simple.
Match the campaign type to the event you can observe
A welcome campaign is a natural first use because the entry action is clear: a person signed up or submitted a form. Drip’s published example begins with a form submission, offers a first-purchase incentive, waits, and follows up with product information; the example also uses an order goal so the purchase changes the path. Drip’s welcome-workflow example is one product-specific illustration, not a template every business should copy. If your form offers a guide rather than a coupon, the first email should deliver that guide.
A post-purchase sequence starts from a different fact: an order has already happened. Its useful job could be to explain the purchased product or answer a common setup question. A first-purchase discount pitch would be out of place there. The same customer can have a welcome path and a later post-purchase path, but the entry and stop rules should prevent contradictory messages from arriving together. Drip’s trigger-filter example explicitly discusses excluding a person from one workflow based on participation in another. Drip’s workflow guide supplies that mechanism for its product.
A lead follow-up can also work if the contact’s request is specific. Someone who asked for a consultation may need scheduling information, a short explanation of what the meeting covers, and a stop when the booking is recorded. Someone who merely viewed a page has given a weaker signal; a sales-heavy sequence based on that single action is harder to justify as useful. This is a judgment about the context supplied by the event. It is also conditional on the platform being able to record the event and route the contact appropriately.
A re-engagement sequence deserves particular restraint. “Has not acted recently” can be a meaningful condition only if you define the action and the period, and only if sending another marketing message remains appropriate for that contact. If a person has explicitly opted out, re-engagement is not a reason to put them back into marketing. I would set a clear end to this path rather than using indefinite reminders to compensate for the absence of a response.
These examples share a structure but not a script. The welcome reader asked for something new. The buyer needs help after an order. The consultation requester needs a next step. The inactive contact may need a single relevant reason to return, or no message at all. Treating all four as a generic “seven-day nurture” sequence would erase the event that makes each campaign worth sending.
Build and check the complete path before activation
Before opening the automation editor, write the campaign in one line: “When this event occurs for an eligible contact, send this first message; wait for this reason; check this condition; then send, branch, or exit.” If that sentence contains an undefined event, resolve it before adding email copy. A diagram can then show the entry, each action, each wait, each decision, and each exit. Both Drip and Mailchimp describe flows assembled from these kinds of parts, although their exact controls differ. Drip’s workflow components and Mailchimp’s flow map description are useful when translating the sentence into either interface.
Trace a few concrete people through the finished map. One submits the form and never buys. One buys immediately after the first email. One buys while waiting for the second. One no longer wants marketing. One triggers the entry event again after leaving. For each, state the next email, whether any email should be suppressed, and the exact exit reached. This exercise is a design check, not a claim that a preview screen alone can reproduce every real-world event.
Pay special attention to what happens between a wait and the next send. The original entry condition may have been true days ago, while the next email depends on a current fact. If the copy says “you have not bought yet,” the path needs a purchase check or stop rule close enough to that send to justify the statement. If the tool cannot check the fact, rewrite the email so it does not claim knowledge the system lacks.
Then check the ends of every branch. Drip says a person is removed when they reach an Exit, and its documentation warns that a route without a reachable exit can leave a person active. Drip’s exit guidance gives a concrete reason to inspect the last node of each route. A campaign is ready to activate only when the person who succeeds, the person who does nothing, and the person who should stop all have a sensible destination.
Make a marketing opt-out stop the marketing
For U.S. commercial email, the FTC says CAN-SPAM requires a clear way for recipients to opt out of future marketing messages and requires senders to honor an opt-out within ten business days. The FTC also says commercial messages need accurate header information, non-deceptive subject lines, identification as an ad, and a valid physical postal address. The FTC’s CAN-SPAM business guide states these obligations. A drip campaign does not receive a special exemption because its messages were scheduled in advance.
The ten-business-day rule is a legal outer limit described in the cited U.S. guidance, not a useful delay to build into a workflow. I would make an opt-out stop marketing as soon as the request is recorded, including messages already waiting in a sequence. A workflow exit and a sender-wide marketing suppression solve related but different problems: leaving one flow should not leave another marketing flow free to send. The system design has to carry the person’s choice wherever marketing emails are queued.
A buyer or member can still opt out of marketing. The FTC specifically notes that subscribers and members retain that right. The FTC’s discussion of subscribers and members matters for post-purchase campaigns: an existing relationship does not make every later promotional email a transaction notice. If a message mixes an order update with a promotion, the FTC says its primary purpose determines how CAN-SPAM treats it. The FTC’s explanation of mixed-purpose email is the relevant source; do not classify a sales pitch as transactional merely because it mentions an earlier order.
This U.S. guidance addresses U.S. commercial email. It does not settle rules in other places or for other channels. The practical design choice here is narrower and durable: let a contact’s marketing choice override the campaign’s desire to complete a sequence. If you cannot reliably pass that choice into every send path, fix the routing before adding another drip.
Judge the campaign by its goal and by who reached each step
A send count tells you the workflow ran. It does not tell you whether the intended action happened or whether the right people received each message. Drip says its workflow dashboard includes email metrics such as sent, opened, and clicked, alongside order and revenue measures such as attributed orders and revenue per person. Drip’s workflow reporting description shows why it is possible to inspect both delivery through the path and the outcome the path was meant to support.
Choose the main outcome before reading the dashboard. In the first-order example, count the people who entered the flow and the people who placed a first order after entry, with a time window that makes sense for the campaign. In the consultation example, count bookings. Opens and clicks can help explain where attention changed, but they are not substitutes for the business action you defined as the goal. If the goal event is missing from your data, a high click count cannot fill that gap.
Denominators matter once a path branches. Imagine an illustrative flow in which 100 people enter and 40 place an order before the reminder. Only 60 remain eligible for that reminder. A click rate for the reminder should describe the people who actually received it, while an overall first-order rate should refer to the original 100 entrants. Mixing the two populations can make a branch look better or worse without any change in what contacts did. The numbers here are an example of how to read a flow, not a result from a real campaign.
Be careful with revenue labeled as “attributed” by an automation dashboard. It can show which orders the tool associates with the flow under its rules; it does not, by itself, establish that the emails caused every order. I would use that report to inspect movement and outcomes, then make changes according to the campaign’s actual goal and the paths people took. If too few eligible contacts reach the second message, look at entry filters and exits before rewriting its subject line. If many people reach it but the message answers no new question, the content or the timing deserves attention.
Fix the rule that failed, then reconsider the email
When someone never enters, check the trigger event, activation time, and entry filters. Drip and Mailchimp both describe triggers that apply after activation; Drip also describes filters that can exclude a contact from entry. Drip’s trigger guidance and Mailchimp’s flow guidance make these the first places to inspect. Sending another manual email will not repair a missing event in the automated path.
When someone receives the wrong branch, identify the exact field or event the decision read at that point. Mailchimp says a contact’s path is determined by configured conditions and the actions the contact takes. Mailchimp’s description of conditional paths explains the mechanism. The fix may be to correct the data source, move the decision closer to the message it controls, or stop claiming a fact the system cannot establish. Copy changes alone are the wrong first move when the route is wrong.
When someone keeps receiving emails after the intended action, inspect the goal, the stop condition, and every route to an exit. Drip’s documentation distinguishes the goal step from the Exit that removes a contact, and describes how a path with no reachable exit can keep a person active. Drip’s goal explanation and exit guidance point to a structural repair: make the outcome change the route and make the route end.
A good drip campaign is therefore less about having many timed emails than about making each send conditional on a still-relevant reason. Set a specific entry event, write the messages around the questions it raises, use waits and branches only where they change the next useful step, and give every route a real end. The result is a follow-up that can continue when help is useful and stop when the contact has already moved on.