CONNECTIONS / WooCommerce
WooCommerce orders, hashed and routed server-side.
WooCommerce already fires order and checkout hooks across a WordPress store. Signals reads those native webhooks and delivers the same order, cart, and refund events server-side to every platform you advertise on, deduped against whatever pixel plugin is already installed.
- ● woocommerce :: signals live
- > Order created value=142.50 EUR
- > Order status processing
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 81%
The signal WooCommerce yields.
Every kind of signal that moves between WooCommerce and the platforms, through one hashed, deduplicated route.
- Web conversions
- An order placed on a WooCommerce store fires the order.created webhook, which Signals reads over the REST API and routes server-side to every mapped destination, no separate tracking plugin required.
- Offline conversions
- Cart-updated hooks that fire as line items change give upper-funnel platforms a signal earlier than the completed order, for campaigns optimizing on intent rather than purchase alone.
- Custom audiences
- A refund or cancellation processed in WooCommerce posts back to the same order record, so a destination that supports revenue adjustment reflects what was actually kept.
Pick your platform. Every use case for it, in one place.
Every way WooCommerce data moves, grouped by platform and ranked by how many use cases WooCommerce supports.
Google 4 
Meta 4 
Snap 3 
TikTok 3 
LinkedIn 2 
OpenAI 2 
Pinterest 1 
Reddit 1 
X 1 - Web conversions Google Enhanced Conversions Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Meta Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Web conversions Meta Messenger Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Snapchat Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions TikTok Events API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
From authorization to delivered signal.
-
Connect
A scoped WooCommerce REST API key authorizes read access to orders, cart, and customer events. Nothing installs on top of the existing WooCommerce plugin.
-
Map
WooCommerce order statuses and hooks mapped to each destination's event schema in the visual mapper, including refunds and cancellations.
-
Hash and dedupe
Identifiers hashed with SHA-256 and deduped against any Meta or Google pixel plugin already running on the storefront.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
WooCommerce questions, answered.
Does this require installing another WooCommerce plugin?
No. Ingestion runs on WooCommerce's native REST API and webhooks, so nothing new sits in the WordPress plugin list, and a theme or WooCommerce update does not risk breaking event capture the way a bundled tracking plugin sometimes does. The scoped API key is the only credential the store needs to issue.
Do we remove our existing Meta or Google pixel plugin?
No. Keep it running for on-site tracking. Signals dedupes against that plugin's events on a shared event ID, so both deliver without a single order getting counted twice toward the same campaign, and you can compare match rates between the two before deciding anything.
How are WooCommerce order statuses handled, since an order changes state after checkout?
Each status transition, from pending to processing to completed or refunded, maps to its own event in the visual mapper. Most stores map completed orders to purchase and leave earlier states available for upper-funnel optimization, since not every status change is worth a destination's attention.
What happens with a guest checkout that has no WordPress user account?
WooCommerce does not require an account to check out, and Signals does not either. Whatever identifier the order carries is hashed and used for matching; an order with no email or phone still delivers as an event, just with a lower match rate.
NEXT STEP
See your WooCommerce data working in every ad platform.
Ready to enable a use case, or still mapping what WooCommerce data could do? Our team helps you find the right place to start.
