WooCommerce runs on WordPress, so the install path is identical: use the Admaxxer WordPress plugin. The plugin detects WooCommerce and registers a woocommerce_thankyou hook so every completed checkout reports revenue back to Admaxxer.
Steps
1 Install the Admaxxer WordPress plugin
Download admaxxer-1.0.0.zip, upload via Plugins → Add New → Upload Plugin, and activate.
2 Configure your website ID
Open Settings → Admaxxer, paste your website ID, and save.
3 Confirm WooCommerce detection
The plugin settings screen shows "WooCommerce detected — revenue hooks enabled" when both plugins are active. No further config needed.
4 Verify the install
Load any public page on your site in a fresh browser tab. Within a few seconds, the Admaxxer dashboard realtime view should show the event. If nothing lands after 2 minutes, re-check the snippet is actually in the rendered HTML <head> (View Source, not just DevTools).
Verify installation
Place a test order through WooCommerce checkout.
Within 30 seconds the order should appear in Admaxxer under Attribution → Revenue with the source/medium of the visitor session.
Load any page on your domain in a normal browser tab.
In the Admaxxer dashboard, open Pixel → Realtime — a pageview should appear within ~5 seconds.
Troubleshooting
Pageviews arrive but orders do not.
Confirm the Admaxxer plugin is activated AFTER WooCommerce — WP load order matters for hook registration. Deactivate and reactivate the Admaxxer plugin if unsure.
No events are showing up. What now?
Open DevTools Console and Network. Filter for script.js and /api/event. If they are blocked:csp, your Content Security Policy is blocking admaxxer.com — see /documentation/troubleshoot/csp. Also double-check that data-website-id matches the ID shown in your dashboard.
Events show up in staging but not production.
Confirm data-domain matches the production hostname exactly (no protocol, no trailing slash). Also confirm the website's Allowed Domains list in settings includes the prod domain.
My site is a single-page app — am I missing pageviews?
Use script.hash.js if you rely on location.hash routing. Otherwise the default script.js already hooks history.pushState/replaceState and tracks SPA navigations.