Thijs Joosten Digital Acquisition

S2S Conversions sends purchase and lead events directly from your server to Google Analytics 4 via the Measurement Protocol — bypassing ad blockers, browser restrictions, and cookie limitations.
Unlike client-side tracking via Google Tag Manager, server-side events are never blocked and always arrive — even when a visitor uses an ad blocker, Safari ITP, or closes the browser before the thank-you page loads.
<h4>Key Features</h4>
<ul>
<li>GA4 purchase tracking — sends complete purchase data including items, revenue, tax and shipping</li>
<li>GA4 lead tracking — tracks form submissions as generate_lead events</li>
<li>Session ID tracking — correctly attributes conversions to the right channel (Google Ads, Meta, Organic) instead of Unassigned/Direct</li>
<li>Form integrations — supports Contact Form 7, WPForms, Gravity Forms, and Elementor Pro Forms</li>
<li>10 cookie consent tools — works with Cookiebot, Complianz, OneTrust, Real Cookie Banner, Borlabs, iubenda, Moove GDPR, CookieScript, WP Cookie Notice, and a custom banner</li>
<li>Adblocker-proof — events are sent server-side, never blocked</li>
<li>GDPR-ready — GA4 events contain no personally identifiable information; consent is respected before sending any data</li>
<li>Debug log viewer — built-in log viewer in the settings page for easy troubleshooting</li>
<li>WooCommerce HPOS compatible — fully supports High Performance Order Storage</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>When a customer completes a checkout, the plugin captures the GA4 session data (client_id, session_id) before the payment redirect</li>
<li>After payment, the plugin sends the purchase event server-side via the GA4 Measurement Protocol</li>
<li>Because the session data was captured before the redirect, the conversion is correctly attributed to the original traffic source</li>
</ol>
<h4>Upgrade to TJDA Pulse</h4>
The free version tracks GA4 only. Upgrade to TJDA Pulse at <a href="https://pulse.tj-da.com" rel="nofollow ugc">pulse.tj-da.com</a> for:
<ul>
<li>Google Ads — server-side click conversion upload + enhanced conversions</li>
<li>Meta CAPI — Facebook/Instagram Conversions API with email and phone hashing</li>
<li>LinkedIn CAPI — LinkedIn Conversions API</li>
<li>Data Manager API — dual-write to Google’s Data Manager API</li>
<li>Lead conversion slots — map specific forms to specific Google Ads conversion actions</li>
<li>License management — secure per-domain licensing</li>
</ul>
<h4>Supported Consent Tools</h4>
<ul>
<li>Cookiebot</li>
<li>Complianz</li>
<li>OneTrust</li>
<li>Real Cookie Banner v3</li>
<li>Borlabs Cookie</li>
<li>iubenda</li>
<li>Moove GDPR</li>
<li>CookieScript</li>
<li>WP Cookie Notice</li>
<li>Custom banner (cookieConsent cookie)</li>
</ul>
<h4>External Services</h4>
This plugin sends data to the following external services:
<ul>
<li>Google Analytics (analytics.google.com) — to send purchase and lead events via the Measurement Protocol. <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
<li>s2s-plugin.tj-da.com — to verify DPA (Data Processing Agreement) acceptance. No personal data is sent; only a domain verification request is made. <a href="https://s2s-plugin.tj-da.com/privacy.php" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h3>Additional Information</h3>
S2S Conversions was built out of frustration with the growing gap between what web analytics reports and what actually happens. Ad blockers, iOS tracking prevention, and payment redirects cause a significant portion of conversions to go unrecorded — meaning marketers make decisions based on incomplete data.
The solution is straightforward: send conversion events from the server instead of the browser. The server always fires. It doesn’t get blocked. It doesn’t lose session data during a payment redirect. And because it captures the GA4 session ID before any redirect happens, conversions are attributed to the right channel — Google Ads, Meta, Organic — instead of showing up as Unassigned or Direct.
This free version focuses entirely on GA4 and handles the most common scenarios: WooCommerce purchases and form submissions. It works alongside your existing Google Tag Manager setup, not instead of it.
If you need server-side tracking for Google Ads, Meta CAPI or LinkedIn CAPI, TJDA Pulse at <a href="https://pulse.tj-da.com" rel="nofollow ugc">pulse.tj-da.com</a> covers those platforms with the same approach.
Built by <a href="https://tj-da.com" rel="nofollow ugc">Thijs Joosten Digital Acquisition</a> — a digital marketing specialist focused on measurement, attribution and conversion optimisation.

S2S Conversions

Server-side GA4 tracking via the Measurement Protocol. Adblocker-proof, GDPR-ready, and free forever.

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.

S2S Conversions vs AxiTrace for WooCommerce