WordPress

The PixelFox WordPress plugin installs the tag on every page and, with WooCommerce active, tracks the whole funnel - with the purchase sent server-side so it survives ad blockers. It runs in two modes: offline (anonymous, nothing leaves your server, an API key is the whole setup) and online (the full product with identity, segments and the dashboard).

Install

Download the plugin zip from your PixelFox dashboard.
Plugins → Add New → Upload Plugin, upload the zip, activate PixelFox.
Open Settings → PixelFox and paste your API key - the only required setting - then pick the mode and your business category.

Settings

Setting	What it does
Mode	Offline - anonymous only or Online - full dashboard. See below
API key	Your site's key. Required
Site ID	Needed for courier fraud checks and feedback. Found in your dashboard URL
Business category	Shows the recommended conversion events for your kind of store
WooCommerce events	Track product views, add-to-cart, checkout and purchases (on by default)
Courier fraud check	Show a COD risk score on the order screen
COD restriction	Withdraw cash on delivery below a delivery success rate you choose (default 60%). Fails open: if the lookup is unavailable, COD stays enabled
Custom loader	Load vendor tags (GTM, GA4, Meta, TikTok) through your first-party tracking domain, so blocklists matching the vendors' domains do not fire
Advanced → Ingest host	Where the tag sends events and where it is loaded from. Leave blank for `api.pixelfox.app`; set it to your custom ingest endpoint, e.g. `https://t.yourstore.com`, to serve everything from your own domain
Advanced → Dashboard API host, Script URL	Leave blank unless you self-host

Re-check connection at the bottom of the page tests the key against the host.

Offline and online

	Offline	Online
The tag	A tiny local collector; no external script	The PixelFox tag from the ingest host
Where events go	A table in your own database only. No page view or conversion is transmitted	Your database and PixelFox
Identity	Not collected	Logged-in shoppers identified, cross-device stitching, segments
Dashboard reporting	The plugin's own sales summary	The full dashboard
Courier fraud checks	Work in both modes - they are queries against the shared fraud dataset by nature, and can be turned off

Switch modes at any time; nothing already recorded is lost.

WooCommerce events

With WooCommerce active you get, with no extra configuration:

product_viewed on product pages; view_cart on the cart page; search with the query on search results.
add_to_cart - on form posts and on AJAX adds (the event rides back with the cart fragments, so themes like Astra, Flatsome and Kadence work without a page reload); remove_from_cart.
checkout_started when the checkout form renders (CartFlows steps that are not the checkout are skipped).
complete_registration on a new account's first page.
purchase - sent server-side from woocommerce_thankyou and from the processing/completed status transitions (a closed tab still counts), with the order id, total, currency, line items, the billing profile (online mode), the shopper's IP and user agent, and the click ids, _fbp/_fbc/_ttp/Reddit/UET cookies, GA client id and PixelFox device id snapshotted on the order at checkout. Once per order.

Logged-in shoppers are identified to the tag once per session (online mode), so the anonymous browsing before login, the account, and every device they use join one person - see identity and devices.

Attribution

The plugin keeps first-touch (90 days) and last-touch (7 days) cookies with the UTM parameters, the click ids (gclid, fbclid, msclkid, ttclid, li_fat_id, ScCid, rdt_cid, twclid, wbraid, gbraid) and the landing URL, and stamps them on the order at checkout.

Also in the plugin

COD protection: withdraw cash on delivery below a risk threshold, add an advance payment fee, and block checkout for listed phones or IPs. See COD protection.
Fraud meta box on the order screen with the cross-courier history, and feedback.
Delivery outcomes reported from order status changes into the shared fraud dataset.
Deleting the plugin removes its options, blocklists and local events table.

The plugin's folder, main file (pixelfox.php), settings option and text domain are named pixelfox. A store that installed the plugin while it was still called "Signals" keeps its settings: the first load after updating copies them across, and nothing needs re-entering.