axitrace

AxiTrace for WooCommerce connects your store to the AxiTrace server-side tracking platform at <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a>. 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 <code>woocommerce_add_to_cart</code> 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:
<ul>
<li>Facebook / Meta — Conversions API (CAPI)</li>
<li>TikTok — Events API (server-side)</li>
<li>Google Ads — Offline Conversion Upload (GCLID-based attribution)</li>
<li>Google Analytics 4 — Measurement Protocol</li>
</ul>
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 <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a> 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 <code>statistics</code> and <code>marketing</code> 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 (<code>wp_privacy_personal_data_exporters</code> / <code>wp_privacy_personal_data_erasers</code>), 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 <code>stat.axitrace.com</code> 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 <a href="https://axitrace.com/privacy/" rel="nofollow ugc">axitrace.com/privacy/</a> and the <code>== External Services ==</code> 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 <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> is required. Free workspaces are available. Paid plans unlock higher event volumes, longer data retention, and priority support — see <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> for current pricing.
Requires an AxiTrace account at <a href="https://axitrace.com/" rel="nofollow ugc">https://axitrace.com/</a>.
<h3>External Services</h3>
This plugin connects to stat.axitrace.com — the AxiTrace event-ingestion API.
<ul>
<li>Service: AxiTrace conversion tracking SaaS.</li>
<li>Endpoint: <code>https://stat.axitrace.com/woocommerce/pixel</code> (POST).</li>
<li>When data is sent: on page views (cart, product, checkout, thank-you), add-to-cart events, begin-checkout events, and order placement / payment completion.</li>
<li>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.</li>
<li>Why: to forward the conversion to Facebook CAPI, TikTok Events API, Google Ads, GA4, and other ad platforms configured in your AxiTrace workspace.</li>
<li>Terms of Service: https://axitrace.com/terms/</li>
<li>Privacy Policy: https://axitrace.com/privacy/</li>
</ul>
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. <code>metrics.your-store.com</code> (which you set up in your AxiTrace workspace and verify via CNAME to <code>stat.axitrace.com</code>), the SDK and ingestion endpoint load from your own domain instead of stat.axitrace.com. The data transmitted, the endpoint path (<code>/woocommerce/pixel</code>), 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 <code>stat.axitrace.com</code> 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 <code>https://axitrace.com/api/public/workspace/tracking-domain?key={public_key}</code> (AxiTrace admin host — separate from the ingestion host <code>stat.axitrace.com</code>) 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.

AxiTrace for WooCommerce

Server-side conversion tracking for WooCommerce — Facebook CAPI, TikTok Events API, Google Ads, and GA4 from one plugin.

trackcombo

lucaswhiather

Track Combo — Conversions API for WooCommerce turns your store into a unified tracking source. One plugin, one tag, and every relevant event reaches Meta (Facebook/Instagram), Google Ads, TikTok, Pinterest, Kwai and any destination you configure in your Track Combo workspace — both from the browser and from the server via the WooCommerce Webhook.
Instead of juggling multiple pixels, conflicting event IDs, and broken deduplication after the iOS 14 / browser tracking updates, Track Combo captures the event once on the storefront, enriches it with first-party data on the server, and fans it out to all destinations with proper event_id deduplication between client and server.
<h3>What the plugin does</h3>
<ul>
<li>Injects the Track Combo web tag in the storefront <code><head></code>.</li>
<li>Exposes <code>window.tcWoo</code> with structured product, cart, order, and customer data so events do not depend on DOM scraping.</li>
<li>Registers a native <code>WC_Webhook</code> that sends <code>order.updated</code> to the Track Combo backend when the order reaches the purchase status you choose.</li>
<li>Deduplicates <code>purchase</code> between the client-side <code>complement_data</code> event and the server-side webhook using the order ID as <code>transaction_id</code>.</li>
<li>Declares compatibility with High-Performance Order Storage (HPOS) and works with both classic shortcode and Checkout Blocks checkouts.</li>
</ul>
<h3>Events sent</h3>
<ul>
<li><code>page_view</code>, <code>search</code>, <code>view_item_list</code>, <code>view_item</code></li>
<li><code>add_to_cart</code>, <code>initiate_checkout</code>, <code>add_shipping_info</code>, <code>add_payment_info</code></li>
<li><code>complement_data</code> (client-side on thank-you page, merged server-side)</li>
<li><code>purchase</code> (server-side via webhook — reliable even when the browser tab is closed)</li>
</ul>
<h3>Why Conversions API</h3>
Tracking quality on WooCommerce stores dropped sharply after iOS 14.5 and the phase-out of third-party cookies. Conversions API (CAPI) is Meta’s, Google’s and TikTok’s answer: send events directly from your server. Track Combo wraps all of them behind one integration.
<h3>Why Track Combo instead of multiple plugins</h3>
<ul>
<li>One plugin instead of one per ad network.</li>
<li>One dedupe boundary handled by Track Combo — no <code>event_id</code> mismatches.</li>
<li>No tag-manager containers to maintain.</li>
<li>Full visibility of every event in the Track Combo dashboard.</li>
</ul>
You need a Track Combo account to use this plugin. Sign up at <a href="https://trackcombo.com/" rel="nofollow ugc">trackcombo.com</a>.
<h3>External services</h3>
This plugin relies on Track Combo (https://trackcombo.com), the service operated by the plugin author, to deliver first-party event tracking and server-side conversion delivery to advertising platforms (Meta Conversions API, Google Ads, TikTok and others). It connects to the following Track Combo endpoints:
<ul>
<li>
Configuration API — <code>https://server.trackcombo.com/integrationwoocommerce</code>. Called only when the store owner saves the plugin settings in WordPress admin (validate the API key, persist the purchase status filter, register the store domain). Data sent: the API key (HTTP header), and the purchase status or store domain string when those are updated. No customer data is sent through this endpoint.
</li>
<li>
Web tag — <code>https://track.track-combo.com/tag/{container_id}.js</code> (or your configured first-party CNAME, e.g. <code>https://tracks.yourstore.com/...</code>). Loaded on every storefront page view to enable client-side event tracking. The tag itself dispatches tracking events from the browser to the Track Combo events endpoint.
</li>
<li>
Order webhook — a WooCommerce webhook registered by the plugin that POSTs the WooCommerce order payload to a URL on <code>server.trackcombo.com</code> whenever an order reaches the purchase status you configure in the plugin settings (default: “Processing”). This enables reliable server-side <code>purchase</code> events even when the customer closes the browser tab.
</li>
</ul>
Track Combo terms of use: https://trackcombo.com/termos-de-uso/ 
Track Combo privacy policy: https://trackcombo.com/politica-de-privacidade/

Track Combo — Conversions API for WooCommerce

Send WooCommerce events (view, add-to-cart, purchase) to Meta CAPI, Google Ads, and TikTok through Track Combo — no extra pixels needed.

AxiTrace for WooCommerce vs Track Combo — Conversions API for WooCommerce