Skip to main content
Upstack Data

WooCommerce to Loops

Forward every WooCommerce event to Loops server-side, resolved to a person against a 750M+ device graph — so records and reporting reflect the person, not the device.

What changes

What changes when WooCommerce feeds Loops.

Server-side delivery

Events reach Loops through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.

Identity-resolved events

Every event sent to Loops carries a resolved customer, matched against a 750M+ device graph.

Every event, server-side

Storefront and checkout events are captured from WooCommerce on the server, independent of the browser.

One setup, every destination

Connect WooCommerce once and forward to every ad platform, email tool and warehouse you run.

What actually moves

What WooCommerce carries, and what Loops needs.

WooCommerce and Loops describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what WooCommerce can put on an event, the right is what Loops can actually use.

WooCommerce sends

order_id
WooCommerce order number
billing_email / phone
checkout contact fields
customer_id
WordPress user, when logged in
line_items
products and quantities
order_total
order value after discount

Loops receives

email
contact key
event name
what the lifecycle message reacts to
data variables
personalisation

Records you can audit

How you know it is working.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

  • Per-record inspection

    Trace any property back to the event that set it.
  • Deduplication

    One person, one record, across devices and identifiers.
  • Bot and fraud filtering

    Automated traffic never becomes a contact.

Where to check in Loops

Loopsthe contact's event history.

Get WooCommerce talking to Loops.

A 15-minute walkthrough of this connector on your own account.