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 \u2014 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.<\/p>\n\n
Tracking is inactive until the merchant connects the plugin. Disconnecting the plugin removes local Trackity credentials and stops the storefront script and event delivery.<\/p>\n\n
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 \u2014 without it the plugin performs no tracking and sends no data.<\/p>\n\n
Service:<\/strong> Trackity Analytics\nProvider:<\/strong> Trackity (https:\/\/trackity.com)\nAPI endpoint:<\/strong> https:\/\/api.trackity.com\nPrivacy Policy:<\/strong> https:\/\/www.trackity.com\/privacy-policy\/\nTerms & Conditions:<\/strong> https:\/\/www.trackity.com\/terms-and-conditions\/<\/p>\n\n What is sent to Trackity, when, and why:<\/strong><\/p>\n\n 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 \u2192 Export Personal Data and Tools \u2192 Erase Personal Data.<\/p>\n\n\n No. Tracking starts after a store administrator connects the plugin with a Trackity API key.<\/p><\/dd>\n Yes. Use the Disconnect button on the Trackity admin page.<\/p><\/dd>\n\n<\/dl>\n\n\n Initial release.<\/p>","raw_excerpt":"Trackity analytics and conversion tracking integration for WooCommerce stores.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/311127","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=311127"}],"author":[{"embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/trackity"}],"wp:attachment":[{"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=311127"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=311127"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=311127"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=311127"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=311127"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/test.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=311127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
https:\/\/api.trackity.com\/api\/woocommerce\/oauth\/authorize<\/code> and \/api\/woocommerce\/oauth\/exchange<\/code>. This is required to authenticate the store against the merchant's Trackity account.<\/li>\nhttps:\/\/api.trackity.com\/api\/woocommerce\/webhooks<\/code>. This is required for analytics and ad-platform conversion reporting.<\/li>\nhttps:\/\/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>\n\/pixel-events\/*<\/code> endpoint at https:\/\/api.trackity.com<\/code>.<\/li>\n<\/ol>\n\n\n
\/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does tracking start immediately after activation?<\/h3><\/dt>\n
Can I disconnect the plugin?<\/h3><\/dt>\n
1.0.7<\/h4>\n\n
\n
trk_<random><\/code> which is incompatible with Shopify pixel UUID format).<\/li>\n_fallback_<timestamp><\/code> when fewer than 3 browser signals are available, matching Shopify pixel behaviour.<\/li>\n_trackity_{param}<\/code>, _trackity_{param}_expiry<\/code>, _trackity_{param}_creation<\/code>) now written alongside the v2 blob so server-side code reading individual keys finds them.<\/li>\n1.0.6<\/h4>\n\n
\n
cartId<\/code> and lineItemCount<\/code> now included in add_to_cart payloads, matching Shopify pixel behaviour.<\/li>\ngiftCards<\/code> field added to checkout and purchase payloads (always empty array \u2014 WooCommerce has no native gift card mechanism).<\/li>\n<\/ul>\n\n1.0.5<\/h4>\n\n
\n
kx_email<\/code>, _kx<\/code>) are now captured and stored in the tracking blob.<\/li>\n<\/ul>\n\n1.0.4<\/h4>\n\n
\n
1.0.0<\/h4>\n\n