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.

modovisa

A tiny settings page where you paste your Tracking token and enable tracking. The plugin then loads the lightweight Modovisa tracker on the front-end only.
<ul>
<li>Loads once per page in <code><head></code> (optional <code>defer</code>).</li>
<li>Does not load in <code>wp-admin</code>.</li>
<li>Uses WordPress script APIs (<code>wp_register_script</code>/<code>wp_enqueue_script</code>) and standard attributes.</li>
<li>Plays nicely with common performance plugins (Autoptimize, WP Rocket).</li>
</ul>
<h3>How-to video</h3>
Watch a short walkthrough of the setup:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/olSW5JawjzE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h3>External services</h3>
This plugin connects your WordPress site to the Modovisa Analytics service to track visitor journeys in real time on your WordPress site including page views and related events.
Domains and what they do 
– <code>https://cdn.modovisa.com/modovisa.min.js</code> — JavaScript file served from the Modovisa CDN. The plugin loads this script on the front-end when tracking is enabled. 
– <code>https://modovisa.com</code> (and subdomains) — Modovisa’s application/API endpoints that receive analytics events generated by the script.
What data is sent and when 
– On front-end page loads, the Modovisa script sends an event payload to Modovisa that typically includes: 
 – Page URL/path, referrer (if available), user agent, and basic device/viewport info. 
 – A Tracking identifier (your Tracking token) so data is associated with the correct Modovisa Tracking token. 
 – Pseudonymous visit/session identifiers (e.g., first-party cookies or similar storage) to recognize returning visits. 
– The plugin does not track or load the script in <code>wp-admin</code>. It does not send WordPress user emails, passwords, or other WP user PII.
Consent and performance notes 
– If you use a consent tool, configure it so the Modovisa script loads only after consent. 
– The script tag includes compatibility attributes for common performance plugins (e.g., <code>data-noptimize</code>, <code>data-nowprocket</code>, <code>data-cfasync</code>) to prevent aggregation or deferral from breaking analytics. These attributes do not transmit any data by themselves.
Provider and policies 
– Service: Modovisa Analytics 
– Terms of Service: https://modovisa.com/legal/terms-and-conditions 
– Privacy Policy: https://modovisa.com/legal/privacy
<h3>Privacy</h3>
This plugin connects your site to Modovisa Analytics to measure visits and conversions. On front-end page loads, the Modovisa script (from <code>https://cdn.modovisa.com/modovisa.min.js</code>) sends event data to Modovisa for processing and reporting. The payload typically includes page URL, referrer (if available), user agent, and pseudonymous visit/session identifiers. The plugin does not send WordPress admin data or WP user PII.
Use of this plugin requires an active Modovisa account and Tracking token, which you enter on the plugin settings page. By enabling tracking, you consent to the transmission of analytics data to Modovisa as described in their policies: 
– Terms: https://modovisa.com/legal/terms-and-conditions 
– Privacy: https://modovisa.com/legal/privacy

Modovisa Analytics

Injects the Modovisa real-time tracking script into your site’s .

FirstTrack — Server-Side Ad Tracking vs Modovisa Analytics