An analytics plugin counts visits and shows you reports: which pages are read, where visitors come from, which countries and devices they use and how long they stay. In WordPress it can also place the dashboard inside your admin area, so you do not have to log in to another service.
Plugins differ most in where the data is collected and stored. Some count visits on your own server and keep the numbers in your own database. Others connect your site to an outside analytics service and display that service’s reports. That one distinction affects speed, privacy, cookie banners and what you keep if you leave.
WPMusk has not run hands-on tests of any plugin named here. This page is a buyer’s guide, and products appear as examples, not rankings.
A tracker records a page view. It can be a small JavaScript file that runs in the visitor’s browser and sends a request, or server-side code that logs the request as WordPress handles it. Koko Analytics’ listing says its collection endpoint bypasses WordPress. Independent Analytics’ listing says tracking sends a deferred request to your site’s REST API. Both approaches work with a page cache only if the tracker runs even when the page itself comes from the cache, so confirm this for any candidate.
Counting unique visitors needs some kind of identifier. Traditional analytics set a cookie. Cookie-free tools instead derive an identifier. Independent Analytics’ listing says it generates an ID from the IP address, which it does not store, and the user agent. WP Statistics’ listing says IP addresses are hashed with a random daily salt. These are the vendors’ own descriptions and not independent audits.
WP Statistics, Koko Analytics and Independent Analytics store data in your WordPress database, according to their listings. Matomo’s WordPress listing says all data is stored in your WordPress installation and recommends Matomo On-Premise or Cloud for high-traffic sites. Site Kit by Google’s listing says it connects your site to Google services such as Analytics, Search Console, Tag Manager and PageSpeed Insights, and shows insights in the WordPress dashboard. Its listing does not say where the underlying data is stored; for those services, the data is held by the connected service.
Local tools can store raw or aggregated data. Koko Analytics’ listing says it stores only aggregated counts, and offers cleanup of data older than a chosen age. Independent Analytics lists automatic deletion of old data. Aggregated counts keep the database small but limit what you can analyse later. Raw records answer more questions but take more space and carry more privacy responsibility.
You need some measurement if you make decisions from traffic: what to write, which pages to improve, whether a campaign worked. Even a small site benefits from knowing which pages are read.
You may not need a separate plugin if your host already provides basic statistics, or if the only numbers you ever look at are search impressions and clicks. Search Console covers that; see the Search Console guide.
Think about what you will do with the numbers. If you only need to know whether traffic rises or falls, a very light tool is enough. If you run paid campaigns, e-commerce funnels or A/B tests, you will need the event tracking, UTM handling and conversion reports that lighter tools may reserve for paid tiers or may not offer.
| Approach | Where data lives | Cookies and consent | Typical trade-off |
|---|---|---|---|
| Local counter, aggregated | Your database | Often cookie-free | Very light, but fewer reports |
| Local analytics with detailed reports | Your database | Often cookie-free by default | Richer reports, more database growth |
| Self-hosted analytics platform | Your server or a separate server | Configurable | Powerful, needs resources and upkeep |
| Hosted analytics service | Vendor’s servers | Depends on the service and configuration | No storage burden, but data leaves your site |
| Dashboard connector for external services | The connected service | Depends on the service | Convenient view, adds another account |
Our plugin scoring weights are speed impact 30%, reliability 25%, support 20%, value 15% and ease of use 10%.
Every page view triggers a tracker. Ask how large the script is, whether it loads from your own domain or an outside host and whether it writes to the database on each hit. Koko Analytics’ listing claims the tracker adds less than 1 KB to pages; treat that as a vendor claim until you check it. Matomo’s listing notes each page view adds a tracking request and recommends a larger PHP memory limit. Measure on staging, using the method in the evaluation plan below. See also the PageSpeed Insights guide.
Your numbers are only useful if you trust them. Ask how the tool treats bots, how it works with caching and whether it can exclude your own visits. WP Statistics’ listing mentions bot filtering, role-based exclusion and filters by IP. Treat all analytics as an estimate, and compare the numbers against server logs or a second tool for a week before relying on them.
Rules on consent differ by country and by what the tool collects. WP Statistics’ listing itself says consent needs depend on your country and settings and does not claim GDPR compliance on its own. Cookie-free is not the same as consent-free in every jurisdiction, so check local rules or ask a professional. Look for data export and deletion tools, IP anonymisation and a retention setting.
Can you export your data, and in what format? WP Statistics’ listing mentions export as XML, CSV or TSV, and Independent Analytics’ listing mentions CSV and PDF export. If you pick a hosted service, learn what you get if you cancel.
List the questions you ask: top pages, referrers, campaigns, countries, device types, search terms, outbound clicks, file downloads, form submissions, e-commerce revenue. Then check which tier answers them. Independent Analytics’ listing places campaign reports, click tracking and e-commerce analytics in its paid version. WP Statistics’ listing places campaign analytics and custom events in paid add-ons.
A good dashboard answers a question in one screen. Try the date picker, the filters and the page-level view. Check whether non-admin users, such as an editor or client, can see reports without access to settings. Independent Analytics’ listing mentions sharing report access with other users.
Read recent forum threads. Look at update frequency and whether security issues were handled fast. Vet the plugin with the plugin vetting checklist.
Many blockers block well-known analytics scripts, which undercounts traffic. WP Statistics’ listing mentions an option to rename the tracker script. Counting from the server avoids the problem but brings back the bot-filtering question.
These are examples, not rankings. The descriptions come from each product’s wordpress.org listing and should be checked against the current version.
WP Statistics. Its listing says data is created and stored in your own WordPress database, that it does not use cookies and that it hashes IP addresses with a random daily salt. It lists reports on visitors, content, referrals, geography and devices, and sells some features as paid add-ons. It fits sites that want detailed local reports.
Koko Analytics. Its listing says it stores aggregated counts only, does not require cookies, sends nothing to third parties and is GPL-licensed. It is built to be minimal. It fits sites that want simple traffic numbers with little overhead.
Matomo for WordPress. Its listing says all data is stored in your WordPress installation, mentions a GDPR manager, data export and deletion tools and retention settings, and points larger sites to Matomo On-Premise or Cloud via a separate plugin. It fits teams that want a full analytics platform with data ownership, and have the server resources to run it.
Independent Analytics. Its listing says it stores data in your WordPress database, does not communicate with external servers, does not use cookies and lists views, sessions, bounce rate and referrer reports in the free version. Campaign tracking, click tracking and e-commerce reports are in the paid version. It fits sites that want dashboards inside WordPress with a clear free tier.
Site Kit by Google. Its listing says it connects Search Console, Analytics, AdSense, PageSpeed Insights and Tag Manager, and shows insights in the WordPress dashboard. It is a connector rather than a separate tracker. It fits sites already using Google’s services that want the reports in the admin area.
| Question | Candidate A | Candidate B | Candidate C |
|---|---|---|---|
| Where is data stored? | |||
| Cookies set? Consent needed in your country? | |||
| Tracker size and where it loads from? | |||
| Works with your page cache and CDN? | |||
| Bot filtering and own-visit exclusion? | |||
| Reports you need: campaigns, events, e-commerce? | |||
| Which of those are in the paid tier? | |||
| Export formats and retention controls? | |||
| Ad-blocker handling? |
The lock-in with analytics is your history. Switching tracking tool is easy; carrying years of data across is not, because tools store data in different shapes. Aggregated counts from one tool rarely import neatly into another.
A practical approach is to export key monthly totals before leaving and keep them in a spreadsheet. Expect a visible break in the trend lines at the switch date, and note it so nobody mistakes it for a traffic change.
If you use a hosted service, also ask what happens to your data if you cancel. With a local database tool, the data stays with you, but check what the uninstall routine removes. For a plugin that stores raw data, deleting tables on uninstall may erase your history, so export first.
WPMusk has not run hands-on tests of any analytics plugin, and this page contains no test results. When a full review is published, it will state what was tested, on which setup and what we saw. This page carries no score: it is guidance for choosing, not a measured result.
The planned method follows the evaluation plan above and the weights listed earlier. We will compare tracker weight against a baseline, test cache behaviour and read each tool’s privacy documentation. For the performance side of that testing, see the Core Web Vitals guide.
Not necessarily, but rules differ by country and by what is collected. Read the plugin’s documentation and, if in doubt, ask a professional.
It can. The size of the tracker and whether it writes to your database on each hit matter. Measure on staging.
Tools define visitors, sessions and bots in different ways, and block lists differ. Pick one as your reference and judge trends rather than absolute counts.
It displays data from connected Google services in your dashboard. The tracking and data storage are handled by those services.
Some tools offer e-commerce reports, often in a paid tier. Check that your shop plugin is supported.
Keep it only as long as you use it. A retention setting limits database growth and privacy exposure.
Rarely in full. Export summaries before you leave and keep them separately.