WooCommerce Product Views Ecommerce is a lightweight extension that logs which registered users have opened a product page and what they did next — viewed, added to cart, or completed checkout. It is aimed at store owners who want per-customer browsing history inside the WordPress dashboard rather than aggregated analytics charts, and at a $10 one-off price it sits at the impulse-buy end of the WooCommerce extension market. The plugin is published on ThemeForest by the developer Codeden, and it is currently at version 1.0.
What WooCommerce Product Views Ecommerce Actually Records
The core of the plugin is a log. Every time a logged-in user opens a product page, an entry is created that ties three pieces of information together: the user, the product, and the timestamp. That third element is the one most store owners underestimate. Knowing that a customer looked at a product is mildly interesting; knowing they looked at it three times over the course of a week and still did not buy is the kind of signal that changes how a follow-up email is written.
On top of the raw view record, the extension tracks progression through the purchase funnel. A row in the log can show that a user only viewed the item, that they added it to the cart, or that they went all the way through checkout and bought it. In practice this turns the log into a crude but readable funnel report per customer and per product, which is the main reason someone would install it rather than relying on a general analytics platform.
Per-user history rather than aggregate numbers
Most free analytics integrations in WordPress report totals: this product had 400 views last month, the store converted at 2.1 percent. WooCommerce Product Views works the other way around. It answers the question “what has this specific account been looking at”, which is useful when a wholesale customer emails asking about pricing, or when a returning buyer seems to be comparing two similar items. The data sits in the WordPress admin, so no external account, tracking script, or consent banner change is required to read it.
Purchase status attached to each view
Because the purchase outcome is stored alongside the view rather than in a separate report, the plugin can distinguish between a window shopper and a converted customer without any manual cross-referencing. That distinction is what makes the log actionable for segmentation: users who viewed but never bought form a natural list for a reminder campaign, and users who viewed and bought confirm which product pages are doing their job.
Installation and scope
The vendor describes installation as quick and straightforward, which matches the shape of the product — there is no configuration wizard, no external service to connect, and no additional database schema beyond the logging table. The stated compatibility is WooCommerce 2.1.9. That figure is worth pausing on. It is an old WooCommerce release, and the vendor does not state whether the plugin has been tested against current WooCommerce or WordPress versions. Anyone running a modern store should treat compatibility as something to verify before purchase rather than assume.
Where WooCommerce Product Views Ecommerce Fits, and Where It Does Not
The clearest fit is a small B2B or wholesale operation where the number of customer accounts is manageable and each one matters individually. If a store has forty trade accounts and the owner wants to know which of them keep returning to a discontinued line, or which have been circling a bulk-pricing page without ordering, a per-user view log is directly useful. The same applies to high-touch retail niches — furniture, machinery, specialist equipment — where a single sale justifies a personal follow-up and the browsing history informs that conversation.
It also suits agencies and freelancers who maintain client stores and want a cheap diagnostic tool in the toolkit. At $10, adding it to a staging site to inspect customer behaviour during a conversion-rate investigation is a low-risk decision, and the data can be exported or read directly if a deeper analysis is needed.
It is the wrong choice for a high-traffic consumer store. A shop processing thousands of orders a month will generate a view log so large that reading it row by row is pointless, and the plugin offers no aggregation, charting, cohort analysis, or automated reporting to compensate. Those stores are better served by a full analytics platform or a dedicated behavioural tracking tool. It is also a poor fit for stores that rely on guest checkout, because the tracking is tied to user accounts — an anonymous visitor leaves no trace in the log at all. Finally, anyone running a current WooCommerce build should confirm compatibility first, since the vendor only names version 2.1.9.
Strengths and Limitations of This WooCommerce Product Views Ecommerce Plugin
Strengths
- Very low price point. At $10 it costs less than most single-purpose WooCommerce add-ons and carries no subscription, so there is no recurring cost to justify.
- Customer-level granularity. The log answers per-account questions that aggregate analytics dashboards cannot, which is the plugin’s whole reason for existing.
- Funnel state included. Recording view, cart, and purchase status in the same record removes the need to reconcile two data sources.
- Timestamps make behaviour patterns visible. Repeat visits over time are often more informative than a single view count.
- No external dependency. Data stays in the WordPress database, so there is no third-party service to configure or pay for.
Limitations
- Stated compatibility stops at WooCommerce 2.1.9. The vendor gives no indication of testing against later WooCommerce or WordPress releases, which is the single biggest risk for a buyer today.
- Registered users only. Guest browsing is invisible, so stores with guest checkout enabled will see an incomplete picture.
- No reporting layer. There is no dashboard widget, chart, export button, or scheduled email summary described. The data is presented as a log to be read, not as analytics to be interpreted.
- No segmentation or automation. The plugin identifies users who viewed but did not buy, but it does not act on that list — no abandoned-view emails, no tagging, no integration with marketing tools.
- Version 1.0 with a single changelog entry. There is no track record of maintenance, security patches, or feature iteration to assess.
- Sales figures are not disclosed. There is no public adoption data to use as a signal of reliability.
How It Compares With Other Customer Tracking Options
The alternatives fall into three groups, and the plugin’s position depends on which one a store is weighing it against.
General analytics platforms — whether a hosted service or a self-hosted WordPress analytics plugin — report in aggregate. They are stronger at trend analysis, traffic sources, and conversion rates across the whole store, and they handle anonymous visitors. They are weaker at answering “what did account number 214 do last Tuesday”. A store that needs both will usually run an analytics platform as the primary tool and treat a plugin like this as a supplementary lookup.
Marketing automation and CRM extensions sit at the other extreme. They track behaviour and then act on it, triggering emails, applying tags, and scoring leads. They cost considerably more and require configuration, but they close the loop that WooCommerce Product Views leaves open. For a store whose real goal is recovering abandoned browsers automatically, a marketing tool is the better purchase.
Direct database queries or custom code occupy the middle ground. A developer can build a similar view log with a few hooks and a custom table, and would gain full control over reporting and retention. The $10 price is effectively buying the time saved on that work, which is a reasonable trade for a non-developer but a marginal one for an agency with the skills in house.
Against all three, the plugin’s distinctive claim is simplicity and price. It does one narrow thing, stores the result locally, and costs almost nothing. Buyers should judge it on that basis rather than expecting it to substitute for an analytics or automation stack.
Frequently Asked Questions
Does WooCommerce Product Views track visitors who are not logged in?
No. The plugin records views against user accounts, so only registered and logged-in customers appear in the log. Anonymous visitors and guest checkouts leave no entry. Stores that allow guest purchasing will therefore see an incomplete record of product interest, and should not treat the log as a full picture of store traffic.
Is WooCommerce Product Views compatible with the current version of WooCommerce?
The vendor only states compatibility with WooCommerce 2.1.9, which is a significantly older release. No information is provided about testing against later versions of WooCommerce or WordPress. Buyers on a modern store should verify compatibility on a staging environment before relying on the plugin in production, since the listing offers no assurance either way.
Can the plugin send follow-up emails to customers who viewed but did not buy?
No. It identifies those customers in the log but provides no automation, email sending, or integration with marketing platforms. Acting on the list requires a separate tool or manual outreach. The plugin’s role stops at recording and displaying the behaviour, which is a meaningful limitation for stores hoping to recover abandoned product views automatically.
What information does each log entry contain?
Each entry ties a user to a product and includes the date and time of the view. It also records the outcome — whether the customer only viewed the item, added it to the cart, or completed a purchase. That combination is what allows a store owner to read the log as a simple per-customer funnel.
Verdict on WooCommerce Product Views Ecommerce
This plugin is worth buying for a specific kind of store: a small or mid-sized operation with registered accounts, a high-value product, and a genuine need to know what individual customers have been looking at. Wholesale and B2B shops, specialist retailers, and agencies doing conversion diagnostics on client sites all get real value from a $10 one-off tool that keeps its data local and requires almost no setup.
It should be avoided by high-traffic consumer stores that need aggregate reporting, by any store relying on guest checkout, and by anyone who wants behavioural data to trigger automated marketing — the plugin records but does not act. The unresolved question of compatibility with current WooCommerce versions is the deciding factor for many buyers, and the vendor’s silence on it is a legitimate reason to test before committing.
Weighed honestly, this is a narrow utility rather than a growth platform. It does one job cleanly and cheaply, and it is priced accordingly.
