Plugin Conflicts

Customer History is a read-only admin plugin that uses standard WordPress and WooCommerce APIs, so conflicts are uncommon. When one does happen, here’s how to find and resolve it.

How to isolate a conflict

• Temporarily deactivate your other plugins (keep WooCommerce and Customer History active).
• Reproduce the issue. If it’s gone, reactivate the others one at a time, re-testing after each, until the culprit reappears.
• To rule out the theme, switch to a default theme (e.g. Twenty Twenty-Four) and re-test.

It’s server-side, so JavaScript rarely matters

Activity is recorded in PHP, not by a front-end tracking script, so the usual “exclude the tracking script from minification” advice doesn’t apply — there’s no such script on normal storefront pages. The only front-end script the plugin adds is a tiny billing-email capture on the checkout page (part of Pro’s abandoned-cart feature). If a page builder or optimizer breaks the admin screens, that’s the area to look at, not storefront tracking.

Caching plugins & object cache

• Full-page caching can cause anonymous page views to be undercounted (the recording step runs in PHP). See Tracking Not Working.
• Object caching is fine — but because the reports are cached for performance, a figure can briefly lag until its cache refreshes. It’s compatible with WP Rocket, W3 Total Cache, and similar.

Security plugins

Aggressive security or firewall plugins occasionally block admin-ajax.php or REST requests that the admin screens use to load data. If reports won’t load or actions fail in wp-admin, allow Customer History’s admin requests in your security plugin. Common ones to check: Wordfence, Sucuri, iThemes Security.

Database tables

Customer History stores its data in its own tables — for example wp_pd_woo_customer_history_sessions and tables prefixed wp_pdwchs_ (your site’s table prefix replaces wp_). Collisions are very unlikely, but if you suspect another plugin uses the same names, contact support.

Reporting a conflict

If you find a genuine conflict, let us know with the conflicting plugin’s name and version, the steps to reproduce, and your WordPress/WooCommerce/PHP versions.