Install Admaxxer on WordPress

Troubleshooting

The plugin shows "Activated" but no events arrive.

Three common causes. (1) Website ID is empty or wrong — re-check that it starts with admx_. (2) A caching plugin (WP Rocket, W3 Total Cache, LiteSpeed) is stripping the pixel — exclude admaxxer.com from minification and deferred-JS rules. (3) A security plugin (Wordfence, Sucuri) is blocking the outbound POST — whitelist admaxxer.com in your firewall.

Pixel works but WooCommerce orders never appear in Admaxxer.

The most common cause: the Webhook HMAC Secret field in Settings → Admaxxer is empty. Without it, the plugin silently skips the server-side order POST (this is intentional fail-closed behavior — the plugin will not send unsigned webhooks). Open Integrations → WooCommerce → Connect in the Admaxxer dashboard and copy the Signing secret from the “Final step: webhook setup” card. Paste it into the WP plugin and place a new test order — the previous unposted orders are not retroactively sent (we don't backfill). Second cause: a caching plugin is stripping the cookie that carries the visitor ID — exclude admx_visitor_id from your cache vary rules.

My PayPal/Stripe redirect order didn't track — does the plugin handle redirect drops?

Yes, since v1.1.0. The plugin subscribes to woocommerce_payment_complete in addition to woocommerce_thankyou, so orders that pay but never reach the thank-you page (browser closed, network drop, redirect blocked) are still captured server-side. Atomic local dedup via WC order meta prevents double-firing.

Where is the Webhook HMAC Secret in the Admaxxer dashboard?

Open Integrations → click WooCommerce → click Connect. The “Final step: webhook setup” card reveals the Signing secret. Each website has its own secret — if you run multiple stores, each one gets its own.

Cookieless mode for GDPR — do I still need a consent banner for the pixel?

When Enable Cookieless Tracking is on, the plugin loads /js/script.cookieless.js, which writes no persistent cookie — visitor IDs come from a salted fingerprint that rotates daily. This setup is generally recognized as exempt from EU/UK consent banner requirements for the pixel itself, but final compliance depends on your jurisdiction — review with your DPO. With the toggle off (default) a single first-party cookie _admx_visitor_id is set with a 1-year expiry; disclose it.

Is the plugin compatible with WooCommerce HPOS (High Performance Order Storage)?

Yes. The plugin declares HPOS compatibility via before_woocommerce_init and uses wc_get_order() rather than direct SQL — works on legacy posts-table and HPOS tables identically.

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.