What Is a Drip Campaign? Definition, Examples, and Triggers

A drip campaign is a series of pre-written emails that an automation sends to one person over time. It starts when that person does something, such as signing up, starting a trial, or leaving a checkout, and it stops when they reach the goal or the sequence runs out. Some drips run on a fixed schedule (day 0, day 2, day 5). Others check what the person has done before each send. For onboarding, the second kind usually wins, because it never asks someone to do a step they already finished.

This guide covers how drips work, time-based versus behavior-triggered sequences, five example sequences with day-by-day logic, and how to measure them.

How does a drip campaign work?

Every drip campaign, simple or complex, is built from the same five parts:

A drip is different from a newsletter or broadcast. A broadcast goes to a whole list at once. A drip runs on each person's timeline, so someone who signed up on Monday and someone who signed up on Friday receive the same emails on different days.

Time-based drips vs. behavior-triggered sequences

The term "drip campaign" covers two different designs. Knowing which one you're building matters more than any copy decision.

Time-based drips are simple: day 0 welcome, day 2 tips, day 5 a customer story. They fit content where there is no product state to check, such as a newsletter welcome or an email course.

Behavior-triggered sequences check state before each send. "Wait one day, then if the user hasn't connected a data source, send setup help; if they have, send the next step instead." They need event data your email tool can read, but every message matches where the person actually is.

Why behavior-triggered onboarding beats a fixed drip for activation

Activation is the moment a new user first gets real value, such as publishing a first report, sending a first invoice, or inviting a teammate. It is a specific action, and a drip built on fixed delays sends the same emails on the same days whether or not the user has taken it. That causes three problems:

1. It sends stale instructions. A user who connected their data in the first ten minutes still gets "Connect your data" on day 2. After one or two emails like that, people learn your onboarding emails don't apply to them and stop reading.
2. It ignores speed. Fast users wait for a schedule built for the average user. Slow users get the next step before finishing the current one. A behavior-triggered sequence sends the next step when the previous one is done, and sends help when someone is stuck.
3. Its results are hard to read. If the "connect your data" nudge goes to everyone on day 2, its conversion rate mixes people it helped with people who were already done. When each email goes only to people in one state, the question is clean: of users who got the nudge, how many connected within 48 hours? A holdout that gets no nudge shows how many would have connected anyway.

Many automation tools let you add a goal-based exit to a fixed drip, so it stops once someone activates.¹ Add one, but it won't fix the first two problems: until activation, everyone still gets the same steps on the same days. A behavior-triggered sequence checks state before each send, exits on activation, and hands the user to the next stage, such as team adoption or upgrade.

The trade-off is real. Behavior triggers need reliable event data, more branches to test, and someone to notice when a product change breaks an event. For a newsletter or a five-lesson email course, a fixed schedule is fine. For onboarding, trials, and re-engagement, react to behavior.

We don't know of a rigorous public benchmark that compares the two designs head to head, so don't take anyone's multiplier on faith, including ours. Run your own test: send half of new signups each version and compare activation rates.

Drip campaign examples with timing and trigger logic

Each example lists when each step runs, what it checks, and what it sends. Adapt the days to your own product.

1. SaaS trial onboarding (behavior-triggered)

A 14-day trial where activation means "published a first report."

Exit: the account pays, cancels, unsubscribes, or the trial expires. If you bill with Stripe, its customer.subscription.trial_will_end event fires three days before a trial ends, which makes a convenient trigger for the last step.²

Our welcome email examples show copy for the first email in this sequence.

2. Newsletter welcome series (time-based)

There is no product state to check, so a fixed schedule works.

• Day 0: Confirm the subscription, say how often you send, link the single best past issue.
• Day 2: Three most-read posts, grouped by topic.
• Day 5: Ask one question ("What are you working on?") and invite replies.
• Day 9: Optional: introduce a paid product or community, once.

Exit: unsubscribe, or the regular edition takes over.

3. Abandoned checkout (behavior-triggered)

For stores, with marketing consent recorded.

• 1 hour after a checkout starts without an order: Reminder showing the items left behind.
• 24 hours: Answer the usual objection: shipping cost, delivery time, or returns.
• 72 hours: Final reminder. Add an incentive only if your margins allow it, since people learn to wait for discounts.

Exit: an order is placed. Check before every send, not just at entry.

4. Re-engagement (behavior-triggered)

For a product people should use weekly.

• No key action for 7 days: Remind them what they've built ("You have 3 projects and 12 saved reports").
• Day 14, still inactive: A different angle: what's new, or a shortcut to the task they used most.
• Day 21, still inactive: Say you'll pause reminders and keep their data saved.

Exit: any key action. Our guide to re-engagement emails covers triggers, copy, and how Duolingo does it.

5. B2B lead nurture (mostly time-based)

For someone who downloaded a guide but hasn't signed up.

• Day 0: Deliver the guide.
• Day 5: How a similar company solved the problem the guide covers.
• Day 12: Address the objection that usually stalls the deal, such as security, migration effort, or price.
• Day 19: A low-effort next step: a short demo, a teardown, or a free trial.

Exit: the lead books a demo or starts a trial, at which point they move to onboarding. Weekly spacing suits a considered purchase; our B2B email marketing playbook covers the rest of the funnel.

How to build a drip campaign in six steps

1. Pick one goal and the event that proves it. "Activate new users" becomes "first report published within 7 days of signup."
2. Choose a durable entry trigger. Use something stored in your database, such as a new account row or a trial start, not a page view that can fire twice.
3. Map the steps as states. For each email, write down the state it's for: "signed up, no data source after 24 hours."
4. Write one email per state. One job and one call to action per email. Our email marketing templates include copy for the common lifecycle emails.
5. Set exit and suppression rules. Exit on the goal. Suppress unsubscribed and bounced addresses, and decide what happens when someone qualifies for two sequences at once.
6. Launch with a holdout and measure. Keep a small random group out of the sequence so you can see how many would have reached the goal anyway.

Which metrics matter for a drip campaign?

Measure the goal, not the inbox.

Open rates are a weak signal. Apple Mail Privacy Protection loads email content, including tracking pixels, before the reader opens the message, so opens overstate engagement.³ Clicks are a useful diagnostic, and the goal action is the real measure. For keeping sequences out of spam, see the email deliverability guide.

Common drip campaign mistakes

• No exit condition. People keep getting nudges for steps they finished.
• A fixed schedule for state-dependent tasks. Onboarding emails that ignore what the user has already done.
• One sequence for everyone. An invited teammate joining an existing workspace needs different emails from the person who created it.
• Too many emails, too close together. If two emails could be one, merge them.
• Set and forget. Product changes rename events, move buttons, and change pricing. Review every sequence at least once a quarter, and watch for steps whose send volume suddenly drops to zero.

What tools run drip campaigns?

Most email marketing platforms can run a time-based drip. Sending services built for app email, such as Postmark, deliver the messages your app triggers, so the sequence logic lives in your own code or another tool.⁴ The real question is whether the tool can see the behavior you want to trigger on. Marketing platforms see email activity and whatever data you sync into them. Product-messaging tools take events from your app through an API or SDK. If your product data lives in your own database, you need either a sync or a tool that reads that data directly.

Dreamlit, the company behind this blog, takes the whole job off your hands. Our experts decide what to send, run the emails that turn signups into paying users, and own the results. Built for apps with 500+ signups a month.

Want to see where your onboarding loses people? Get a free activation audit.

Footnotes

1. Customer.io Documentation, "Goals & conversion criteria," https://docs.customer.io/messaging/send/automations/conversions/⁠ ↩

2. Stripe, "Configure trial offers on subscriptions," events table: customer.subscription.trial_will_end is "Sent 3 days before the trial period ends," https://docs.stripe.com/billing/subscriptions/trials⁠ ↩

3. Apple, "Use Mail Privacy Protection on iPhone," https://support.apple.com/guide/iphone/use-mail-privacy-protection-iphf084865c7/ios⁠ ↩

4. Postmark, "Coming from ActiveCampaign? Start Here: Postmark Overview," https://postmarkapp.com/support/article/coming-from-activecampaign-start-here-postmark-overview⁠ ↩

---

Frequently asked questions

What is a drip campaign?

A drip campaign is a series of pre-written emails sent automatically to one person over time. It starts when that person does something, such as signing up or starting a trial, and it stops when they reach the campaign's goal, unsubscribe, or reach the last email.

What is the difference between a drip campaign and a behavior-triggered sequence?

A classic drip sends each email after a fixed delay, such as day 0, day 2, and day 5. A behavior-triggered sequence also checks what the person has done before each send and branches or exits accordingly. Many people call both drip campaigns; the difference is whether the next email depends on the person's actions.

Is a drip campaign the same as a newsletter?

No. A newsletter or broadcast goes to a whole list at the same moment. A drip campaign runs on each person's own timeline, starting from the event that enrolled them, so two people in the same drip can be on different emails on the same day.

How many emails should a drip campaign have?

As many as it takes to reach one goal, and no more. Onboarding sequences often need three to six emails over the first one to two weeks. If an email doesn't move the person toward the goal, cut it.

How long should I wait between drip emails?

Match the gap to how quickly the next step can realistically happen. A setup nudge can go one day after signup, while a B2B nurture email usually needs about a week between sends. Always check the exit condition before each send so nobody gets a reminder for something they already did.

What is an exit condition in a drip campaign?

An exit condition is the rule that removes someone from the sequence, such as completing the goal action, making a purchase, unsubscribing, or moving into a more important sequence. Without one, people keep getting emails about steps they already finished.

What metrics should I track for a drip campaign?

Track the share of enrolled people who reach the goal, how long it takes them, and unsubscribe and spam complaint rates. Clicks are a useful diagnostic. Open rates are unreliable because Apple Mail Privacy Protection preloads images.