Trackity for WooCommerce

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.

External services

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

com)

com

com/privacy-policy/

com/terms-and-conditions/

What is sent to Trackity, when, and why:

• During connection: the store URL, the merchant-supplied Trackity API key, and a CSRF state token are sent to https://api.trackity.com/api/woocommerce/oauth/authorize and /api/woocommerce/oauth/exchange. This is required to authenticate the store against the merchant’s Trackity account.

• 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 https://api.trackity.com/api/woocommerce/webhooks. This is required for analytics and ad-platform conversion reporting.

• On every storefront page load while connected: a JavaScript file is requested from https://api.trackity.com/pixel/global-script. 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.

• 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 /pixel-events/* endpoint at https://api.trackity.com.

• When a store administrator runs WordPress’s built-in Tools → Erase Personal Data or Tools → Export Personal Data for a shopper: that shopper’s email address (and phone number, for an erasure request) is sent to https://api.trackity.com/api/woocommerce/redact or /api/woocommerce/data-request respectively, so Trackity can apply the same request to its own copy of that shopper’s tracking data, not just the local WordPress copy.

The Trackity service is governed by Trackity’s Privacy Policy and Terms & Conditions, linked above. ). 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 — both now also notify the Trackity backend (item 5 above), not just the local WordPress copy.