AxiTrace for WooCommerce

com. Every purchase, add-to-cart, begin-checkout, and add-payment-info event is captured and forwarded to your ad platforms – reaching customers that browser-based pixels miss entirely.

Why server-side tracking?

Browser pixels can be blocked by ad blockers, restricted by iOS Intelligent Tracking Prevention, and refused via cookie consent banners. Server-side events travel directly from your WooCommerce server to Facebook CAPI, TikTok Events API, Google Ads, and Google Analytics 4, so conversions are still recorded when the browser pixel cannot fire.

Deduplication so you never double-count

AxiTrace generates a deterministic UUID v5 event ID for every WooCommerce order. The same event ID is attached to both the browser-side purchase pixel fire and the server-side purchase event. Facebook CAPI, TikTok Events API, and Google Ads use that shared event ID to deduplicate automatically – each conversion is counted exactly once, regardless of how many times the confirmation page loads or how many pixels fire.

Server-side AddToCart events

AxiTrace sends AddToCart events server-side, triggered by the WooCommerce woocommerce_add_to_cart hook. This records add-to-cart activity from the server, so the event is captured even when the browser-side pixel is blocked or restricted.

Full checkout funnel

InitiateCheckout carries your real cart total and currency (not a placeholder zero), and AddPaymentInfo fires the moment a shopper selects a payment method – giving Facebook, TikTok, and Google Ads the mid-funnel signal they need to optimize toward checkout completion, not just clicks.

Asynchronous by design – checkout never blocks

All server-side event transmissions are dispatched via WooCommerce Action Scheduler. The HTTP request to AxiTrace’s ingestion API happens in a background job, decoupled from the order placement flow. Checkout latency is unaffected even if the AxiTrace API is momentarily slow or unavailable.

Platform coverage

One plugin. One workspace key. AxiTrace routes your events to whichever ad platforms you connect in your dashboard:

• Facebook / Meta – Conversions API (CAPI)

• TikTok – Events API (server-side)

• Google Ads – Offline Conversion Upload (GCLID-based attribution)

• Google Analytics 4 – Measurement Protocol

HPOS and Cart/Checkout Blocks compatible

AxiTrace for WooCommerce declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and the modern Cart/Checkout Blocks, so it works correctly on stores that have migrated away from legacy shortcode-based checkout.

WP Consent API support

Consent is governed by your AxiTrace workspace settings, so you flip one switch in AxiTrace and every storefront page follows it – no code, no per-plugin configuration. With that switch on, the SDK writes no cookie, no storage entry and sends no request until the visitor agrees to marketing.

On top of that, the plugin detects the WP Consent API (implemented by Complianz, CookieYes and other consent managers). When one is present, the plugin gates tracking on the marketing category as well: the SDK script loads but stays inert until the visitor allows that category, and a withdrawal made later stops it and deletes the identifiers it wrote.

The decision is read in the visitor’s own browser, so full-page caches cannot leak one visitor’s choice to the next, and a later grant starts tracking without a reload. The decision recorded at checkout travels with the purchase, so your AxiTrace workspace can also decide server-side whether a purchase may be forwarded to the ad platforms. This gives your store a ready compliance path without requiring you to build custom integration.

GDPR personal-data tools built in

AxiTrace registers a WordPress personal-data exporter and eraser ( wp_privacy_personal_data_exporters / wp_privacy_personal_data_erasers ), enabling your store to fulfill GDPR deletion requests directly from the WordPress Tools > Erase Personal Data screen.

Privacy first

com and are SHA-256 hashed inside AxiTrace before being forwarded to any ad platform. No raw PII leaves the AxiTrace platform. com/privacy/ and the == External Services == section below for the complete disclosure.

Free plugin. Paid plans for volume.

The plugin itself is free and open source (GPL v2 or later). com is required. Free workspaces are available.

com for current pricing.

com/.

External Services

com – the AxiTrace event-ingestion API.

• Service: AxiTrace conversion tracking SaaS.

• Endpoint: https://stat.axitrace.com/woocommerce/pixel (POST).

• When data is sent: on page views (cart, product, checkout, thank-you), add-to-cart events, begin-checkout events, payment-method selection at checkout, and order placement / payment completion.

• Data transmitted: order ID, plain-text billing email (hashed downstream by AxiTrace), billing phone, billing city/country/zip, order total + currency, line items (SKU, name, quantity, price), user agent, IP address, AxiTrace session/user identifiers, ad click ids from the page URL or the first-party cookies the AxiTrace tracking script stores them in (gclid, gbraid, wbraid, ttclid, rdt_cid, oppref, msclkid, twclid, epik, li_fat_id, sccid; only the bare id is sent, and a stored id older than its click window – 90 days for Google, TikTok, Microsoft and X, 60 for Pinterest, 30 for LinkedIn, 28 for Reddit, OpenAI Ads and Snapchat – is not sent), or, for Microsoft, X, Pinterest and LinkedIn, from the cookie the platform’s own tag sets (_uetmsclkid, _twclid, _epik, li_fat_id; read only, never changed), ad-platform browser cookies (fbc, fbp, ttp, rdt_uuid, obref, Google Analytics client and session), UTM parameters, page URL/referrer/title.

• Why: to forward the conversion to Facebook CAPI, TikTok Events API, Google Ads, GA4, and other ad platforms configured in your AxiTrace workspace.

• Terms of Service: https://axitrace.com/terms/

• Privacy Policy: https://axitrace.com/privacy/

Optional profit tracking (secret key)

Only when you enter an AxiTrace secret key in the settings (in AxiTrace under Settings, in the Container Information card, as Secret Key):

• Server-side purchases to /woocommerce/pixel additionally carry each line item’s unit cost from the WooCommerce Cost of Goods Sold field, and the request is authenticated with the secret key (HTTP Basic). The cost is never sent from the shopper’s browser.

• Refunds and cancellations of paid orders are sent to https://stat.axitrace.com/v1/refund (POST): order ID, refund ID and date, refunded amount and currency, and the refunded line items (SKU, catalog ID, quantity, amount). No customer personal data is included.

Optional first-party tracking domain

You may optionally configure a custom first-party subdomain under WooCommerce → Settings → Integrations → AxiTrace → “First-party tracking domain”. g. com.

The data transmitted, the endpoint path ( /woocommerce/pixel ), and the recipient (AxiTrace) remain identical – only the hostname changes. This is purely a delivery optimization that helps bypass client-side blocking; no third-party service is added.

com endpoint described above.

Auto-detect lookup endpoint

com ) to look up the default verified domain registered for that workspace. The request contains only the merchant’s own workspace public key (already exposed in every browser event); no customer or visitor data is sent.