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.

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.

S2S Conversions vs Datablow Event Tracker for Meta Conversions API