- 2026-05-20
- by LethaldiranMX
- Trends
- 0 Comments
DeveloperServer-side conversion tracking for WooCommerce — Facebook CAPI, TikTok Events API, Google Ads, and GA4 from one plugin.
AxiTrace for WooCommerce connects your store to the AxiTrace server-side tracking platform at axitrace.com. Every purchase, add-to-cart, and begin-checkout event is captured on the server 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.
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
The plugin detects the WP Consent API and checks the visitor’s consent level before firing events. When no consent framework is present, the plugin fires freely (opt-out model). When a framework is present, the plugin respects the consent status for the statistics and marketing categories. 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/.
External Services
This plugin connects to stat.axitrace.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, 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, click-attribution cookies (fbc, fbp, gclid, ttclid, msclkid, twclid, epik, li_fat_id, sccid, rdt_cid), 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 first-party tracking domain
You may optionally configure a custom first-party subdomain under WooCommerce Settings Integrations AxiTrace “First-party tracking domain”. When set to e.g. metrics.your-store.com (which you set up in your AxiTrace workspace and verify via CNAME to stat.axitrace.com), the SDK and ingestion endpoint load from your own domain instead of stat.axitrace.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.
When this field is empty, the plugin uses the default stat.axitrace.com endpoint described above.
Auto-detect lookup endpoint
When the merchant clicks the “Detect from AxiTrace” button on the settings page, the plugin makes a single server-to-server GET request to https://axitrace.com/api/public/workspace/tracking-domain?key={public_key} (AxiTrace admin host — separate from the ingestion host stat.axitrace.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.
