Klaviyo provides powerful email marketing for WooCommerce stores. This guide covers installation, configuration, and optimization for automated marketing.
Klaviyo for WooCommerce
Why Klaviyo for WooCommerce?
Related: Klaviyo integration, connect WooCommerce with Klaviyo, find related content.
Purpose-built for ecommerce:
| Feature | Benefit |
|---|---|
| Deep sync | All WooCommerce data |
| Automation | Pre-built flows |
| Segmentation | Purchase-based targeting |
| Analytics | Revenue attribution |
| SMS | Multi-channel marketing |
Why choose Klaviyo:
- Ecommerce-specific features
- Advanced segmentation
- Revenue tracking
- Proven ROI
Klaviyo Pricing
Related: connect Shopify with Privy, Shopify Stamped Integration: Reviews & Loyalty Guide (2025), Shopify Mailchimp Integration: Complete Email Marketing Guide (2025).
| Contacts | Email Only | Email + SMS |
|---|---|---|
| 0-250 | Free | Free |
| 251-500 | $20/mo | $35/mo |
| 501-1,000 | $30/mo | $45/mo |
| 1,001-1,500 | $45/mo | $60/mo |
| 5,000 | $100/mo | $120/mo |
| 10,000 | $150/mo | $175/mo |
Free includes:
- 500 emails/month
- 150 SMS credits
- All features
Getting Started
Related: Shopify setup guide, Klaviyo integration, connect WooCommerce with Klaviyo.
Step 1: Install Plugin
- Log into WordPress admin
- Go to Plugins > Add New
- Search “Klaviyo”
- Install and activate
- Connect to Klaviyo account
Step 2: Configure API Keys
Get keys from Klaviyo:
- Go to Settings > API Keys
- Create new API key
- Copy public and private keys
- Enter in WordPress plugin
Step 3: Enable WooCommerce Sync
Configure sync:
- Go to plugin settings
- Enable WooCommerce integration
- Start historical sync
- Verify data in Klaviyo
Step 4: Set Up Tracking
Install tracking:
- Website tracking script
- Viewed Product events
- Added to Cart events
- Started Checkout events
Data Sync
What Syncs Automatically
| Data Type | Synced |
|---|---|
| Customer profiles | ✓ |
| Order history | ✓ |
| Products | ✓ |
| Coupons | ✓ |
| Categories | ✓ |
| Cart contents | ✓ |
Customer Profiles
Synced properties:
- Email address
- First/last name
- Shipping/billing address
- Order count
- Total spent
- Last order date
- Products purchased
Events Tracked
| Event | Trigger |
|---|---|
| Placed Order | Order completed |
| Ordered Product | Each product ordered |
| Fulfilled Order | Order shipped |
| Cancelled Order | Order cancelled |
| Refunded Order | Refund processed |
| Started Checkout | Checkout initiated |
| Added to Cart | Product added |
| Viewed Product | Product page view |
Essential Flows
Welcome Series
Signup trigger
↓
Immediate: Welcome + discount
↓
Day 3: Brand story
↓
Day 7: Best sellers
↓
Day 14: Social proof
Abandoned Cart
| Timing | Content | |
|---|---|---|
| 1 | 1 hour | Cart reminder |
| 2 | 24 hours | Urgency |
| 3 | 72 hours | Discount offer |
Expected recovery: 5-15% of carts
Browse Abandonment
Trigger: Viewed product, didn’t add to cart
- Wait 2-4 hours
- Send product reminder
- Include recommendations
Post-Purchase
Order placed
↓
Immediate: Thank you
↓
Day 3: Tips/how-to
↓
Day 14: Review request
↓
Day 30: Replenishment
Win-Back
| Segment | Timing | Offer |
|---|---|---|
| 30 days inactive | Day 30 | Reminder |
| 60 days | Day 60 | 10% off |
| 90 days | Day 90 | 15% off |
Segmentation
Pre-Built Segments
| Segment | Definition |
|---|---|
| Engaged | Opened/clicked 30 days |
| Repeat customers | 2+ orders |
| High value | Top 20% by spend |
| At risk | 60+ days no order |
| New subscribers | Last 30 days |
Custom Segments
Create segments using:
- Purchase history
- Browse behavior
- Email engagement
- Custom properties
- Predictive analytics
Examples
VIP Customers:
- Total spend > $500
- Order count > 3
- Last order < 90 days
Product Interest:
- Viewed specific product
- Did not purchase
- In last 14 days
Campaigns
Types
| Campaign | Use Case |
|---|---|
| Newsletter | Updates, content |
| Promotion | Sales, discounts |
| New product | Launch announcements |
| Seasonal | Holiday campaigns |
Best Practices
| Element | Recommendation |
|---|---|
| Frequency | 2-4/month |
| Timing | Test for audience |
| Personalization | Use dynamic content |
| Mobile | Optimize design |
A/B Testing
Test:
- Subject lines
- Send times
- Content
- CTAs
SMS Marketing
Enable SMS
- Add SMS in Klaviyo
- Set up sending number
- Configure compliance
- Build SMS list
SMS Flows
| Flow | Use Case |
|---|---|
| Cart abandonment | Higher urgency |
| Shipping update | Delivery notification |
| Flash sale | Time-sensitive |
| Back in stock | Product alerts |
SMS Best Practices
- Keep short (160 chars)
- Clear opt-out
- Respect frequency
- Value-add only
Product Feeds
Dynamic Content
Use product data for:
- Personalized recommendations
- Cart content in emails
- Browse history products
- Best sellers
Product Blocks
Drag-and-drop:
- Product recommendations
- Best sellers
- New arrivals
- Viewed products
Signup Forms
Types
| Form | Best For |
|---|---|
| Popup | High visibility |
| Flyout | Less intrusive |
| Embedded | Always visible |
| Full page | Landing pages |
Best Practices
- Offer incentive (10-15% off)
- Mobile-optimized
- Exit intent trigger
- Clear value prop
Analytics
Key Metrics
| Metric | Benchmark |
|---|---|
| Open rate | 20-25% |
| Click rate | 2-4% |
| Conversion rate | 3-5% |
| Revenue per recipient | Track trend |
| List growth | Track trend |
Revenue Attribution
Klaviyo tracks:
- Email-attributed revenue
- Flow performance
- Campaign ROI
- SMS revenue
Reports
| Report | Insights |
|---|---|
| Flow performance | Automation effectiveness |
| Campaign comparison | Best performers |
| Email deliverability | List health |
| Segment performance | Audience value |
WooCommerce-Specific Features
Coupon Codes
Sync WooCommerce coupons:
- Auto-generated unique codes
- Usage tracking
- Expiration handling
Subscription Support
Works with subscriptions:
- Recurring order events
- Subscription lifecycle
- Renewal reminders
Multi-Currency
Handle international:
- Currency in templates
- Dynamic pricing
- Regional content
Troubleshooting
Data Not Syncing
Causes:
- API key issues
- Plugin conflict
- Server timeout
Solutions:
- Verify API keys
- Check for conflicts
- Increase timeout
- Re-sync manually
Orders Not Tracking
Causes:
- Webhook not set
- Integration disabled
- Plugin outdated
Solutions:
- Check plugin settings
- Verify webhooks
- Update plugin
Klaviyo vs Alternatives
| Feature | Klaviyo | Mailchimp | Omnisend |
|---|---|---|---|
| WooCommerce focus | Good | Good | Good |
| Automation | Excellent | Good | Good |
| Segmentation | Advanced | Basic | Good |
| SMS | Built-in | Separate | Built-in |
| Pricing | Higher | Lower | Mid |
| Best for | Growing brands | Budget | SMB |
Best Practices
List Building
- Offer valuable incentive
- Easy signup process
- Double opt-in
- Clean regularly
Email Strategy
| Stage | Focus |
|---|---|
| Awareness | Welcome series |
| Consideration | Browse abandonment |
| Purchase | Cart abandonment |
| Retention | Post-purchase |
| Re-engagement | Win-back |
Optimization
- Test subject lines
- Optimize send times
- Clean inactive contacts
- Monitor deliverability
2025 Snapshot
Quick benchmarks for the Klaviyo workflow. Use these as planning ranges, then validate against your own data.
| Data point | 2024 | 2025 | Why it matters |
|---|---|---|---|
| Typical core flow setup (welcome + abandoned cart) | 30–60 min | 20–45 min | Estimates time-to-first-value |
| Abandoned cart recovery benchmark | 5–10% | 5–15% | Sets realistic expectations for automation revenue |
| Email ROI benchmark (industry) | ~$36 per $1 | ~$36–$42+ per $1 | Useful for budgeting and vendor comparisons |
| Recommended cadence (SMB) | 1–2 emails/week | 2–4 emails/week | Balances revenue vs list fatigue |
Practical Implementation Notes
Data sync and ownership
Most WooCommerce integrations follow the same lifecycle: a one‑time historical import (customers, products, orders) followed by ongoing incremental updates via API/webhooks. In practice, the biggest failures come from identity and mapping—not from missing features. Before you activate anything customer‑facing, decide which system is the source of truth for customer identity (email vs phone), consent flags, segmentation, and lifecycle fields.
Treat the first week as a controlled rollout. Start with a small segment (internal addresses or a low‑risk cohort), validate that events fire exactly once, and then scale automation volume. This approach prevents silent double‑sending, broken attribution, and hard‑to‑debug “it looks connected but nothing happens” situations.
QA checklist (run once, then reuse)
Use a seed dataset (test customers, a few SKUs, a low‑value test order) to run an end‑to‑end path: signup → first purchase → fulfillment → refund. Confirm that reporting matches your store’s order IDs and timestamps.
Operational checks:
- App permissions/scopes match the features you actually use
- Timezone aligns across scheduled sends, reporting windows, and dashboards
- Edge cases are represented correctly (partial refunds, cancellations, multi‑location fulfillments)
- Baselines are captured so you can measure lift after go‑live
Marketing workflow notes
For email/SMS platforms, prioritize two flows first: welcome and abandoned checkout/cart. Keep early versions simple (one goal per message) and add segmentation only after you’ve validated tracking. A practical sequence is: welcome → abandon → post‑purchase education → win‑back.
Decisions that avoid painful rework:
- Frequency caps per channel (and quiet hours for SMS)
- Consent collection and proof (opt‑in method, opt‑out handling, suppression lists)
- Discount strategy (one‑time codes, expiry windows, exclusions for already‑discounted items)
- Attribution rules (what counts as “assisted” vs “last click”)
Next Steps
After setup:
- Verify sync - Check data in Klaviyo
- Set up flows - Start with essentials
- Build segments - Define audiences
- Create forms - Grow list
- Launch campaigns - Start sending
WooCommerce + Klaviyo implementation checklist (2025)
This section adds practical “make it stable” steps you can use after you install the app/connector. It’s intentionally lightweight: the goal is fewer sync surprises, cleaner reporting, and easier troubleshooting.
1) Quick setup checklist
- Permissions first: grant only the scopes you need (orders/customers/products as required) and document who owns the admin credentials.
- Data mapping: confirm how email, phone, currency, and SKU are mapped between WooCommerce and Klaviyo.
- Historical import: decide how far back to import orders/customers (avoid importing years of data if you don’t need it).
- Deduplication rules: pick one unique identifier per object (usually email for customers, order ID for orders) to prevent doubles.
- Alerts: set a lightweight alert path (email/Slack) for failed syncs, auth expiry, and API rate limits.
2) Data you should verify after connecting
Most integration issues show up in the first hour if you test the right things. Use the table below as a QA checklist (create a test order if needed).
| Data object | What to check | Why it matters |
|---|---|---|
| Customers | Email/phone format, marketing consent fields, duplicates | Prevents double messaging and broken segmentation |
| Orders | Order total, tax, discount, shipping, currency | Keeps revenue reporting and automation triggers accurate |
| Line items | SKU, variant ID, quantity, refunds/returns behavior | Avoids inventory and attribution mismatches |
| Fulfillment | Status changes + timestamps, tracking numbers, carrier fields | Drives customer notifications and post-purchase flows |
| Catalog | Product titles, handles, images, collections/tags | Ensures personalization and reporting match your storefront |
3) Automation ideas for Marketing
- Welcome series: new subscriber → educational sequence + first-purchase offer in Klaviyo.
- Abandoned cart: cart started but not purchased → reminder email/SMS from Klaviyo (timing based on your AOV).
- Post-purchase: order created → delivery/usage tips + cross-sell for complementary products in Klaviyo.
- Win-back: no purchase in 60–90 days → reactivation campaign using Klaviyo segments.
- VIP: customer hits LTV threshold → move into VIP tier and trigger perks via Klaviyo.
API sanity check (WooCommerce REST API)
If your integration UI says “connected” but data isn’t flowing, a quick API call helps confirm whether the store is accessible and returning the objects you expect.
# List the 5 most recent orders (REST)
curl -u ck_your_key:cs_your_secret \
"https://example.com/wp-json/wc/v3/orders?per_page=5&orderby=date&order=desc"Tip: keep tokens/keys in environment variables, and test in a staging store/site before rolling changes to production.
4) KPIs to monitor (so you catch problems early)
- Sync freshness: how long it takes for a new order/customer event to appear in Klaviyo.
- Error rate: failed syncs per day (and which object types fail most).
- Duplicates: number of merged/duplicate contacts or orders created by mapping mistakes.
- Revenue parity: weekly spot-check that WooCommerce totals match downstream reporting (especially after refunds).
- Attribution sanity: confirm that key events (purchase, refund, subscription) are tracked consistently.
5) A simple 30-day optimization plan
- Week 1: connect + map fields, then validate with 5–10 real orders/customers.
- Week 2: enable 1–2 automations and measure baseline KPIs (conversion, AOV, repeat rate).
- Week 3: tighten segmentation/rules (exclude recent buyers, add VIP thresholds, handle edge cases).
- Week 4: document the setup, create an “owner” checklist, and set a recurring monthly audit.
Related integration guides
More marketing tools: Klaviyo email automation, Mailchimp integration, HubSpot integration.
Sources
For WooCommerce Mailchimp, see WooCommerce Mailchimp integration. For HubSpot, check WooCommerce HubSpot integration.