Product Performance Score for WooCommerce
Product Performance Score for WooCommerce helps a store owner see which products are performing better inside the current store and which products deserve review.
The score uses one fixed formula at every stage:
- 20% unique product views.
- 30% carts after a product detail view in the same session.
- 50% paid order performance.
Every product has its own tracking start date and moves through four data stages:
- Initial stage: 1 to 6 complete days. A score can appear after at least one valid view, with a clear limited-data warning.
- Building stage: 7 to 13 complete days, requiring at least 10 valid views.
- Stabilizing stage: 14 to 20 complete days, requiring at least 20 valid views.
- Standard stage: 21 or more complete days, using the latest 21 complete days and requiring at least 30 valid views.
The publication day is not a complete day. Before the first complete day finishes, the product shows a waiting status rather than a score.
Early, building, stabilizing, and standard scores all use the same PPS formula. Only the amount of observed data and the comparison window change. A new product published long after plugin installation still starts from its own initial stage.
All H, I, and S ranks use the same full, same-window candidate set. Products with zero carts after view receive I = 0, and products with zero paid orders receive S = 0. The plugin does not create separate non-zero ranking pools.
Only current standard-stage scores enter the store average. The store average is a simple arithmetic mean and does not remove the highest or lowest products.
The plugin supports WooCommerce simple products and variable parent products. Variation views, carts, and orders are attributed to the parent product.
The Score column includes a WordPress help icon. Hover the score or focus it with the keyboard to see the product’s saved scoring details without recalculating data.
Privacy
The plugin uses one short-lived first-party cookie, eezz_pps_sid, to deduplicate product views and carts inside an anonymous session. The database stores only an HMAC-SHA256 hash of that cookie value.
Product view requests also include a stable HMAC token tied to the product ID. This reduces blind or cross-site pollution of the public analytics endpoint, but it is not intended to stop an attacker who can fetch and replay a public product page.
The plugin does not store IP addresses, full user agents, names, emails, phone numbers, full browsing paths, or order IDs in its custom tables. It does not send data to third-party services.