trackity

Trackity for WooCommerce is the official WordPress client for the Trackity SaaS analytics service (https://trackity.com). The plugin is non-functional on its own — it requires an active Trackity account and API key. Once a merchant connects the store, the plugin sends order, checkout, product, customer, attribution, click identifier, browser, and runtime error data to Trackity for analytics, attribution, and ad-platform conversion tracking.
Tracking is inactive until the merchant connects the plugin. Disconnecting the plugin removes local Trackity credentials and stops the storefront script and event delivery.
<h3>External services</h3>
This plugin connects to the Trackity API, a third-party SaaS service operated by Trackity. Connection to this service is required for the plugin to function — without it the plugin performs no tracking and sends no data.
Service: Trackity Analytics 
Provider: Trackity (https://trackity.com) 
API endpoint: https://api.trackity.com 
Privacy Policy: https://www.trackity.com/privacy-policy/ 
Terms & Conditions: https://www.trackity.com/terms-and-conditions/
What is sent to Trackity, when, and why:
<ol>
<li>During connection: the store URL, the merchant-supplied Trackity API key, and a CSRF state token are sent to <code>https://api.trackity.com/api/woocommerce/oauth/authorize</code> and <code>/api/woocommerce/oauth/exchange</code>. This is required to authenticate the store against the merchant’s Trackity account.</li>
<li>When a WooCommerce order, customer, or product event fires: the relevant order/customer/product payload (including billing/shipping address, email, line items, totals, and tracking attribution captured on the storefront) is sent to <code>https://api.trackity.com/api/woocommerce/webhooks</code>. This is required for analytics and ad-platform conversion reporting.</li>
<li>On every storefront page load while connected: a JavaScript file is requested from <code>https://api.trackity.com/pixel/global-script</code>. That script initialises the ad-network pixels (Meta, Google Ads, TikTok, Microsoft Bing, LinkedIn, Snapchat, Reddit, Pinterest) that the merchant has connected inside the Trackity dashboard. The set of pixels is merchant-specific and changes whenever the merchant connects or disconnects an ad platform in Trackity, which is why it cannot be bundled statically with the plugin. The script is loaded asynchronously and is only injected after the merchant has explicitly connected the plugin.</li>
<li>On storefront pixel events (page view, product view, add to cart, begin checkout, payment info, purchase, runtime errors): the corresponding event payload is sent to the matching <code>/pixel-events/*</code> endpoint at <code>https://api.trackity.com</code>.</li>
</ol>
The Trackity service is governed by Trackity’s Privacy Policy and Terms & Conditions, linked above. Site owners using this plugin are responsible for disclosing the use of Trackity (and any ad-platform pixels they enable through it) in their own site privacy policy and for obtaining any visitor consent required by their local data-protection law (GDPR, CCPA, etc.). The plugin registers WordPress personal-data exporter and eraser callbacks so order tracking data can be exported or erased through Tools → Export Personal Data and Tools → Erase Personal Data.

Trackity for WooCommerce

Trackity analytics and conversion tracking integration for WooCommerce stores.

Hugo Carvalho

Attribution usually breaks somewhere between the ad click and the conversion. ClickTrail makes it survive: cached pages, dynamic forms, multi-page journeys, repeat visits, and consent requirements.
ClickTrail keeps the source of the visit, not a profile of the visitor. Capture is first-party and consent-aware: the plugin does not call external services to identify or enrich visitors, and data only leaves your site through integrations you enable yourself (GTM, webhooks, server-side delivery).
ClickTrail stores first-touch and last-touch attribution from the landing page and keeps it available until the conversion point, where it becomes usable inside WordPress:
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
In WooCommerce, ClickTrail stores attribution on the order, pushes enriched purchase events on the thank-you page, and can optionally emit GA4-style storefront events for <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code>, plus post-purchase milestones, through the same ClickTrail pipeline.
<h4>Pick a starting path</h4>
<ul>
<li>WooCommerce store: enable Capture and WooCommerce. Orders carry campaign context from day one; add storefront events later if you want funnel signals.</li>
<li>Lead-gen forms: enable Capture and Forms. Contact Form 7 and Fluent Forms get hidden fields automatically; Gravity Forms and WPForms fill the <code>ct_*</code> fields you add.</li>
<li>GTM / sGTM stack: enable Capture, Events, and Delivery. Browser events push to the <code>dataLayer</code>, and the server-side adapters feed sGTM or platform APIs directly.</li>
</ul>
<h4>What problems it solves</h4>
<ul>
<li>No paid order reports as “direct”: Paid traffic often ends up looking like direct traffic by the time an order is placed. ClickTrail stores attribution on the order and keeps purchase reporting tied to campaign context.</li>
<li>No checkout journey goes dark: WooCommerce storefront journeys can emit opt-in <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code> signals through the same ClickTrail event layer used elsewhere in the plugin.</li>
<li>No cached or AJAX-rendered form drops attribution: Hidden fields often break on cached pages or dynamically rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li>No cross-domain hop breaks continuity: Approved link decoration and attribution tokens keep continuity between domains or subdomains.</li>
<li>No consent signal is ignored: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin and respect the same consent state.</li>
</ul>
<h4>Core capabilities</h4>
<ul>
<li>Capture: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.</li>
<li>WooCommerce: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.</li>
<li>Forms: automatic hidden-field enrichment for Contact Form 7 and Fluent Forms, compatible hidden-field population for Gravity Forms and WPForms, client-side fallback, dynamic form support, and WhatsApp attribution continuity.</li>
<li>Events: browser event collection with <code>dataLayer</code> pushes, canonical REST intake, webhook ingestion, lifecycle updates, one-time WordPress follow-up events such as <code>login</code>, <code>sign_up</code>, and <code>comment_submit</code>, and optional WooCommerce storefront events.</li>
<li>Delivery: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.</li>
</ul>
<h4>Recent additions</h4>
Recent releases extended the Gravity Forms integration with channel classification, merge tags, and per-form controls:
<ul>
<li>Channel classification: every GF entry now receives a <code>ct_ft_channel</code> value — a human-readable label such as Google Ads, ChatGPT, or Mailchimp — derived from click IDs, UTM parameters, or referrer context. A server-side fallback covers sessions where JS attribution was unavailable.</li>
<li>Expanded click ID capture: six additional click IDs (Reddit <code>rdt_cid</code>, Pinterest <code>pin_cid</code>, Snapchat <code>snap_cid</code>, Mailchimp <code>mc_cid</code> / <code>mc_eid</code>, and Display & Video 360 <code>dclid</code>) are now captured and stored.</li>
<li>Merge tags: nine <code>{clicutcl_*}</code> merge tags are available in GF notifications and confirmations, including <code>{clicutcl_channel}</code>, <code>{clicutcl_click_id}</code>, and seven UTM-based tags.</li>
<li>Per-form toggle: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.</li>
<li>Admin QA mode: attribution data is stored in <code>sessionStorage</code> only when a <code>manage_options</code> user is logged in, preventing admin browsing from appearing in attribution reports.</li>
<li>sessionStorage fallback: attribution capture now falls back to <code>sessionStorage</code> when the browser blocks cookies.</li>
<li>Minification protection: ClickTrail script tags carry exclusion attributes recognised by Autoptimize, Cloudflare Rocket Loader, WP Rocket, and LiteSpeed Cache (corrected attribute set in 1.7.0).</li>
</ul>
<h4>Current admin structure</h4>
The main settings experience is organized by capability:
<ul>
<li>Capture</li>
<li>Forms</li>
<li>Events</li>
<li>Delivery</li>
</ul>
Operational screens stay separate:
<ul>
<li>Logs</li>
<li>Diagnostics</li>
</ul>
<h4>Supported integrations</h4>
<ul>
<li>Forms: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms</li>
<li>Commerce: WooCommerce</li>
<li>CMP sources: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom</li>
<li>Webhook providers: Calendly, HubSpot, Typeform</li>
<li>Server-side adapters: Generic collector, sGTM, Meta CAPI, Google Ads / GA4, LinkedIn CAPI, Pinterest Conversions API, TikTok Events API</li>
</ul>
<h4>Forms behavior by plugin</h4>
<ul>
<li>Contact Form 7 and Fluent Forms: ClickTrail can add hidden attribution fields automatically.</li>
<li>Gravity Forms and WPForms: ClickTrail can populate matching hidden fields you add to the form.</li>
<li>Recommended for Gravity Forms and WPForms: add the hidden fields you want stored or exported, and ClickTrail will fill them.</li>
<li>Elementor Forms (Pro): ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.</li>
<li>Ninja Forms: ClickTrail stores attribution with the submission and surfaces it in the submission record, not as automatic hidden-field injection.</li>
</ul>
<h4>Supported click IDs</h4>
<ul>
<li>Google: <code>gclid</code>, <code>wbraid</code>, <code>gbraid</code></li>
<li>Meta: <code>fbclid</code></li>
<li>TikTok: <code>ttclid</code></li>
<li>Microsoft: <code>msclkid</code></li>
<li>X / Twitter: <code>twclid</code></li>
<li>LinkedIn: <code>li_fat_id</code></li>
<li>Snapchat: <code>sccid</code></li>
<li>Pinterest: <code>epik</code></li>
</ul>
<h4>Additional capture fields</h4>
<ul>
<li>Extended UTMs: <code>utm_id</code>, <code>utm_source_platform</code>, <code>utm_creative_format</code>, <code>utm_marketing_tactic</code></li>
<li>Browser/platform identifiers: <code>fbc</code>, <code>fbp</code>, <code>_ttp</code>, <code>li_gc</code>, <code>ga_client_id</code>, <code>ga_session_id</code></li>
</ul>

ClickTrail – UTM, Click ID & Ad Tracking (with Consent)

Consent-aware attribution for WooCommerce, WordPress forms, and event flows. Capture UTMs and click IDs across conversion paths.

Trackity for WooCommerce vs ClickTrail – UTM, Click ID & Ad Tracking (with Consent)