Skip to content

WooCommerce Intercom Sync

WooCommerce Intercom Sync for Customers, Orders & Events

Customers, orders, cart events, and store metrics land on the Intercom contact so agents and Series see what shoppers actually did.

WooCommerce customers, orders, and events syncing into Intercom
Pain → Solution

When Intercom does not match the store

If agents open a ticket and still lack the order, cart events never start a Series, or you are patching the gap with Zapier and CSV, Sync Engine puts those store facts on the Intercom contact.

What teams struggle with
  • Agents open a ticket and still lack orders, LTV, or last purchase
  • Abandoned carts and checkouts never become Intercom events
  • Zaps and CSV exports lag behind real purchases and refunds
What Sync Engine does
  • Customers, orders, carts, and store metrics land on the Intercom contact
  • Subscriptions, Bookings, and Deposits events sit in the same sync
  • Install, connect OAuth or an Access Token, turn on store sync. HPOS compatible

Keep purchase history on the Intercom contact. Orders, carts, and metrics sync from WooCommerce as they happen.

Outcomes

Purchase context in every conversation

Woo stays the store of record. Intercom gets the customer journey your Series and Inbox already need.

Fewer manual lookups

Agents see order status, totals, and last purchase on the contact instead of digging through Woo mid-ticket.

Better store targeting

Segment by LTV, AOV, VIP / At-Risk, and cart activity so a win-back Series does not also mail someone who ordered yesterday.

Events that fire Series

Order, cart, checkout, and subscription events reach Intercom when they happen on the store, not after a weekly export.

Customers

Store customers become Intercom contacts

Align Woo customers with Intercom contacts, including Woo-sourced fields, custom mappings, and store metrics.

Profile fields

Email, name, phone from Woo billing, avatar, signup, and last activity.

Attributes & metrics

Custom attribute mapping and store metrics (LTV, AOV, segments) land on the contact for Series and Inbox.

Requirements

WooCommerce 8.0+ for store features. HPOS compatible. WordPress user and role sync works with or without Woo.

Orders

Order lifecycle on the contact

Order created, completed, and refunded, without double-sending the same order. Agents see purchase history without leaving Intercom.

Order events

Order created, order completed, and order refunded. The same order is not sent twice.

What agents see

Order status, total, currency, items, shipping, and payment method on the contact.

Runs on your site

Sync runs in the background on your WordPress site and stays within Intercom’s normal API limits.

Cart & checkout

Cart activity that Series can use

Cart and checkout events with abandonment delays from 30 minutes to 24 hours. Placing an order cancels the pending abandonment job.

Cart events

Cart item added starts enabled. Also: cart item removed, cart emptied, cart viewed, and checkout reached.

Abandonment

Cart abandoned and checkout abandoned for logged-in shoppers. Delays: 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, or 24 hours (default 1 hour).

Browse & more

Product viewed and category viewed (deduped 30 min), site search (5 min), product reviewed including guests. Wishlist and coupon events included.

Metrics & segments

Facts already on the contact

You still build Series and Inbox rules in Intercom. Sync Engine’s job is making sure LTV, AOV, and segments are already there.

Store metrics

LTV after refunds, total revenue, refunds, AOV, order count, items, first/last order, days since last order, average days between orders, category, and payment method.

Segments

New (early lifecycle). VIP (LTV ≥ 1000 or ≥ 10 orders). At-Risk (more than 90 days since last order). Regular for everyone else in the active middle.

Inbox impact

Support opens a ticket and already sees last order date and LTV. VIP gets different macros. At-Risk feeds win-back Series.

Subscriptions

Subscriptions, Bookings, Deposits

WooCommerce Subscriptions, Bookings, and Deposits events sit in the same event set. Status changes reach Intercom with the fields agents need.

Subscription events

Status changed, paused (on-hold or paused), purchased, renewed, trial ended, cancelled, and expired.

Purchase details

Purchased and renewed events include next payment date, product name, billing period, and amount.

Bookings & Deposits

Bookings and Deposits events sit alongside Subscriptions. Enable them under Events → Plugins.

Guest checkout

Guest leads merge when shoppers register

Guest buyers become Intercom leads. When they register, history merges into the user contact so it is not split across two profiles.

Guest → lead

Guest checkout creates an Intercom lead with the order history attached.

Register → merge

When the shopper registers, history merges into the user contact. One profile, not two.

Why it matters

Without merge, agents chase a lead and a user for the same buyer. Guest checkout is a common Woo gap Zapier rarely handles cleanly.

Who it’s for

Woo on the store.
Intercom in the inbox.

Woo stores that need orders, carts, and metrics on the Intercom contact so support and Series run on store truth.

  • Woo stores on Intercom

    Orders, carts, and LTV on the contact so agents see purchase history without leaving Intercom.

  • Membership + Woo

    LMS and membership sites that also sell on Woo: role tags plus order history on one Intercom contact.

  • Subscription stores

    WooCommerce Subscriptions status, renewals, and next payment date on the contact for Series and Inbox.

  • Agencies

    One install path per client Woo store: orders and metrics in the inbox without custom glue.

Getting started

Install once. Sync keeps running.

Install the plugin, connect your Intercom workspace, then choose what from the store should sync.

  1. 01

    Install the plugin

    Grab Sync Engine for Intercom from the WordPress.org listing and activate it. Store features need WooCommerce 8.0+ (HPOS compatible).

  2. 02

    Connect your workspace

    Sign in with OAuth, or paste an Access Token if that is how your team manages Intercom. Hit test connection until it says Connected.

  3. 03

    Turn on what you need

    Flip on the Woo events, metrics, and field mappings that matter. Messenger and identity verification stay optional.

Want screenshots and checklists? See How to connect Intercom to WordPress.

Pricing

Free vs Pro for Woo stores

If your job is Woo orders, carts, KPIs, or subscriptions in Intercom, plan on Pro. Free is the install-and-connect path, plus useful WP user sync.

Free
$0 / forever

WordPress user sync, role tags, and 3 WordPress events, plus optional Messenger.

Included

  • ✓ Basic WordPress user sync
  • ✓ 3 basic WP events
  • ✓ Basic role tags
  • ✓ Event prefix
  • ✓ Optional Messenger + IDV
  • ✓ Email support

Start free to connect and sync WordPress users. Store orders, carts, and metrics need Pro ($99/ year, billed yearly).

Other options

Tried Zapier, CSV, or a custom build?

Those can move an order across now and then. Keeping Woo orders, carts, and metrics current on every Intercom contact is a different job, and that is what Sync Engine is for.

  • CSV

    A checked export is fine once a month. It misses the order that completed after you downloaded the file.

  • Zapier

    One Zap can send a new order across. Always-running attributes, metrics, and subscriptions turn into several Zaps someone has to watch.

  • Custom build

    A custom integration means you write and maintain the connection. Sync Engine for Intercom is the ready-made WooCommerce to Intercom path.

FAQ

Questions store teams ask first

Orders, carts, Zapier, and what lands on the Intercom contact when you sync from Woo.

Talk something through with us
Does this sync WooCommerce orders to Intercom?
Yes. Order created, completed, and refunded events land on the contact with status, total, currency, items, shipping, and payment method, without double-sending the same order.
What’s included?
See plans and limits for the full Free vs Pro breakdown.
Can I sync abandoned carts?
Yes: cart and checkout events with abandonment delays from 30 minutes to 24 hours. See the abandoned cart guide.
Zapier already sends some orders.
Possible. Always-running attributes, metrics, and subscriptions are a different maintenance job. See the Zapier comparison.
Guest checkout?
Leads on guest purchase; merge on register. See the guest checkout guide.
Do I need Zapier?
No. Sync Engine connects WooCommerce to Intercom directly.
We already have Messenger on the store.
Keep it. Sync Engine’s job is purchase data on the contact: orders, carts, metrics. Messenger and identity verification stay optional if you want them from the same plugin.
WordPress users without Woo?
Get started

Put order history in every Intercom conversation

Install Sync Engine for Intercom, connect with OAuth or an Access Token, and put WooCommerce orders, carts, and metrics on every Intercom contact.