AxiTrace for WooCommerce

AxiTrace for WooCommerce connects your store to the AxiTrace server-side tracking platform at axitrace.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 Customer email addresses and phone numbers are transmitted in plain text to AxiTrace's ingestion API at stat.axitrace.com and are SHA-256 hashed inside AxiTrace before being forwarded to any ad platform. No raw PII leaves the AxiTrace platform. See our Privacy Policy at axitrace.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). An AxiTrace account at axitrace.com is required. Free workspaces are available. Paid plans unlock higher event volumes, longer data retention, and priority support - see axitrace.com for current pricing. Requires an AxiTrace account at https://axitrace.com/.

1.4.0

• Change: consent is now governed by your AxiTrace workspace settings. The tracking SDK is loaded on every page and asks AxiTrace whether it may run, so turning "Respect cookie consent" on in your workspace gates every storefront page - including stores with no consent plugin at all - without touching any code.
• Change: with the WP Consent API present the SDK is still gated on the marketing category, but it is now the SDK itself that stays inert (no cookie, no storage, no request) instead of the script not being loaded. The site gate and the workspace policy apply together, so a page can only tighten the workspace setting, never loosen it.
• Add: a consent withdrawal reported by wp_listen_for_consent_change now stops tracking immediately and deletes the identifiers AxiTrace wrote, instead of taking effect only on the next page view.

1.3.0

• Fix: the browser-side purchase on the thank-you page never fired on stores with pretty permalinks (the default), so the Meta Pixel bridge never engaged for purchases. It now reads the order from the order-received query var.
• Fix: the browser-side purchase now carries the full order (line items, phone, name, billing address, order number, tax, shipping). AxiTrace keeps whichever of the two purchase events arrives first; a thin browser event would have left the ad platforms without buyer data.
• Fix: the browser-side purchase fires only for orders WooCommerce considers paid. On-hold bank transfers and pending gateway returns are reported by the server-side event once the payment lands.
• Fix: server-side AddToCart now carries the shopper's AxiTrace visitor and session ids, real IP and User-Agent, ad-platform cookies, value and line item instead of the shop server's identity.
• Fix: the SDK now loads on every storefront page. Homepage, landing pages and blog posts were skipped, so ad clicks landing there were never attributed.
• Fix: WP Consent API support actually works now, is cache-safe (the decision is made in the browser), gates on the marketing category, and a later grant boots the SDK without a reload.
• Fix: transient delivery failures (AxiTrace unreachable, timeout, 5xx) are retried with backoff for up to 24 hours instead of being lost after the first attempt.
• Add: purchases carry the human-readable order number (GA4 transaction_id), gross tax, shipping and discount amounts, a catalog id per line item, and the shopper's consent decision.

1.2.1

• Fix: the links in this listing and on the settings screen pointed at pages that do not exist. "Visit plugin site" led to axitrace.com/woocommerce and the install instructions sent you to axitrace.com/admin; both answered with an error page. They now point at the WooCommerce integration page and the sign-in page. No tracking behaviour changes - upgrading is optional.

1.2.0

• Add: purchase events now include the shopper's first name, last name and state/province from the billing address. Facebook Conversions API and TikTok Events API hash and match on these, so including them measurably improves event match quality.
• Add: the TikTok browser ID (_ttp) and Reddit browser and click IDs (_rdt_uuid, _rdt_cid) are captured at checkout and forwarded, so TikTok and Reddit receive an identifier of their own instead of matching on e-mail alone.
• Add: the Google Analytics client and session cookies are captured at checkout, so the server-side purchase reaches GA4 as the shopper's own session instead of an unattributed new user.
• Add: the AxiTrace visitor and session IDs are captured and sent as the external ID, stitching the server-side purchase to the shopper's browsing profile. The WooCommerce customer ID could not serve this purpose: it is a WordPress user ID and is empty for guest checkouts.

1.1.0

• Fix: InitiateCheckout (begin_checkout) now reports the real cart total and currency instead of value=0. Also deduplicated to fire once per checkout session instead of on every reload.
• Add: AddPaymentInfo now fires when a shopper selects a payment method on the checkout page (classic/shortcode checkout), giving ad platforms a mid-funnel signal between InitiateCheckout and Purchase.
• Fix: AddToCart no longer double-fires. It was previously tracked independently from both the server and the browser with no shared ID, recording every add-to-cart twice. The server-side hook (which covers every add-to-cart path, including ad-blocked and JS-disabled browsers) is now the sole source; the redundant browser-side listener was removed.

1.0.2

• Improvement: purchase events now include the customer's own Meta browser pixel cookies (_fbp/_fbc) when present, captured at checkout time and forwarded to Facebook Conversions API for better browser/server event matching. No change for stores without their own Meta Pixel.

1.0.1

• Fix: settings saved through WooCommerce > Settings > Integrations > AxiTrace are now read correctly at runtime. The public key, server-side events toggle, and tracking domain entered in the form are picked up immediately. Previously these values were not detected, so no events were sent. Re-saving the settings is not required after upgrading.

1.0.0

• Initial release.
• Server-side purchase event via Action Scheduler.
• Deterministic UUID v5 dedup for Facebook CAPI, TikTok, Google Ads, GA4.
• Server-side AddToCart event for ad-blocked customers.
• HPOS and Cart/Checkout Blocks compatibility.
• WP Consent API detect-and-check support.
• GDPR personal-data exporter and eraser hooks.