cgzirim

Markopolo AI is a lightweight tracking plugin that captures key WordPress site events and sends them to the Markopolo AI analytics platform for reporting and attribution.
<h4>Key Features</h4>
<ul>
<li>Page and interaction tracking: captures <code>page_view</code>, <code>click</code>, <code>form_interaction</code>, and <code>Search</code> events.</li>
<li>Form data capture: can capture name, email, and phone values when they are present in forms.</li>
<li>Session tracking: uses a UUID-based session identifier to group user activity.</li>
<li>First-party identifier: manages a <code>muid</code> cookie for visitor identification.</li>
<li>Marketing attribution data: can include common attribution cookies such as Facebook Pixel, TikTok, Google Analytics, and Microsoft UET cookies when present.</li>
<li>Simple configuration: add your Tag ID from a WordPress admin settings page.</li>
<li>Lightweight front-end script: loads only when a valid Tag ID and endpoint are configured.</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to Settings > Markopolo AIr.</li>
<li>Enable Enable Tracking in plugin settings.</li>
<li>Enter your Tag ID.</li>
<li>Save settings.</li>
<li>The plugin loads its front-end script and sends tracked events to the Markopolo endpoint.</li>
</ol>
Tracking is off by default. The plugin does not load front-end tracking until Enable Tracking is enabled by an admin and a valid Tag ID is provided.
<h3>External Services</h3>
This plugin relies on Markopolo AI services to provide analytics and attribution functionality.
<h4>Service A: Event ingestion endpoint</h4>
<ul>
<li>What it is used for: Receiving browser-side analytics events for reporting and attribution.</li>
<li>Endpoint: <code>https://mtag.markopolo.ai/mark</code></li>
<li>When data is sent: On tracked front-end events (for example page views, clicks, form interactions, and search events) only after admin opt-in via Enable Tracking, with a valid Tag ID and endpoint configured.</li>
<li>Data sent may include: tag ID, page URL/path/title, referrer, language, timezone, viewport/screen data, session and visitor identifiers, attribution cookies when available, click metadata, and form-related values such as name/email/phone/search terms when detected.</li>
</ul>
<h4>Service B: Settings webhook endpoint</h4>
<ul>
<li>What it is used for: Notifying Markopolo when plugin settings lifecycle events occur.</li>
<li>Endpoint: <code>https://api-alpha.markopolo.ai/v1/integrations/wordpress/webhook</code></li>
<li>When data is sent:
<ul>
<li>Only after an admin has enabled Enable Tracking.</li>
<li>When Tag ID is set for the first time.</li>
<li>When Tag ID is updated.</li>
<li>When Tag ID is removed.</li>
<li>During plugin uninstall, only when tracking is enabled and a Tag ID is configured.</li>
</ul>
</li>
<li>Data sent: event name, tag ID, previous tag ID (when applicable), plugin name, site URL, and event timestamp.</li>
</ul>
<h4>Service terms and privacy</h4>
<ul>
<li>Terms and legal information: https://markopolo.ai/legal</li>
<li>Privacy policy: https://markopolo.ai/legal</li>
</ul>
<h4>Event Types Tracked</h4>
<ul>
<li>page_view: fired on page load.</li>
<li>click: fired when users interact with common clickable elements.</li>
<li>form_interaction: fired on form change and submit events.</li>
<li>Search: fired when a search term is detected from a search form or search URL.</li>
</ul>
<h4>Data Collected</h4>
Depending on the page and user interaction, the plugin may collect and send:
<ul>
<li>Page URL, path, title, referrer, language, timezone, viewport, and screen size</li>
<li>Session ID and visitor identifier (<code>muid</code>)</li>
<li>Marketing attribution cookies when available</li>
<li>Form values such as name, email, phone, and search terms</li>
<li>Click metadata such as element text, ID, class, and coordinates</li>
</ul>
<h4>Privacy & Consent</h4>
This plugin tracks customer behavior including: 
* Page views, clicks, searches, and form interactions 
* Email addresses and phone numbers from form interactions 
* Marketing cookies (Facebook Pixel, TikTok, Google Analytics) 
* Session data and user identifiers
All data is sent to the Markopolo AI platform for analytics purposes. Ensure your privacy policy covers this data collection and complies with applicable privacy regulations (GDPR, CCPA, etc.).
Important: Site owners are responsible for obtaining any user consent required under applicable laws and regulations before enabling or using tracking features.
Plugin-level enablement requires admin opt-in. If Enable Tracking is disabled, front-end tracking and settings webhooks are disabled. Front-end tracking also requires a valid Tag ID.
<h4>Developer Notes</h4>
<ul>
<li>The plugin uses a WordPress admin settings page for configuration.</li>
<li>Settings are sanitized before being saved.</li>
<li>Events are sent asynchronously from the front end.</li>
<li>The plugin includes an uninstall routine that removes its saved settings.</li>
</ul>
<h3>Support</h3>
For support, contact the Markopolo team through your account or via email support@markopolo.ai.

Markopolo AI

Track WordPress events and send them to the Markopolo AI analytics platform.

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.

Markopolo AI vs FirstTrack — Server-Side Ad Tracking