tonigtn

FirstTrack is a bridge plugin that connects your WooCommerce store to the FirstTrack server-side tracking service at first-track.org. A free account at first-track.org is required.
Once installed and configured with your Shop ID, the plugin:
<ul>
<li>Loads a lightweight tracking script (wc.js) on your storefront that captures ad click identifiers (fbclid, ttclid, gclid, etc.) into first-party cookies.</li>
<li>Injects hidden tracking fields into the WooCommerce checkout form so the click data follows the customer into the order.</li>
<li>Saves the captured data into HPOS-safe order meta and (as a backup) into the order’s customer note. The FirstTrack backend then forwards purchase events to the configured ad platforms over their official server APIs.</li>
</ul>
Supported platforms (configured in your FirstTrack dashboard):
<ul>
<li>Meta Conversions API</li>
<li>TikTok Events API</li>
<li>Google Enhanced Conversions</li>
<li>Pinterest Conversions API</li>
<li>Snapchat Conversions API</li>
<li>X (Twitter) Conversions API</li>
</ul>
Features:
<ul>
<li>10-tier deterministic + probabilistic attribution with a confidence score per order</li>
<li>First-party tracking domain support (custom subdomain)</li>
<li>HPOS (WooCommerce High-Performance Order Storage) compatible</li>
<li>Cookie-consent aware (respects <code>_ft_consent</code> cookie and <code>window.__ft_consent</code>)</li>
<li>No bundled ad-platform SDKs in your storefront — all server-to-server</li>
</ul>
<h3>External services</h3>
This plugin relies on the FirstTrack service at first-track.org to deliver server-side ad conversion events. A free account at first-track.org is required for the plugin to function.
Service: FirstTrack (first-track.org)
What it is: a server-side ad conversion tracking service that forwards purchase events from your WooCommerce store to ad platforms (Meta, TikTok, Google, Pinterest, Snapchat, X / Twitter) using each platform’s official server-to-server Conversions API. The plugin is the bridge layer that runs on your store; the FirstTrack service runs at first-track.org and does the platform forwarding.
Script loaded on every storefront page:
On every front-end page, this plugin enqueues a JavaScript file from FirstTrack. The default URL is:
<ul>
<li><code>https://first-track.org/wc.js?shop=<your-shop-id></code></li>
</ul>
If the site administrator has configured a custom tracking domain (via the WordPress option <code>firsttrack_tracking_domain</code>, typically a CNAME subdomain like <code>track.yourstore.com</code> that resolves to FirstTrack’s infrastructure), the script is loaded from that custom host instead:
<ul>
<li><code>https://<your-custom-tracking-domain>/wc.js?shop=<your-shop-id></code></li>
</ul>
In both cases the destination server is FirstTrack’s infrastructure — the custom domain is a CNAME alias only. No data ever goes to a third party other than FirstTrack and (server-to-server, via the FirstTrack backend) the ad platforms that you have configured in your FirstTrack dashboard.
The script captures ad click identifiers into first-party cookies on the visitor’s browser and, on the WooCommerce checkout page, injects them as hidden form fields so the click data follows the order.
Data sent to first-track.org (or the configured custom tracking domain, which resolves to first-track.org):
<ul>
<li>When a visitor lands on your storefront from an ad: the click identifier in the URL (e.g. <code>fbclid</code>, <code>ttclid</code>, <code>gclid</code>, <code>epik</code>, <code>sccid</code>, <code>twclid</code>), the referring URL, the visitor’s user agent, and a randomly generated visitor UUID. These are stored as first-party cookies on the visitor’s browser and posted to the FirstTrack click endpoint at the configured tracking domain.</li>
<li>When a purchase is placed: the order’s tracking field values (<code>_ft_*</code> meta) plus hashed customer email/phone and the order total, currency, line item IDs, billing city/state/country/postcode. Personally-identifying fields are SHA-256 hashed before transmission per the requirements of the ad platforms’ server APIs.</li>
</ul>
Why: FirstTrack uses the click and purchase data to send conversion events to the ad platforms you have configured in your FirstTrack dashboard (Meta Conversions API, TikTok Events API, Google Enhanced Conversions, Pinterest Conversions API, Snapchat Conversions API, X Conversions API). This is required to attribute purchases back to ad campaigns when browser-based pixels are blocked.
Terms and privacy:
<ul>
<li>Terms of Service: <a href="https://first-track.org/terms" rel="nofollow ugc">https://first-track.org/terms</a></li>
<li>Privacy Policy: <a href="https://first-track.org/privacy" rel="nofollow ugc">https://first-track.org/privacy</a></li>
<li>Data Processing Addendum: <a href="https://first-track.org/dpa" rel="nofollow ugc">https://first-track.org/dpa</a></li>
</ul>

FirstTrack — Server-Side Ad Tracking

Server-side conversion tracking for WooCommerce. Sends checkout events to 6 ad platforms via official server APIs with 10-tier attribution.

Octanist

Octanist is a conversion tracking platform that bridges online marketing with offline sales. This plugin is the official connector for WordPress.
<h3>How it works</h3>
The plugin acts as a first-party proxy for the Octanist pixel:
<ul>
<li>Pixel proxy. The tracking script is served from your own WordPress site (<code>/wp-json/oct/p</code>) and transparently fetched from Octanist in the background. No third-party domain, no DNS setup, no ad-blocker signal to match on.</li>
<li>Event proxy. Events from the pixel POST to <code>/wp-json/oct/e</code>; the plugin forwards them to Octanist server-side, carrying along the real visitor IP, country, and user-agent.</li>
<li>Server-side form capture. Form submissions from Gravity Forms, Contact Form 7, WPForms, Ninja Forms, Elementor Pro, Fluent Forms, Formidable Forms, Forminator, SureForms, and Divi Contact Form are captured server-side via action hooks, more reliable than client-side interception, and works with AJAX submissions.</li>
</ul>
<h3>Setup</h3>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to Settings → Octanist.</li>
<li>Paste your measurement ID.</li>
<li>Done.</li>
</ol>
That’s it. No field mapping. No DNS configuration. Listener mode and consent mode are optional toggles.
<h3>Data privacy</h3>
<ul>
<li>Octanist account required. You need an active account at octanist.com.</li>
<li>You are the data controller. Consent capture and privacy-policy disclosure are your responsibility. A consent management platform (CMP) is recommended.</li>
</ul>

First-party proxy for the Octanist pixel. Serves the tracking script from your own domain and captures form submissions server-side.

FirstTrack — Server-Side Ad Tracking vs Octanist