Email Marketing Automation

From blasts to behavioral automation

The earliest form of email marketing was the batch-and-blast: one message, sent to the entire list, on a schedule set by the marketer. Automation platforms — Klaviyo, HubSpot, Mailchimp, ActiveCampaign — replaced that model with behavioral, event-triggered flows: sequences that fire based on what an individual subscriber actually does (or doesn't do), sent only to them, at the moment their behavior makes the message relevant.

The shift matters because relevance drives every downstream metric that matters — open rate, click rate, and ultimately deliverability itself, since inbox providers use engagement signals to decide whether future sends land in the inbox or the spam folder at all.

Drip campaigns vs. behavioral triggers

A drip campaign sends a fixed sequence of messages on a fixed schedule relative to a starting event — day 0, day 3, day 7 — regardless of what the recipient does in between. It's simple to build and predictable, and works well for onboarding sequences where the goal is steady education regardless of interim behavior.

A behavioral trigger fires based on a specific action or inaction: an abandoned cart, a price drop on a viewed product, a lapsed 60-day purchase window, a completed signup with no first login. These flows are dramatically higher-converting than blasts because the message timing itself signals relevance — an abandoned cart email sent within an hour of abandonment converts at a materially higher rate than the same email sent as part of an unrelated weekly newsletter.

Common automated flows by trigger type

Flow	Trigger	Typical timing	Primary goal
Welcome series	New signup / subscribe	Immediate, then day 2-3	Set expectations, first conversion
Abandoned cart	Cart created, no purchase	1hr, 24hr, 72hr	Recover lost revenue
Browse abandonment	Product view, no cart add	2-4hr	Re-engage low-intent interest
Post-purchase	Order completed	Immediate, then day 7-30	Reduce buyer's remorse, cross-sell
Winback / lapsed	No purchase in N days	Day 60, 90, 120	Reactivate before full churn
Price drop alert	Watched item price change	Immediate	Convert warm, price-sensitive intent

Segmentation: sending the right message, not just at the right time

Triggers determine *when* a message sends; segmentation determines *what* it says and to *whom*. Effective segmentation combines multiple data layers: demographic/firmographic (industry, company size, role), behavioral (pages viewed, products purchased, email engagement history), and lifecycle stage (new lead, active customer, lapsed customer, VIP).

The deliverability-relevant segment every mature program tracks explicitly is engagement recency — subscribers who haven't opened an email in 90-180 days should generally be moved to a reduced-frequency or re-engagement-only segment rather than continuing to receive full-volume sends, because a growing base of unengaged recipients is the single strongest signal inbox providers use to downgrade a sender's reputation.

List size vanity metric vs. engaged list reality

A 200,000-subscriber list where 150,000 haven't opened an email in a year isn't an asset — it's a deliverability liability. Gmail and Outlook's spam filters weight engagement rate heavily; continuing to mail a large disengaged segment can suppress inbox placement for the entire domain, including to your actively engaged subscribers. Regular list hygiene (suppressing or re-permission-checking long-unengaged contacts) protects deliverability for everyone else on the list.

Deliverability fundamentals: SPF, DKIM, and DMARC

Before content or timing matters, a message has to authenticate as legitimately sent from your domain, or inbox providers treat it as suspicious by default. Three DNS-based protocols work together:

- SPF (Sender Policy Framework) — a DNS TXT record listing which mail servers are authorized to send email on behalf of your domain. Receiving servers check the sending IP against this list.
- DKIM (DomainKeys Identified Mail) — a cryptographic signature added to each outgoing message, verified against a public key published in DNS, proving the message wasn't altered in transit and genuinely originated from an authorized sender.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) — a policy layer that tells receiving servers what to do when a message fails SPF or DKIM (quarantine, reject, or allow), and provides aggregate reporting on authentication failures across your domain.

dns_email_auth_records.txt

text

; SPF - authorizes Klaviyo and Google Workspace to send as example.com
example.com.  TXT  "v=spf1 include:_spf.klaviyo.com include:_spf.google.com ~all"

; DKIM - published by ESP, one selector per sending platform
pm-bounces._domainkey.example.com.  CNAME  klaviyo-dkim-key.klaviyo.com.

; DMARC - start at monitor-only (p=none), tighten to quarantine/reject
; only after confirming legitimate senders all pass
_dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com; pct=100"

2024 sender requirements made this non-optional

Gmail and Yahoo's bulk sender requirements (effective 2024) mandate SPF and DKIM for any sender exceeding roughly 5,000 messages/day to their domains, and require a valid DMARC record at minimum enforcement level p=none. Senders without all three configured now see outright rejection or mass spam-foldering, not just reduced inbox placement — this moved from a best practice to a hard technical gate.

Platform choice: Klaviyo vs. HubSpot

Klaviyo is purpose-built for ecommerce, with deep native integrations into Shopify/BigCommerce product and order data, letting flows trigger on and personalize with real catalog and purchase data out of the box. HubSpot is a broader CRM-centric platform where email automation is one module among marketing, sales, and service hubs — stronger for B2B lead nurturing tied to a deal pipeline and lifecycle-stage automation than for catalog-driven ecommerce flows. The right choice tracks the business model, not general platform quality: ecommerce-heavy teams lean Klaviyo, B2B pipeline-driven teams lean HubSpot.

What's next

Behavioral email triggers work only as well as the lifecycle and scoring logic feeding them — knowing when a lead is actually ready for a sales-focused sequence versus continued nurture depends on lead scoring.

Next: Lead Scoring Models →