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.

datablow

Datablow Event Tracker connects your WordPress site directly to Meta using the Conversions API (CAPI). It sends events from both the browser and the server side with matching deduplication keys, so your ad campaigns receive complete and accurate conversion data.
Traditional browser-only tracking loses 20–30% of event data due to ad-blockers, iOS privacy protections, and Safari Intelligent Tracking Prevention (ITP). This plugin addresses those challenges by acting as a local proxy on your own domain and writing cookies server-side.
<h4>Core Features</h4>
<ul>
<li>PageView Tracking — Fires PageView events from both the browser pixel and the server side.</li>
<li>Deduplication Engine — Generates matching <code>event_id</code> values for browser and server events so Meta merges them automatically.</li>
<li>Audit Logger — Stores the last 50 Conversions API payloads and HTTP response codes in your admin dashboard.</li>
<li>Test Simulator — Manually trigger test CAPI payloads from WordPress to verify your configuration.</li>
<li>Ad-Blocker Script Proxy — Serves the Meta Pixel JavaScript from your own domain endpoint, preventing ad-blockers from blocking the tracker.</li>
<li>Cookie Keeper — Writes <code>_fbp</code> and <code>_fbc</code> cookies from PHP (server side), extending their lifespan up to 2 years and bypassing Safari ITP limits.</li>
<li>User Registration — Sends <code>CompleteRegistration</code> events when new users register on your site.</li>
<li>URL-to-Event Mapping — Fire any standard Meta event on specific URL paths without writing code.</li>
</ul>
<h3>External Services</h3>
This plugin connects to Meta (Facebook) external services to track web events and transmit conversion data. Specifically:
<ol>
<li>
Meta Pixel JavaScript (connect.facebook.net)
<ul>
<li>The plugin loads the Meta Pixel JavaScript library from <code>https://connect.facebook.net/en_US/fbevents.js</code> in the visitor’s browser to enable browser-side event tracking.</li>
<li>When the Ad-Blocker Script Proxy feature is enabled, this script is fetched server-side and cached locally, then served from your own domain to the visitor’s browser.</li>
<li>What data is sent: No user data is sent to this URL directly; it is a JavaScript file load only.</li>
<li>When: On every front-end page load when a Pixel ID is configured.</li>
</ul>
</li>
<li>
Meta Pixel Noscript Fallback (www.facebook.com/tr)
<ul>
<li>The plugin outputs a 1×1 pixel <code><img></code> tag inside a <code><noscript></code> block requesting <code>https://www.facebook.com/tr</code>.</li>
<li>What data is sent: Pixel ID and a PageView event signal for visitors who have JavaScript disabled.</li>
<li>When: On every front-end page load when a Pixel ID is configured and JavaScript is disabled.</li>
</ul>
</li>
<li>
Meta Graph API / Conversions API (graph.facebook.com)
<ul>
<li>The plugin sends server-side event data to <code>https://graph.facebook.com/v19.0/{pixel_id}/events</code>.</li>
<li>What data is sent: Event name, event time, deduplication event ID, action source, hashed user data (SHA-256 hashed email, phone, name, city, state, zip, country), client IP address, user agent, and Facebook browser/click cookies (<code>_fbp</code>, <code>_fbc</code>). For purchase events, value and currency are also included.</li>
<li>When: On PageView (every front-end page load), custom URL-mapped events, and user registrations — depending on which features are enabled in settings.</li>
<li>Authentication: An Access Token stored in WordPress options is appended to each request.</li>
</ul>
</li>
</ol>
These connections to Meta services are required for the plugin’s core conversion tracking functionality. The processing occurs on Meta’s external servers.
<ul>
<li>Service Provider: Meta Platforms, Inc.</li>
<li>Meta Terms of Service: https://www.facebook.com/legal/terms</li>
<li>Meta Privacy Policy: https://www.facebook.com/about/privacy</li>
<li>Meta Conversions API Terms: https://www.facebook.com/legal/developer_terms</li>
<li>Meta Platform Terms: https://developers.facebook.com/terms/</li>
</ul>
No data is transmitted until you configure a valid Meta Pixel ID and Conversions API Access Token in the plugin settings.

Datablow Event Tracker for Meta Conversions API

First-party Meta Conversions API and browser tracking plugin for WordPress. Bypasses ad-blockers and extends cookie lifetimes.

AxiTrace for WooCommerce vs Datablow Event Tracker for Meta Conversions API