Connectors

WooCommerce

Track orders, refunds, and cancellations from WooCommerce using native webhooks.

WooCommerce sends webhooks natively, so you write no server-side code to forward events. Install a small plugin for session matching, then register the webhooks in your WooCommerce admin.

Event mapping

WooCommerce topic	WC order status	TrustData event	Shopify equivalent
`order.created`	`processing`, `completed`	`purchase`	`orders/paid`
`order.updated`	`refunded`	`refund`	`orders/updated` (with refunds)
`order.updated`	`cancelled`, `failed`	`refund`	`orders/cancelled`

Before you start

You need:

The TrustData JS SDK installed on your storefront (see JavaScript SDK)
Your Attribution ID from Settings → Attribution IDs

During checkout, the TrustData plugin saves the visitor ID from the browser to order meta. WooCommerce then includes it in webhook payloads, which lets TrustData match the order to the original ad click.

Download trustdata-woocommerce.zip from the GitHub releases
In your WordPress admin, go to Plugins → Add New → Upload Plugin
Select the ZIP file → click Install Now → Activate

There is nothing to configure. The plugin works as soon as you activate it.

Step 2: Register webhooks in WooCommerce

Go to WooCommerce → Settings → Advanced → Webhooks → Add webhook.

Create two webhooks:

Order created

Field	Value
Name	`TrustData Order created`
Status	Active
Topic	Order created
Delivery URL	`https://t.trustdata.tech/webhooks/woocommerce/YOUR_ATTRIBUTION_ID/orders`
Secret	Generate a random string and copy it
API version	WP REST API Integration v3

Order updated

Field	Value
Name	`TrustData Order updated`
Status	Active
Topic	Order updated
Delivery URL	`https://t.trustdata.tech/webhooks/woocommerce/YOUR_ATTRIBUTION_ID/orders`
Secret	Same secret as above
API version	WP REST API Integration v3

Replace YOUR_ATTRIBUTION_ID with your Attribution ID from the TrustData dashboard.

Both webhooks share the same endpoint URL and secret. WooCommerce sends the topic in the X-WC-Webhook-Topic header.

How session matching works

The JS SDK sets a _trdt_vid cookie when a visitor lands on your store. At checkout, the TrustData plugin reads this cookie and saves it to the WooCommerce order as _td_visitor_id meta. WooCommerce includes all order meta in the webhook payload, so TrustData receives the visitor ID alongside the order data.

Loading diagram…

Troubleshooting

Conversions not attributed

Confirm the TrustData plugin is active
Check that _trdt_vid appears in browser DevTools → Application → Cookies on your storefront
In WooCommerce → Webhooks, check the Delivery log for the webhook. A 200 response means TrustData received it
In the TrustData dashboard → Webhooks tab → Recent Activity, check session_matched. A value of false means TrustData received the webhook but found no session

Webhook delivery failures

Confirm the Delivery URL contains the correct Attribution ID
Check that the webhook Status is set to Active
WooCommerce retries failed deliveries automatically. Check the delivery log for error details

PrestaShop

Track orders, refunds, and signups from PrestaShop using the TrustData module.

How attribution works

Understand how TrustData attributes conversions to marketing touchpoints.