Can I tag customers based on order value ranges?

Yes, add a router path with a numeric filter on the 'total' field. Set conditions like 'greater than 100' for VIP tags.

What happens if a customer orders multiple product categories?

They'll get all applicable tags. Use Make's array functions to iterate through line_items and apply multiple category tags to one subscriber.

How do I handle refunded orders?

Add a filter after WooCommerce to check order status. Only process 'completed' status orders, or set up a separate scenario to remove tags on refunds.

Can I update existing Mailchimp subscribers instead of just adding new ones?

Set the Mailchimp action to 'Add/Update Subscriber' and enable the update_existing parameter. This adds tags to existing subscribers rather than creating duplicates.

Beginner~12 min setupMarketing & E-commerceVerified April 2026

How to Tag Mailchimp Customers by WooCommerce Purchase with Make

Automatically tag new customers in Mailchimp based on their WooCommerce purchase to trigger product-specific email sequences.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Make

Also on:Zapier N8n Power-automate Pipedream

Best for

E-commerce stores that need product-specific email sequences based on what customers actually bought.

Not ideal for

Simple welcome emails that don't vary by product or stores with very low order volume.

Sync type

polling

Use case type

sync

Real-World Example

💡

A 12-person outdoor gear company uses this to tag customers who buy camping gear vs hiking boots vs climbing equipment. Before automation, they manually segmented 200+ monthly orders into product categories every week, often missing time-sensitive follow-ups for gear maintenance tips and seasonal product recommendations.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Make

Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

WooCommerce store with REST API enabled and Consumer Key/Secret generated

Active Mailchimp account with at least one audience list created

Email automation sequences set up in Mailchimp that trigger on specific tags

Make account with available operations (free tier includes 1,000/month)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Customer Email	`billing_email`	Primary email address from WooCommerce billing info, maps to Mailchimp subscriber email
Product Names	`line_items.name`	Array of purchased product names, used to determine which tags to apply
Order Date	`date_created`	When the order was placed, prevents duplicate processing of old orders

3 optional fields▸ show

First Name	`billing_first_name`	Customer's first name for email personalization in Mailchimp
Order Total	`total`	Total order value, useful for VIP customer tags based on purchase amount
Product Categories	`line_items.categories`	Product category data for broader segmentation beyond individual products

Step-by-Step Setup

Dashboard > Create new scenario > + > WooCommerce

Create new scenario in Make

Set up the foundation for your WooCommerce to Mailchimp automation. This creates the workspace where you'll build the trigger-to-action flow.

1Click 'Create a new scenario' from your Make dashboard
2Click the large '+' circle in the center
3Search for 'WooCommerce' in the apps list
4Select WooCommerce from the results

✓ What you should see: You should see a WooCommerce module placed in your scenario canvas with configuration options available.

WooCommerce module > Watch Orders > Connection

Configure WooCommerce order trigger

Set up the trigger that fires when someone completes a purchase. This watches for new orders and kicks off your email tagging sequence.

1Select 'Watch Orders' from the WooCommerce trigger options
2Click 'Add' next to Connection to create new WooCommerce connection
3Enter your WooCommerce store URL (including https://)
4Paste your Consumer Key and Consumer Secret from WooCommerce API settings
5Click 'Save' to establish the connection

✓ What you should see: The connection shows 'Successfully verified' and you see fields for Limit and Order Status filters.

⚠

Common mistake — Don't use 'Watch Order Updates' — that fires on every status change, including refunds and cancellations

Make

click +

search apps

Mailchimp

Configure WooCommerce order …

Mailchimp

module added

WooCommerce module > Settings

Set order status filter

Configure the trigger to only fire on completed purchases, not pending or processing orders. This prevents premature email sequences from starting.

1Set Limit to 10 (processes up to 10 new orders per run)
2Click the Status dropdown
3Select 'completed' from the status options
4Leave other fields at default values

✓ What you should see: The trigger configuration shows Status: completed and Limit: 10.

⚠

Common mistake — Using 'processing' status will trigger emails before payment clears — stick with 'completed'

Mailchimp

trigger

filter

Status

matches criteria?

yes — passes through

no — skipped

WooCommerce

notified

Scenario canvas > + > Mailchimp > Add/Update Subscriber

Add Mailchimp module

Connect Mailchimp as the destination where you'll add tags based on purchase data. This creates the action that responds to new WooCommerce orders.

1Click the '+' button to the right of your WooCommerce module
2Search for 'Mailchimp' in the apps directory
3Select Mailchimp from the results
4Choose 'Add/Update Subscriber' from the actions list

✓ What you should see: A Mailchimp module appears connected to WooCommerce with configuration options visible.

Mailchimp module > Connection > Add

Connect Mailchimp account

Authenticate your Mailchimp account so Make can add tags to your subscribers. This establishes the permission to modify your email lists.

1Click 'Add' next to Connection in the Mailchimp module
2Click 'Sign in with Mailchimp' button
3Log into your Mailchimp account in the popup window
4Click 'Allow' to grant Make access to your account
5Verify the connection shows your Mailchimp username

✓ What you should see: Connection status shows green with your Mailchimp account name displayed.

⚠

Common mistake — If you have multiple Mailchimp accounts, double-check you're connecting the right one — Make doesn't show account details until after connecting

Make settings

Connection

Choose a connection…Add

click Add

Mailchimp

Authorize Make

popup window

✓

Connected

green checkmark

Mailchimp module > Audience

Select target audience

Choose which Mailchimp list receives the tagged customers. This determines where your post-purchase email sequences will pull subscribers from.

1Click the Audience dropdown in the Mailchimp module
2Select your main customer list from the dropdown
3Verify the list name matches your intended email sequence audience

✓ What you should see: The Audience field shows your selected list name and loads additional configuration options below.

⚠

Common mistake — Don't select a general newsletter list — choose the list that feeds your product-specific email sequences

Mailchimp module > Email Address

Map customer email field

Connect the customer's email address from WooCommerce to Mailchimp's subscriber field. This ensures the right person gets tagged and added to sequences.

1Click in the Email Address field in the Mailchimp module
2Select 'billing_email' from the WooCommerce data dropdown
3Verify the field shows the mapped WooCommerce email variable

✓ What you should see: Email Address field displays '{{1.billing_email}}' showing the connection to WooCommerce order data.

⚠

Common mistake — Use billing_email, not shipping_email — billing email is required for orders while shipping email can be empty

Mailchimp fields

email_address

status

merge_fields.FNAME

merge_fields.LNAME

tags[0].name

available as variables:

1.props.email_address

1.props.status

1.props.merge_fields.FNAME

1.props.merge_fields.LNAME

1.props.tags[0].name

Mailchimp module > First Name, Last Name

Configure customer name mapping

Pull the customer's name from WooCommerce into Mailchimp for personalized emails. This populates subscriber details for your email sequences.

1Click in the First Name field
2Select 'billing_first_name' from WooCommerce order data
3Click in the Last Name field
4Select 'billing_last_name' from the dropdown

✓ What you should see: Name fields show '{{1.billing_first_name}}' and '{{1.billing_last_name}}' mappings.

Mailchimp module > Tags > Add item

Add product-based tags

Create tags based on what the customer bought so Mailchimp can trigger the right email sequence. This is the core logic that personalizes follow-up emails.

1Scroll down to the Tags section in the Mailchimp module
2Click 'Add item' to create your first tag rule
3In the tag field, type a static tag like 'purchased-electronics'
4Click 'Add item' again to add more product-specific tags as needed

✓ What you should see: Tags section shows your product category tags that will be applied to new subscribers.

⚠

Common mistake — Keep tag names consistent with your Mailchimp automation triggers — mismatched tag names won't fire your email sequences

Between modules > + > Router > Add route

Set up conditional product tagging

Use Make's router to apply different tags based on specific products purchased. This allows for precise email sequence targeting.

1Click the '+' button after WooCommerce but before Mailchimp
2Select 'Router' from the flow control options
3Click 'Add route' to create product-specific paths
4Set up filters for each route based on line_items product names

✓ What you should see: Router appears between WooCommerce and Mailchimp with multiple conditional paths for different products.

⚠

Common mistake — WooCommerce line_items is an array — you'll need to use 'contains' operators, not exact matches

Scenario controls > Run once

Test the automation

Run a test to verify tags are applied correctly when new orders come through. This catches configuration errors before going live.

1Click 'Run once' at the bottom of your scenario
2Place a test order in your WooCommerce store
3Wait 2-3 minutes for the trigger to detect the new order
4Check your Mailchimp audience for the new subscriber with correct tags

✓ What you should see: Test run shows green checkmarks on all modules and your Mailchimp list contains the test customer with appropriate product tags.

⚠

Common mistake — Use a real email address you control for testing — you'll need to verify the tags actually appear in Mailchimp

Make

▶ Run once

executed

✓

Mailchimp

✓

WooCommerce

🔔 notification

received

Scenario controls > Toggle ON > Scheduling

Activate the scenario

Turn on the automation to start tagging customers automatically. This puts your post-purchase email sequences into production.

1Click the toggle switch in the bottom left to 'ON' position
2Set scheduling to 'Every 15 minutes' for regular order checking
3Click 'OK' to confirm activation
4Verify the scenario status shows 'Active' with a green indicator

✓ What you should see: Scenario dashboard shows your automation as Active with the next scheduled run time displayed.

Drop this into a Make custom function.

Copy this template{{map(1.line_items; "name")}}

▸ Show code

{{map(1.line_items; "name")}}

... expand to see full code

{{map(1.line_items; "name")}}

Scaling Beyond 300+ orders/day+ Records

If your volume exceeds 300+ orders/day records, apply these adjustments.

Batch process orders

Increase the WooCommerce trigger limit to 50 orders per run and reduce scenario frequency to every 30 minutes. This reduces API calls and operation usage.

Use webhook instead of polling

Switch from 'Watch Orders' to a webhook trigger. Set up a WooCommerce webhook pointing to your Make webhook URL to get instant notifications without polling limits.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Set WooCommerce connection timeout to 30 seconds to handle slow API responses

Applies when: Always

Add error handling route for Mailchimp 'Invalid Email' responses

Applies when: Always

Configure scenario to stop on consecutive errors to prevent API rate limit bans

Applies when: High volume

Test with orders containing 5+ line items to verify array processing works correctly

Applies when: Always

Set up Make's incomplete execution storage for orders that partially fail tagging

Applies when: Enterprise

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if you need complex product-based tagging rules or want to process multiple line items differently. Make's router and array functions handle WooCommerce's nested order data better than Zapier's limited formatter options. Skip Make if you just need basic 'purchased anything' tagging — Zapier's WooCommerce integration is simpler for single-path workflows.

Cost

This workflow uses 2 operations per order (WooCommerce trigger + Mailchimp update). At 150 orders/month, that's 300 operations total. That fits Make's free tier at 1,000 operations/month. Zapier's free tier only covers 100 tasks, so you'd need their $20 Starter plan. N8n is free but requires hosting at $5-15/month.

Tradeoffs

Zapier handles WooCommerce webhook setup automatically while Make requires manual REST API configuration. N8n offers better error retry logic with exponential backoff built-in. But Make wins on array processing — WooCommerce orders contain multiple line items and Make's iterator handles product-specific tagging without custom code.

WooCommerce's REST API paginates at 10 orders per request, so high-volume stores hit rate limits fast. Set your scenario to run every 15 minutes max — more frequent polling gets throttled. Mailchimp's tag API is slow, taking 3-5 seconds per subscriber update. Orders with multiple products create separate tag requests, so a 5-item order takes 15+ seconds to process fully.

Ideas for what to build next

→
Add purchase value segmentation — Create additional router paths that tag customers as 'high-value' or 'bulk-buyer' based on order totals and quantities.
→
Set up abandoned cart recovery — Build a companion scenario that removes 'cart-abandoned' tags when customers complete purchases tracked by this automation.