The Complete Drip Campaign Guide for 2026

Guide •

By the editorial team (a pen name for the site's editorial team)

How to plan, build, and measure drip email sequences, which tools handle the email side and which handle the triggers, and what each setup costs as your list grows.

← All Blog Posts

TL;DR

For most teams that want to run drip campaigns from one contact list, Drip is the best pick in this guide. Its lowest published plan covers 1 to 2,500 people at $39 a month on monthly billing, lists unlimited email sends and up to 50 workflows, and offers a 14-day free trial with no credit card required. Drip sends and schedules the emails. If your triggers come from payments or from other software, you will usually add a tool such as Stripe, Paddle or Make to pass those events along. The rest of this guide explains where that split makes sense, what each setup costs at realistic list sizes, and how to build and measure a sequence that you can pause safely.

Covered here: Drip pricing by list size • Tool comparison • Trigger sources • Sequence design • Exit and suppression rules • Setup checklist • Common mistakes

What a Drip Campaign Has to Decide

A drip campaign is a sequence of emails that a contact enters because of a rule, not because someone pressed send. That makes it different from a newsletter or a one-off broadcast. Before you open any software, a drip campaign needs four decisions written down: who enters, what each message is for, when the next message is sent, and who leaves early.

The entry rule is the most important one. A welcome sequence might start when someone confirms an email address. An onboarding sequence might start when a trial account is created. A win-back sequence might start when a subscriber has not opened anything for 90 days. Each of these rules depends on an event your system can actually see. If the event lives in a payment processor, a product database or a form tool, the email platform needs a way to receive it.

The exit rule is the one teams skip most often. A contact who buys in the middle of a nurture sequence should not receive the rest of the sales pitch. A contact who replies to a message should probably move to a person, not stay in an automated path. A customer who has entered a payment-recovery sequence should leave it when the payment succeeds. Writing the exit condition next to the entry condition is the fastest way to avoid embarrassing sends.

The four decisions

  • • Entry: the exact event or segment rule that enrolls a contact
  • • Purpose: what each email asks the reader to do
  • • Timing: the wait between steps and any branches
  • • Exit: the conditions that stop the sequence early

Where teams usually get stuck

  • • The entry event exists in one tool but the sender cannot read it
  • • Two sequences target the same contact on the same day
  • • Purchases do not remove people from promotional steps
  • • Nobody owns the sequence after launch

Drip, the Platform, for Drip Campaigns

Drip is built around people and workflows. Its pricing tiers are set by the number of people in your database, not by the number of emails you send, which makes it easier to predict costs when your list grows slowly but your sequences run often. The first tier, for 1 to 2,500 people, costs $39 a month on monthly billing and includes unlimited email sends, dynamic segments, onsite campaigns and up to 50 workflows. The price rises with the people band: the 4,501 to 5,000 band is $89 a month, and the 9,001 to 10,000 band is $154 a month.

What Drip does well for drip campaigns

Drip is strongest when a single list needs several overlapping sequences. A workflow can be triggered by a subscription event, a tag, a segment change or a form submission, and it can split contacts into branches based on what they do next. Dynamic segments let you keep the list in one place and let each sequence pull only the people who meet its rule. For a team that runs a welcome series, a trial-to-paid series and a win-back series on the same audience, this structure avoids copying contacts between lists.

The lower tiers include unlimited email sends, so you do not have to plan the cost of a sequence around a send quota. For most small and mid-sized teams this removes the most common budgeting surprise in email automation: a sequence that works well and then gets expensive because every message counts.

Where Drip falls short

Drip does not replace a billing system. It does not decide whether a payment has failed, whether a subscription has been downgraded or whether a seat was removed. Those events have to come from Stripe, Paddle, your own application or an automation tool, and someone has to map them to Drip workflows. Plan that work before you promise a payment-recovery sequence.

The send allowance also changes with the largest bands. The lower tiers list unlimited email sends, but the 45,001 to 50,000 band lists 600,000 email sends and the 37,501 to 40,000 band lists 480,000. If you plan to mail a large list many times a month, read the send allowance on the live pricing page before you choose a band, rather than assuming the lower-tier wording applies to every plan.

There is no ongoing free plan on the pricing page. The trial is 14 days and does not require a credit card. Use the trial to build one real sequence end to end: entry rule, two or three emails, one exit condition and one test contact. A trial that only shows the workflow builder will not tell you whether the triggers you need can reach it.

Pricing and plan details: Drip's pricing page.

Tool Comparison for Drip Campaigns

Most drip setups use two or three tools rather than one. The table below compares the tools that appear in drip-campaign workflows. Prices are in US dollars as shown on each vendor's pricing page, checked on 7 October 2026. Where a vendor does not publish a price, the table says so.

Tool Best for Entry price (plan, billing) Key limitation
Drip Running several behavior-triggered sequences from one contact list $39/month for 1 to 2,500 people (monthly billing); 14-day trial, no card No ongoing free plan; price rises by people band
Make Routing events from forms, CRMs and billing tools into your email platform Free: 1,000 credits/month. Core: $9/month billed annually or $10.59 monthly, for 10k credits Each module action uses a credit; it is an automation tool, not an email sender
Stripe Payment events such as failed charges, renewals and cancellations used as triggers Per-transaction pricing; no monthly platform fee on standard payments pricing Handles payments, not email; you still need a sender to act on its events
Paddle Software sellers who want merchant-of-record billing and subscription events Per-transaction pricing; no monthly platform fee Billing platform, not an email tool; transaction fees apply to every sale
Segment (Twilio Segment) Large teams merging customer data from many tools before sending Pricing on request Custom pricing and a heavier setup than a single email platform
Convert Testing page variants that feed a drip goal, such as a signup or trial start Growth: $299/month billed annually or $399 monthly, for 100,000 monthly tested users; 15-day trial Experimentation tool, not an email sender; no ongoing free plan

Read the table by role rather than by brand. Drip sends the sequence. Stripe or Paddle tells you what happened to a payment. Make moves data between tools that do not talk to each other natively. Segment is for teams with many data sources. Convert helps you test the page a contact lands on before they enter the sequence. Most drip campaigns need one sending platform and at most one event source.

Drip Pricing at Realistic List Sizes

Drip prices by people band. The table below uses five list sizes and the band each one falls into. All figures are monthly prices on monthly billing, from Drip's pricing page checked on 7 October 2026. Annual billing rates are not shown in the figures used here, so the yearly totals are simple arithmetic on the monthly price.

Active people Drip band Price per month (monthly billing) Yearly total at that rate (12 × monthly)
2,000 1 to 2,500 people $39 12 × $39 = $468 a year
5,000 4,501 to 5,000 people $89 12 × $89 = $1,068 a year
10,000 9,001 to 10,000 people $154 12 × $154 = $1,848 a year
25,000 22,501 to 25,000 people $369 12 × $369 = $4,428 a year
40,000 37,501 to 40,000 people (480,000 email sends listed) $609 12 × $609 = $7,308 a year

Two things change the total more than the headline price. The first is the people band, because your list is what you pay for, not the number of sequences. Remove inactive or unsubscribed contacts before you move up a band, and check whether the band you are considering includes the send allowance you need. The second is the connection layer. A Make Core plan at $9 a month on annual billing, or $10.59 monthly, covers 10,000 credits. A sequence that reads a form, updates a CRM and then adds a Drip tag can use several credits per contact. Count the module actions in your scenario before you assume the included credits will cover your volume.

Stripe and Paddle do not add a monthly platform cost on their standard pricing, but they charge per transaction. Their cost belongs in your payment budget rather than in your email budget. Segment and Drip's larger enterprise-style bands should be quoted directly, since the first is priced on request and the second depends on the people band you choose.

Tool-by-Tool Notes for Drip Campaign Teams

Drip: the sending platform

What it does well: keeps several sequences on one people list, with segments and workflows that can branch on behavior. Good for SaaS onboarding, ecommerce post-purchase flows and nurture tracks that share a database.

Where it falls short: it is not a billing system, so payment events must come from elsewhere. There is no free plan after the trial, and the largest bands list fixed send counts.

Price: $39 a month for 1 to 2,500 people on monthly billing, rising to $609 a month for 37,501 to 40,000 people in the bands shown above.

Pricing page: drip.com/pricing

Make: the connector

What it does well: moves events between apps. A form submission, a CRM stage change or a webhook from a billing tool can become a Drip tag or a workflow entry. Its visual builder makes the path easy to audit when something goes wrong.

Where it falls short: every module action spends a credit, so high-volume events can use the included allowance quickly. The free plan limits you to 2 active scenarios, runs scenarios at most every 15 minutes, caps execution at 5 minutes and keeps logs for 7 days. Check that the Drip actions you need exist in Make's app list before you design around them.

Price: free with 1,000 credits a month. Core is $9 a month billed annually or $10.59 monthly for 10k credits, with unlimited active scenarios.

Pricing page: make.com/en/pricing

Stripe: payment events as triggers

What it does well: it reports the events that matter most to a billing sequence: a renewal, a declined charge, a cancellation or a plan change. A sequence that starts on a failed charge and stops when the next charge succeeds depends on these events being sent reliably.

Where it falls short: Stripe does not send the email. You have to connect its events to your email platform, usually through webhooks or an automation tool, and test that the exit event (for example, a successful payment) removes the contact from the recovery sequence.

Price: no monthly platform fee on standard payments pricing; costs are per transaction.

Pricing page: stripe.com/pricing

Paddle: billing for software sellers

What it does well: Paddle acts as the merchant of record, so it handles billing, tax and payment handling for software sales. For a team that sells software and wants subscription events as drip triggers, this means the billing record and the sequence rules come from the same place.

Where it falls short: it is a billing platform, not an email tool. You still need a separate sender, and its per-transaction pricing is charged on every sale rather than as a fixed monthly fee.

Price: per-transaction pricing with no monthly platform fee.

Pricing page: paddle.com/pricing

Segment: a customer data layer

What it does well: collects first-party data from products, sites and tools and sends it to destinations. Teams with many systems use it so that every sequence reads the same customer profile.

Where it falls short: the setup is heavier than a single email platform, and the pricing is custom. For a team with one product, one list and one billing provider, it is usually more than the sequence needs.

Price: pricing on request. The page mentions a free trial for Connections, without stated duration or limits.

Pricing page: segment.com/pricing

Convert: testing the path into a sequence

What it does well: tests page variants and experiments that lead into a drip goal. If you want to know whether a signup page or a trial page brings in contacts who then respond to a welcome sequence, a testing tool answers the first half of that question.

Where it falls short: it does not send email, and it has no ongoing free plan. The Growth plan is sized by monthly tested users, so high-traffic pages can move you into a larger tier.

Price: Growth is $299 a month billed annually or $399 monthly, for 100,000 monthly tested users. Pro is $420 a month billed annually or $599 monthly. A 15-day trial is available on Growth and Pro.

Pricing page: convert.com/pricing

How to Choose the Setup

Start from the trigger, not the tool. Write down the event that enrolls a contact and the system where that event is recorded. If the event is already inside your email platform, such as a tag or a form submission, one tool may be enough. If the event is a payment, a plan change or a usage limit, you need a route from the billing or product system into the sequence. That route decides whether you add a connector, a billing platform or a data layer.

The table below turns that logic into a short decision guide.

If you need Pick Because
Several sequences that share one people list Drip Segments and workflows run on the same database, and the first tier includes unlimited sends
A recovery sequence that starts on a failed payment Stripe or Paddle events, plus Drip The billing system knows when a charge fails; the email platform sends the messages and needs the success event to exit
Form or CRM events feeding a sequence without code Make, plus Drip Make moves events between apps; check that the Drip actions you need exist before you build
Test before you buy Make Free and the Drip trial Make's free plan covers 1,000 credits a month; Drip's 14-day trial needs no card, so you can test one full sequence
One customer profile across many products and tools Segment A data layer is worth its custom cost when many systems need the same profile
Evidence that a landing page change improves the drip entry rate Convert Experiments on the page that feeds the sequence; keep the email results in your own reporting

Building a Drip Campaign Step by Step

Step 1: Write the entry and exit rules first

Write one sentence for entry and one for exit. For example: "A contact enters the trial onboarding sequence when a trial account is created. A contact leaves when they add a payment method or cancel the trial." Keep the wording specific enough that a developer or a platform admin can build it without asking questions. If a rule uses a field, name the field.

Step 2: Map the purpose of each email

Each step should have one job. In a trial onboarding sequence, one email might show how to import the first data set, another might explain how to create an automation, and a third might invite the reader to book a setup call. Do not put three different offers into one message. A reader who has not finished the first step will not respond well to a pitch for the third.

Step 3: Set the timing with reasons

Time each gap for a reason. Payment-recovery steps often need to come quickly after the failed charge, while a nurture sequence for a slow buying cycle can run over weeks. Avoid giving every sequence the same cadence. Write the reason beside each gap in your plan, so that a later reviewer can see why the gap exists.

Step 4: Add branches only where behavior changes the message

A branch is useful when the next email should be different because of what the reader did. A contact who opened the setup guide but did not connect a data source should receive a different follow-up from a contact who already connected it. Branches that only split contacts into identical paths make the workflow harder to maintain without improving the message.

Step 5: Set suppression before launch

Suppression keeps contacts from receiving messages they should not get. Before launch, define which events remove a contact from promotional steps: a purchase, a reply, an unsubscribe, a support ticket or entry into a competing sequence. Test each one with a test contact. A purchase that does not stop a discount reminder is one of the most common and most visible drip errors.

Setup step Owner Done when
Entry event is recorded in a system the sender can read Developer or platform admin A test account enters the workflow on its first try
Consent and permission status are checked on entry Marketing lead Only contacts with a valid permission basis can enroll
Exit events remove contacts from the sequence Marketing operations Each exit condition has been tested with a test contact
Suppression rules cover purchases, replies and unsubscribes Marketing operations A purchase test removes the contact from promotional steps
Primary conversion and review window are defined Marketing lead The team has one goal metric and a date to review it
Migration from an old tool, if any, is reconciled Operations Active contacts in both systems are counted and matched before the old sequence is switched off

Sample Sequences by Purpose

The sequences below show how the four decisions look in practice. They are outlines, not templates to paste. Adapt the content to the product, the audience and the offer you actually have.

Trial onboarding (for a software product)

  • Entry: trial account created. Exit: paid plan started, or trial cancelled.
  • Email 1, day 0: the one setup task that matters most, with a link to the guide for it.
  • Email 2, day 2: send only to contacts who have not finished the first task. Show the second step.
  • Email 3, day 5: one realistic example of the result the trial should lead to.
  • Email 4, day 10 (before trial end): the plan choice, with the price from the vendor's pricing page for the list size that applies.

Failed-payment recovery (for a subscription)

  • Entry: a failed charge event from the billing system. Exit: a successful charge, a cancellation or a manual plan change.
  • Email 1, same day: a plain notice of the failed payment with a direct link to update the card.
  • Email 2, a few days later: a reminder with what happens to access if the card is not updated.
  • Email 3, final notice: a clear date after which the plan will be cancelled, and how to contact support.

Win-back for inactive subscribers

  • Entry: no opens or clicks in 90 days. Exit: any click, reply or purchase.
  • Email 1: a short note asking whether the reader still wants the emails, with a preference link.
  • Email 2, one week later: the most useful thing the list has sent recently, with no new offer.
  • After Email 2: suppress the contact from promotional sends if there is still no engagement. Do not keep sending to a list that does not open.

Measuring the Sequence

Measure each sequence against its own goal rather than against an industry average. A welcome sequence might be judged by how many new contacts complete the first setup task. A payment-recovery sequence should be judged by how many failed charges end in a successful payment. A win-back sequence should be judged by how many inactive contacts engage again, and by how many unsubscribes it causes.

Keep a holdout group where you can. A small group of eligible contacts who do not enter the sequence shows what would have happened anyway. Without it, you can credit the sequence with results that were already happening. The exact holdout size depends on your list, so decide it before launch and write it down.

Review the sequence in three places: at each email, at each step and at the end of the sequence. An email with a low click rate may still be the best email in the sequence if the readers who click go on to convert. A sequence that loses most of its contacts by the third email may need a shorter wait, a clearer first message or a stronger exit condition. Look at drop-off between steps as well as final outcomes.

Common Drip Campaign Mistakes

Triggers that the sender cannot see

The most frequent failure is a sequence built around an event that lives in another system. A team writes a payment-recovery sequence, then discovers that the email platform never receives the failed-charge event. Confirm the route from the source system to the sequence before you write a single email.

Missing exit rules

A customer who buys mid-sequence should not receive the rest of the pitch. A person who has replied should not receive the next automated message. Each sequence needs at least one exit rule that is tested, not just described.

Overlapping sequences

When a welcome sequence, a nurture track and a promotional campaign are active for the same contact, the contact can receive several messages in the same week. Decide which sequence has priority and suppress the others during it. A simple priority list written in the plan prevents most of these collisions.

Paying for people who never engage

Tiered pricing by people means that an inactive list has a real cost. Review the list before a band change, remove or suppress contacts who have not engaged in a long period, and keep the win-back sequence as the final step before removal.

Set and forget

Pricing changes, product changes and seasonal offers all make old sequences out of date. Put a review date on every active sequence and assign an owner. A sequence that refers to a removed feature or an expired offer damages trust faster than a missing email.

Summary: What to Do Next

If you run one list and want several sequences on it, start with Drip's 14-day trial and build one sequence end to end before you commit. Use the $39 monthly tier for a list of up to 2,500 people, and check the band that applies as the list grows. If your entry events come from payments or other software, add the connector that already has the event, whether that is Stripe, Paddle or Make, and test the exit event before you launch.

Write the entry and exit rules first, give each email one purpose, set suppression before launch and review the sequence on a fixed date. Those four habits do more for a drip campaign than any single feature.

Ready to Build Your Drip Campaigns?

Compare drip email platforms and the tools that feed them, then choose the setup that matches your triggers.

Compare Drip Tools

Frequently Asked Questions

What is the best starting plan for a drip campaign on Drip?

For a list of 1 to 2,500 people, Drip's lowest published plan is $39 a month on monthly billing. It includes unlimited email sends, dynamic segments, onsite campaigns and up to 50 workflows. Use the 14-day trial, which needs no credit card, to build one sequence before you commit.

Does Drip have a free plan?

The pricing page shows a 14-day free trial with no credit card required and no ongoing free plan. If you need a free starting point for the connection layer rather than the email platform, Make's Free plan includes 1,000 credits a month.

Can Drip send a failed-payment recovery sequence on its own?

Drip sends the emails, but it does not detect payment failures. The failed-charge and successful-charge events must come from your billing system, such as Stripe or Paddle, or from a connector. Test both events before launch, because the recovery sequence should stop as soon as the payment succeeds.

How much does a drip setup cost for 10,000 people?

The 9,001 to 10,000 people band on Drip costs $154 a month on monthly billing, which is 12 × $154 = $1,848 a year. Add the cost of any connector you use. A Make Core plan is $9 a month billed annually, or $10.59 monthly, for 10k credits. Payment processor fees depend on your transaction volume and are charged per transaction.

Why do my drip emails keep reaching contacts who already bought?

The purchase event is probably not reaching the sequence, or it is not set as an exit condition. Check that the purchase event is recorded in a system the sender can read, add it as an exit or suppression rule, and test it with a test purchase before you launch again.

Should I use Convert for my drip campaign?

Convert is for testing page variants, not for sending email. It is useful if you want to test the signup or trial page that feeds a sequence. Growth is $299 a month billed annually or $399 monthly for 100,000 monthly tested users, with a 15-day trial. Measure the email results in your email platform, not in Convert.

How long should a drip sequence run?

Match the length to the decision. A trial onboarding sequence usually runs until the trial ends, because its job is to finish the setup before the deadline. A nurture sequence for a slow buying cycle can run longer. Whatever the length, set an exit rule for a purchase or an unsubscribe, and review the sequence on a fixed date.