Loading tutorials…
Loading tutorials…
Drip's signup takes 5 minutes. The setup that doesn't sabotage deliverability or break Workflows in week three takes 2-3 hours. Sending domain, DKIM, sender identity, default Lookups, and compliance posture are the parts most stores skip — and pay for later in lost inbox placement.
Who this is forDTC store owners signing up for Drip for the first time, or operators who created an account on a whim and haven't gone past the dashboard tour. If your store does $20K+/month and you're picking Drip over Klaviyo specifically for the price and visual workflow builder, this is the foundation you need before importing a single contact.
What you'll need
Step 1
Sign up via drip.com → choose the right plan tier → set workspace defaults BEFORE importing contacts. Once contacts are in, some defaults are sticky.
Go to drip.com → Start Free Trial. Use a real business email — `owner@yourdomain.com`, not a Gmail. Drip uses this email as the default `Reply-To` until you change it.
Pick the right plan tier. Drip pricing is based on contacts. For DTC stores under 2,500 active subscribers, the entry tier is fine. Above 10,000, the next tier kicks in — budget accordingly. Don't pick annual billing on day one; keep monthly until the integration is verified working.
In the dashboard → Settings → Account → set: workspace name (use your brand name, not your personal name), timezone (match your store), and default Reply-To. The default Reply-To is shown in every email unless overridden per workflow.
Under Settings → Compliance → fill in your full physical mailing address. CAN-SPAM requires this in every marketing email; Drip auto-appends it to the footer. PO Box is fine; a residential address is risky if the brand grows.
Under Settings → Users → invite your team (specialist, designer, anyone who'll touch workflows). Give each person their own login — shared logins are a security and audit nightmare.
Step 2
Drip → Settings → Sending Domains → Add your domain. Then add the DKIM CNAME, SPF include, and DMARC TXT record at your DNS provider. This is the single biggest deliverability lever.
In Drip → Settings → Sending Domains → click "Add Sending Domain." Enter `yourdomain.com` (apex), not `mail.yourdomain.com` or `www.yourdomain.com`.
Drip will show you the DKIM record(s) — usually 2-3 CNAME records like `drip1._domainkey.yourdomain.com → drip1._domainkey.dripemail2.com`. Copy each one exactly.
In your DNS provider (Cloudflare, GoDaddy, Route 53) → add each CNAME. Leave proxy/CDN OFF for these — Cloudflare proxying DKIM CNAMEs breaks alignment.
SPF: if you have no existing SPF record, add `v=spf1 include:_spf.dripemail2.com -all`. If you already send from Google Workspace, Mailchimp, etc., MERGE the includes into one record — never have two `v=spf1` records on the same domain or both break.
DMARC: add `_dmarc.yourdomain.com → v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com`. Start with `p=none` for the first 30 days, then move to `p=quarantine` once you confirm 100% authentication via the DMARC reports.
Back in Drip → Sending Domains → click 'Verify.' DNS propagation is usually instant but can take up to 24 hours. Don't send any campaigns until status reads 'Verified' on all three (DKIM, SPF, DMARC).
Step 3
Drip → Settings → Email Defaults → set the from-name, from-address, and reply-to your brand will use across all workflows. This is what subscribers see in their inbox preview.
In Settings → Email Defaults → From Name: use a recognizable human name + brand pattern. E.g., 'Sarah at Glow Skincare' outperforms 'Glow Skincare' by 8-12% on open rate in DTC.
From Email: use `firstname@yourdomain.com` not `noreply@`. Noreply addresses underperform because they signal 'don't engage with us' — and Apple Mail Privacy now boosts replied-from senders in inbox ranking.
Reply-To: set to a monitored inbox. If a customer hits reply with a question and it bounces, you've lost a sale AND damaged engagement metrics that affect future deliverability.
Default footer: confirm Drip is auto-appending your business mailing address and the unsubscribe link. Both are CAN-SPAM required; missing either is a $50K-per-email FTC fine in extreme cases.
Send a single test email from Drip → People → your own profile → 'Send test email.' Verify the from-name, from-address, footer, and that DKIM passes in the raw headers (Gmail → Show original → search for `dkim=pass`).
Step 4
Build the 4-5 Lookups every DTC store needs day one. Without these, every Workflow you build later will reference missing structure.
Drip uses 'Lookups' (saved segments) and 'Tags' (manual or rule-applied labels) instead of Klaviyo's Segments + Tags. The mental model: Tags are static labels (cheap to apply, slow to maintain); Lookups are dynamic queries (always fresh, costs a query each time).
Build these 5 Lookups before any Workflow runs: (1) 'Engaged 30 days' — opened or clicked in last 30 days. (2) 'Engaged 90 days' — same, 90-day window. (3) 'Customers' — has placed an order ever. (4) 'Repeat customers' — has placed 2+ orders. (5) 'Newsletter subscribers, no purchase' — opted-in, zero orders.
Create each: People → Lookups → New Lookup → name it → add the rule (e.g., 'Has opened an email' in last 30 days) → Save.
Build a small Tag library: `welcome-completed`, `vip`, `unengaged-90d`, `manual-do-not-send`. Tags are applied by Workflows or manually; don't over-engineer the taxonomy on day one.
These structures are the 'database schema' of your Drip account. Changing them later is painful because every Workflow, Form, and Broadcast that references a Lookup or Tag has to be updated.
Step 5
Settings → Compliance → confirm CAN-SPAM, GDPR, and unsubscribe options match your audience geography. Default settings are US-only safe — they will get you fined in EU/UK/Canada.
In Settings → Compliance → Privacy → enable 'Show GDPR-compliant consent prompts' if ANY EU/UK/Canada traffic hits your site. This adds explicit consent checkboxes to Drip-hosted forms.
Set 'Double opt-in' to ON for all marketing lists if you sell into EU/UK/Canada. Single opt-in is allowed in the US but no longer recommended — Gmail's 2024 sender requirements penalize lists with high spam rates that single opt-in tends to produce.
Configure the unsubscribe page: Settings → Email Defaults → Unsubscribe Page. Use Drip's hosted unsubscribe (don't try to self-host) — it handles List-Unsubscribe headers automatically, which Gmail and Yahoo now require.
Add a preference center URL if your brand sends multiple campaign types (newsletters, sale alerts, product drops). One-click full unsubscribe causes 30-40% more churn than letting people downgrade to 'less frequent.'
Document your consent records. Drip stores opt-in timestamp + source per subscriber, but if you ever face a GDPR complaint you need to be able to export those proofs. Settings → Compliance → Export Consent Records.
Step 6
Send a test broadcast to 5-10 internal addresses. Check DKIM, inbox placement, unsubscribe link, and footer. Only THEN import your real list.
Drip → Broadcasts → New Broadcast → use a simple template. Send to 5-10 internal email addresses you control across Gmail, Outlook, Yahoo, iCloud, and a corporate Microsoft 365 if you have one.
In each inbox: (1) verify the email lands in Primary/Inbox, not Promotions or Junk. (2) Click "Show original" / "View headers" — confirm `dkim=pass`, `spf=pass`, `dmarc=pass`. (3) Click the unsubscribe link — it should load Drip's unsubscribe page and process correctly. (4) Verify the footer shows your real business address.
Run the broadcast HTML through mail-tester.com (paste their unique address as one of your test recipients). Target score: 9.5/10 or better. Anything under 8 means you have a deliverability issue to fix before going live.
Only after this validation passes — import your real list. Drip → People → Import → CSV. Map columns carefully; the 'Source' field is what Drip uses for opt-in proof later.
Set imported contacts to active state intentionally. Drip's import wizard offers 'Subscribe to campaigns' as a checkbox — only check this for subscribers with clear documented consent. Importing a list as 'subscribed' without consent is the fastest way to a Gmail spam-rate flag in your first 30 days.
Common mistakes
Sending campaigns before DKIM/SPF/DMARC verify
What goes wrong: Inbox placement collapses immediately. Open rates run 12-18% instead of the DTC norm of 25-32%. Once Gmail or Outlook classifies a sender as 'low reputation,' it takes 60-90 days of clean sending to recover — meaning $5K-15K/mo of lost email revenue on a $50K/mo store.
How to avoid: Verify all three records (DKIM, SPF, DMARC) read "Verified" in Drip → Settings → Sending Domains BEFORE the first broadcast. Then send 5 test emails and grep raw headers for `dkim=pass spf=pass dmarc=pass`.
Importing contacts with no documented consent and marking them subscribed
What goes wrong: Spam complaints spike to 0.5-2% in week one (Gmail's threshold for sender penalty is 0.3%). Drip's deliverability ops will throttle your sending, and in extreme cases freeze the account. Recovering a frozen account takes 2-4 weeks and a written affidavit on consent provenance.
How to avoid: Only import contacts with provable opt-in (signup form record, checkout consent checkbox, etc.). For ambiguous lists, run a re-permission campaign FIRST asking them to reconfirm — losing 60% of an old list is worth keeping the 40% who actually want to hear from you.
Skipping DMARC because it looks scary
What goes wrong: Gmail (Feb 2024) requires DMARC for senders doing 5,000+ emails/day. Without it, campaigns get bulk-routed to Promotions or rejected entirely on the Gmail side. Costs DTC stores 15-25% of email revenue silently. Diagnoses look like 'something changed at Gmail' — but the actual change was your own missing DMARC.
How to avoid: Add the DMARC TXT record: `v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com`. Start with `p=none` so it monitors without enforcing. After 30 days of clean DMARC reports, move to `p=quarantine`. This is a 5-minute fix that protects $2K-15K/mo of revenue.
Using `noreply@` as the from-address
What goes wrong: Apple Mail Privacy, Gmail, and Outlook all factor reply rate into inbox ranking. `noreply@` senders are pre-marked as transactional/promotional and lose 8-15% of inbox placement vs `firstname@brand.com`. On a 50K-subscriber list this is 4,000-7,500 fewer engaged opens per campaign.
How to avoid: Settings → Email Defaults → From Email → use `firstname@yourdomain.com` (a name a real person sends from). Monitor that inbox or auto-forward to a shared support inbox. Replies are revenue signals; treat them as such.
No physical mailing address in the footer
What goes wrong: CAN-SPAM violation. Each email is a separate offense with statutory damages up to $50,684/email (2024 cap). Most brands won't get sued, but high-volume senders without addresses are flagged by Spamhaus and other RBLs, killing deliverability platform-wide.
How to avoid: Settings → Compliance → Mailing Address. PO Box is fine. Auto-appended to every email footer by Drip. Verify by sending a test broadcast and confirming the address is visible.
Recap
Done — what's next
How to connect Drip to Shopify (events, catalog sync, identified browsing)
Read the next tutorial
Hand it off
Drip account setup is mostly invisible work — DKIM records, compliance posture, sender identity — that doesn't show up in the dashboard. A specialist who's set up 30+ DTC Drip accounts will do this in 2 hours flat at $14-16/hr. The alternative is finding out at week 6 that your Promotions-tab inbox placement has been quietly tanking the entire flow library you spent another 20 hours building.
See specialist rates
Drip is roughly 30-50% cheaper than Klaviyo at comparable contact tiers and has stronger visual Workflow building. The trade-off: Klaviyo has deeper Shopify integration (richer event data, predictive CLV out of the box), more pre-built flow templates, and a larger specialist ecosystem. For stores under $1M/yr where price matters and you have someone who'll learn Workflows, Drip is a reasonable pick. For stores above $5M/yr where every email-revenue point counts, Klaviyo's deeper integration usually wins back the price difference.
DNS propagation is usually instant on modern providers (Cloudflare, Route 53) and up to 24 hours on slower ones (some shared hosts). Most stores see Drip flip from 'Pending' to 'Verified' within 5-15 minutes. If it's been 24+ hours and still pending, the most common cause is: (1) Cloudflare proxy enabled on the DKIM CNAME (turn it off), (2) two SPF records on the same domain (merge them), or (3) a typo in the record value (re-copy from Drip exactly).
You technically can send from Drip's default domain (`dripemail2.com`) without verifying yours — but you'll see open rates 30-50% lower than verified-domain sends. Gmail and Outlook deprioritize emails where the from-domain doesn't match the authentication domain. Skip this step and the entire Drip investment underperforms by half. Verification is a 15-minute setup; never skip it.
Yes, for 30-60 days during cutover. Important: disable all marketing workflows in the platform you're migrating FROM before activating the same flows in Drip, or subscribers get duplicated welcome/abandoned-cart emails. Keep transactional emails (order confirmation, shipping) on the old platform until you're 100% cut over to avoid breaking customer order communications.
The entry tier covers up to 2,500 active subscribers. For most DTC stores under $200K/yr, that's enough. Watch the 'active subscriber' count carefully — Drip counts anyone you've messaged in the last 30 days, including via Workflows. If you cross 2,500 you'll auto-upgrade; budget for that month-over-month as the list grows. Pro tip: prune unengaged subscribers (no open/click in 180 days) quarterly to stay under tier thresholds.
Drip has SMS as an add-on with per-message pricing. Functional but lighter than a dedicated SMS platform like Attentive or Postscript. For DTC stores where SMS is 15%+ of marketing revenue, you'll outgrow Drip's SMS within 6-12 months. For stores using SMS as a light supplement to email, Drip's built-in SMS works fine and avoids the integration complexity of a separate tool.
Drip
Drip's Shopify app installs in 5 minutes. The integration that actually drives 25-35% of e-commerce revenue takes 2 hours of structured setup. Historical sync, identified browsing, catalog feed, and event mapping are where DIY installs lose money for months.
Drip
Welcome Workflows are typically 30-45% of automated email revenue in a healthy Drip account. A bad welcome Workflow leaves 60% of that on the table. This is the build that captures it — trigger, delays, copy structure, exits, and validation.
Drip
Drip deliverability problems silently bleed revenue. Open rates drop from 28% to 16%, you think the audience is 'fatigued,' but the real issue is Gmail's been routing you to Promotions for 60 days. This is the systematic diagnostic that finds the actual problem.
Drip
Migrating from Mailchimp to Drip is a 6-10 hour project, not a 1-hour data dump. List structure differs, automation logic differs, consent rules differ. Most stores that DIY this lose 15-30% of subscribers and 30-50 days of email revenue. This is the migration that doesn't.
Klaviyo
Shopify and Klaviyo plug together in 10 minutes, but the integration that drives 30%+ email revenue takes 2-3 hours of structured setup. Historical sync, back-in-stock, and identified browsing are where most stores miss the money.