CONNECTIONS / WordPress
Whatever runs commerce on your WordPress site, delivered.
A WordPress site rarely sells through a single plugin: WooCommerce handles the cart on some, Easy Digital Downloads or a lead form handles it on others. Signals reads whichever order, lead, or checkout event your stack actually fires and delivers it server-side to every platform you advertise on.
- ● wordpress :: signals live
- > Form submitted value=0.00 lead
- > Order completed value=96.00 GBP
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok
- ✓ 3 destinations synced · match 74%
The signal WordPress yields.
Every kind of signal that moves between WordPress and the platforms, through one hashed, deduplicated route.
- Web conversions
- Whichever plugin generates the sale, WooCommerce, Easy Digital Downloads, or a checkout add-on, its order event maps to purchase and routes server-side the same way.
- Offline conversions
- A lead form submitted through a plugin like Gravity Forms maps as a conversion event of its own, useful for sites where the real business result is a form fill, not a cart.
- Custom audiences
- An identifier captured anywhere on the site, whether from a checkout field or a lead form, is SHA-256 hashed at ingestion before it is used for matching.
Pick your platform. Every use case for it, in one place.
Every way WordPress data moves, grouped by platform and ranked by how many use cases WordPress 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
Scoped API access set up against the site, pointed at whichever commerce or forms plugin generates the events worth tracking.
-
Map
Site events, whether an order, a form submission, or a checkout step, mapped to each destination's event schema in the visual mapper.
-
Hash and dedupe
Identifiers hashed with SHA-256 at ingestion; no PII is stored on host servers in Datahash Cloud, and a self-hosted Core deployment is available where data cannot leave the perimeter.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
WordPress questions, answered.
Is this the same connector as WooCommerce?
No. WooCommerce has its own connector built around its order and checkout hooks. This one covers the broader WordPress site, useful when commerce runs through a different plugin, or when leads and form fills matter as much as completed orders.
Which WordPress events can be synced?
Orders, refunds, and form submissions from whichever plugin the site runs, plus checkout steps where a plugin exposes them. Most teams map completed orders or qualified leads first, then add upper-funnel events once match rate looks solid, rather than mapping every available event on day one.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud. A self-hosted Core deployment is available for sites where data cannot leave the perimeter at all, with the same event mapping and destination list either way.
What if the site runs a page builder instead of a standard theme?
Page builders like Elementor or Divi do not change how events reach Signals, since capture happens at the plugin or API level, not in theme markup. A redesign of the page layout does not break delivery, because nothing about the connection depends on how a page renders.
NEXT STEP
See your WordPress data working in every ad platform.
Ready to enable a use case, or still mapping what WordPress data could do? Our team helps you find the right place to start.
