Home
Connectors
WooCommerce - Postscript

Postscript

Send every WooCommerce event to Postscript, server-side

Q: How do I check that WooCommerce events are reaching Postscript?

Open Postscript › Subscribers › the individual subscriber's activity feed.

Q: Can one purchase trigger the same flow twice?

No. One order produces one event, so a single purchase cannot trigger the same flow twice.

Q: How long does it take to connect WooCommerce to Postscript?

Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, Postscript included.

Each event is resolved to a person against a 750M+ device graph before it reaches Postscript, so flows trigger on a known profile rather than an anonymous session.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a WooCommerce event reaches Postscript. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from WooCommerce

Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.

See the WooCommerce integration

WooCommerceWhat it sends

order_idWooCommerce order number
billing_email / phonecheckout contact fields
customer_idWordPress user, when logged in
line_itemsproducts and quantities
order_totalorder value after discount

02 Understand

Resolved to one person before it leaves

Every WooCommerce event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved before it is sent

IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.
DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Postscript

Send identity-resolved events to Postscript so SMS flows reach subscribers the pixel missed.

See the Postscript integration

PostscriptWhat it receives

phonesubscriber key
emailprofile matching
order / cart propertiesautomation triggers

The catch

WooCommerce identifies logged-in users cleanly and guests barely at all, so the flows work well for repeat account-holders and silently skip most first-time buyers.

Where to check in PostscriptSending you can audit

Postscript Subscribers the individual subscriber's activity feed

What changes

What changes when WooCommerce feeds Postscript. Two gains on the Postscript side, two on the WooCommerce side.

Postscript

Server-side delivery

Events reach Postscript through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

Postscript

Identity-resolved events

Events sent to Postscript carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

WooCommerce

Every event, server-side

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

WooCommerce

One setup, every destination

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

Setup

Live in under 20 minutes.

Connect WooCommerce once and every destination, Postscript included, is forwarded the same resolved events.

Upstack dashboardExample

WooCommerce Data source Connected

Postscript Destination Healthy

Read the full Postscript setup guide

01

Connect WooCommerce

Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.
02

Add the Postscript destination

Under Destinations, add Postscript. Every resolved WooCommerce event is then forwarded to it.
03

Check delivery to Postscript

Trace any event to the profile it resolved to, and see why.