SOLUTION / WOOCOMMERCE

Server-side attribution for WooCommerce, compliant by default

TrackLayer gives WooCommerce stores server-side conversion events without fragile theme snippets, pixel plugins, or checkout hacks. It enriches consented WordPress order data with EMQ confidence intervals and anomaly auto-pause before Meta, Google, TikTok, Pinterest, and Snapchat receive the payload.

woocommerce_thankyouWP hookcaptured

order.updatedWebhookenriched

purchaseMeta CAPIaccepted

refundDestinationsdeduped

WOOCOMMERCE SIGNAL PIPELINE

§ 01

Why WooCommerce stores need this

42%

median Meta event match quality without server-side

38%

of Safari users blocked from conversion tracking

7-day

ITP cookie window vs 90-day attribution

§ 02

What TrackLayer does for WooCommerce

WordPress plugin

One-click install from WordPress Plugins with a lightweight 5MB plugin and no theme edits.

WooCommerce hooks auto-wired

Purchase, refund, subscription, and cart-recovery events are captured from native WooCommerce hooks.

Consent Mode bridge

Pandectes, CookieYes, and Complianz consent states are forwarded with each event before routing.

Multi-store networks

WP multisite and WooCommerce multi-store setups can route stores into one TrackLayer workspace.

Checkout event capture

Stripe, PayPal, and Klarna checkout signals are captured, enriched, and deduplicated server-side.

HPOS-compatible

Built for WooCommerce High-Performance Order Storage, with HPOS on or off during migration.

§ 03

Installation in 3 steps

Install TrackLayer from WP Plugins

Activate the plugin and paste your API key

Connect ad platforms via OAuth in the TrackLayer dashboard

§ 04

Webhook to CAPI

WooCommerce order webhook JSON

{
  "id": 10492,
  "number": "WC-10492",
  "status": "processing",
  "currency": "EUR",
  "total": "148.00",
  "billing": {
    "email": "maya@example.com",
    "phone": "+4915123456789"
  },
  "customer_ip_address": "203.0.113.42",
  "customer_user_agent": "Mozilla/5.0 ...",
  "meta_data": [
    { "key": "_fbclid", "value": "IwAR3..." },
    { "key": "_consent_state", "value": "granted" }
  ],
  "line_items": [
    { "sku": "BNDL-3", "quantity": 1 }
  ]
}

Meta CAPI POST body after enrichment

{
  "event_name": "Purchase",
  "event_time": 1776942360,
  "event_id": "woocommerce_10492",
  "action_source": "website",
  "event_source_url": "https://store.com/checkout/order-received/10492",
  "user_data": {
    "em": ["a8f5f167f44f4964..."],
    "ph": ["c8d96c5a0e9b2c49..."],
    "fbc": "fb.1.1776942000.IwAR3...",
    "client_ip_address": "203.0.113.42",
    "client_user_agent": "Mozilla/5.0 ..."
  },
  "custom_data": {
    "currency": "EUR",
    "value": 148.00,
    "value_usd": 158.36,
    "content_ids": ["BNDL-3"],
    "content_type": "product"
  }
}

PRICING FOR GROWING STORES

From $79/mo. Matches Shopify plans.

Compare plans

§ 05

Merchant proof

"After 3 years on SEGMENT + a half-broken Facebook plugin, TrackLayer replaced both with one toggle."

CTO at a 40k SKU WooCommerce store

§ 06

FAQ

Is it compatible with WooCommerce Subscriptions?

Yes. TrackLayer captures initial purchases, renewals, failed payments, refunds, and cancellations from WooCommerce Subscriptions events, then maps them to the destinations that support lifecycle signals.

Does HPOS need to be on or off?

Either state works. TrackLayer reads from the current WooCommerce order storage layer and remains compatible during HPOS migrations, so stores can switch when their plugin stack is ready.

What about multi-currency via WPML or Currency Switcher?

TrackLayer keeps the order currency from WooCommerce and can forward both the source value and normalized reporting value for stores using WPML, Currency Switcher, or similar multi-currency plugins.

Does it work with WordPress cache plugins?

Yes. The plugin uses server-side WooCommerce hooks and checkout callbacks, so caching layers like WP Rocket, LiteSpeed Cache, and W3 Total Cache do not block purchase capture.

Where is data stored for EU and US merchants?

Workspaces can be provisioned in EU or US regions. Consent state, hashed identifiers, and destination routing controls are kept region-aware for merchant data residency requirements.

§ 07

Built for WooCommerce

EMQ confidence intervals

Statistical match-quality bands per destination.

Anomaly auto-pause

Pause spend when delivery drift is detected.

Audit chain integrity

Immutable event logs for compliance review.

READY FOR SERVER-SIDE WOOCOMMERCE ATTRIBUTION

Start with the WordPress plugin, then verify live events in minutes.

Download from WordPress.org →Read the docs →