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.

Crelora

<a href="https://onelence.com" rel="nofollow ugc">OneLence</a> is a marketing decision layer that helps teams understand which channels, campaigns, creators, affiliates, and customer journeys actually contribute to growth—so decisions are based on evidence, not guesswork.
OneLence Connect is the official WordPress integration for the OneLence platform. It sends reliable server-side attribution and conversion data from your WordPress site into your OneLence workspace, including WooCommerce activity, with less data loss from ad blockers and browser restrictions.
Once connected, your WordPress data becomes part of the broader OneLence decision workflow: attribution, channel evaluation, conversion analysis, reinvestment decisions, and growth prioritization.
This plugin is focused on reliable data collection and delivery for OneLence. Reporting, decision workflows, and strategic insights happen inside your OneLence workspace.
What you get
<ul>
<li>More reliable attribution with server-side tracking and reduced data loss</li>
<li>WooCommerce conversion tracking with automatic retry handling when delivery fails</li>
<li>Consent-aware tracking compatible with popular CMPs and OneLence Consent</li>
<li>Hybrid tracking mode that combines server reliability with browser SDK capabilities without duplicate page views</li>
<li>No-code event setup using the Events tab with visual selectors and rule builders</li>
<li>Diagnostics and validation tools in wp-admin, including Test Connection before launch</li>
<li>Reliable inputs for OneLence decisions about channels, campaigns, creators, affiliates, and growth priorities</li>
</ul>
What you need
<ul>
<li>A <a href="https://onelence.com" rel="nofollow ugc">OneLence account</a> (<a href="https://onelence.com/pricing" rel="nofollow ugc">free trial available</a>)</li>
<li>Use Connect to OneLence in the plugin dashboard—your site is linked and credentials are configured automatically</li>
</ul>
Works on any WordPress site, including WooCommerce stores, SaaS sites, landing pages, content-driven brands, and lead-generation websites.
WooCommerce support is optional but fully supported for order and conversion tracking.
Learn more
<ul>
<li><a href="https://onelence.com" rel="nofollow ugc">OneLence — marketing decision layer</a></li>
<li><a href="https://onelence.com/docs/integrations/start-integration/website-builder-setup/wordpress" rel="nofollow ugc">WordPress setup guide</a></li>
<li><a href="https://onelence.com/docs/integrations/start-integration" rel="nofollow ugc">Integrations overview</a></li>
</ul>
<h3>External services</h3>
This plugin connects to external services. Data is only sent when tracking is enabled and your consent settings allow it.
<h4>OneLence ingestion API</h4>
Used to deliver server-side attribution events and WooCommerce conversions to your OneLence workspace.
<ul>
<li>What is sent: page URLs, visitor identifiers (<code>olm_vid</code>), UTM and attribution parameters, event names and configured properties, WooCommerce order metadata when store tracking is enabled, and optional user email on login for identify events.</li>
<li>When: on page views, configured events, conversions, and related server-side actions according to your tracking mode and consent mode.</li>
<li>Where: <code>https://ingest.onelence.com</code></li>
<li>Provider: Crelora / OneLence — <a href="https://onelence.com/terms-of-service" rel="nofollow ugc">Terms of Service</a>, <a href="https://onelence.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Mark browser SDK (Hybrid / JS-only modes)</h4>
Used for client-side tracking when Hybrid or JS-only tracking modes are enabled.
<ul>
<li>What is sent: analytics and attribution data configured in the plugin, including page views and custom events, subject to your CMP and consent settings.</li>
<li>When: after consent is granted (or immediately when no CMP is detected and your consent mode allows it).</li>
<li>Where: the Mark SDK bundled inside this plugin (<code>assets/js/mark.browser.umd.js</code>). No third-party script host is used on WordPress.org builds.</li>
<li>Provider: Crelora / OneLence — <a href="https://onelence.com/terms-of-service" rel="nofollow ugc">Terms of Service</a>, <a href="https://onelence.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Connect to OneLence (setup)</h4>
Used when an administrator clicks Connect to OneLence in wp-admin to link the WordPress site to a OneLence workspace.
<ul>
<li>What is sent: OAuth/session tokens and site metadata required to obtain API credentials.</li>
<li>When: during the administrator-initiated connect flow.</li>
<li>Where: OneLence web properties under <code>onelence.com</code></li>
<li>Provider: Crelora / OneLence — <a href="https://onelence.com/terms-of-service" rel="nofollow ugc">Terms of Service</a>, <a href="https://onelence.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>OneLence Consent (optional separate plugin)</h4>
Not required. If installed, OneLence Connect reads consent signals from that plugin and may forward optional coverage metrics when forwarding is enabled in settings.
<ul>
<li>What is sent: consent state required for tracking decisions and optional lightweight coverage metrics when forwarding is enabled.</li>
<li>When: while visitors interact with the consent banner and when forwarding is enabled.</li>
<li>Where: local WordPress installation (OneLence Consent plugin). Download: <a href="https://onelence.com/consent/download" rel="nofollow ugc">onelence.com/consent/download</a></li>
<li>Provider: Crelora / OneLence — <a href="https://onelence.com/terms-of-service" rel="nofollow ugc">Terms of Service</a>, <a href="https://onelence.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h3>Privacy</h3>
<ul>
<li>Cookies: <code>olm_vid</code> (visitor identity) and <code>olm_utm</code> (attribution parameters). These are set according to your consent mode and detected CMP.</li>
<li>Consent: OneLence Connect reads consent signals from your CMP; it does not replace your cookie banner. Optional OneLence Consent is available as a separate plugin.</li>
<li>WordPress tools: Personal data export is registered with WordPress privacy tools. Use Keep Data on Uninstall in Tracking settings if you want plugin options retained after uninstall.</li>
<li>Policy: <a href="https://onelence.com/privacy-policy" rel="nofollow ugc">OneLence privacy policy</a></li>
</ul>
<h3>For developers</h3>
OneLence Connect exposes WordPress hooks for custom integrations, including:
<ul>
<li><code>onelco_should_track</code></li>
<li><code>onelco_event_payload</code></li>
<li><code>onelco_conversion_payload</code></li>
<li><code>onelco_visitor_id</code></li>
<li><code>onelco_event_sent</code></li>
<li><code>onelco_conversion_sent</code></li>
<li><code>onelco_load_mark_sdk</code></li>
</ul>
Custom conversions can use:
<ul>
<li><code>ONELCO_Tracker::track_custom_conversion()</code></li>
<li><code>onelco_track_custom_conversion</code> action</li>
</ul>
Full integration reference:
<a href="https://onelence.com/docs/integrations/start-integration/website-builder-setup/wordpress" rel="nofollow ugc">WordPress setup docs</a>

OneLence Connect for WordPress

Connect WordPress to OneLence for reliable attribution, cleaner marketing signals, and clearer decisions about what deserves more investment.

Trackity for WooCommerce vs OneLence Connect for WordPress