We Compared The Features of 99 Web Analytics Tools: Here's What We Found

Last updated: May 25, 2026

Privacy controls are universal in web analytics tools, but that does not mean the category is privacy-first. We built a dataset of 99 web analytics tools, classified every feature with a seven-label availability scheme, and found a market where basic reporting is almost everywhere while revenue, behavior, lead, publisher, and server-log capabilities split sharply by workflow.

The dataset spans seven workflow families: privacy-first traffic analytics, B2B visitor identification, UX behavior optimization, general web analytics platforms, server log analytics, WordPress site analytics plugins, and publisher content analytics. For each tool, we recorded a comparable feature taxonomy covering analytics, attribution, conversion, revenue, behavior, privacy, content, lead enrichment, and log diagnostics, then classified availability to capture actual packaging rather than marketing claims.

The full feature comparison table

We built this dataset from scratch. For each of the 99 web analytics tools, we inspected public feature information and recorded the primary workflow, business model, and availability of 12 feature categories: website traffic and audience reporting, traffic sources and campaign attribution, event and goal conversion tracking, ecommerce and revenue performance tracking, real-time dashboards and alerting, segmentation and custom reporting filters, privacy consent and data ownership controls, heatmaps and user behavior replay, form friction and abandonment analysis, publisher content and editorial analytics, B2B account identification and lead enrichment, and server log parsing and HTTP diagnostics. Each feature was classified with one of seven standardized availability labels. The full comparison table is below.

Questions on features of web analytics tools

These are the questions that matter if you are deciding which features in web analytics tools are table stakes, which ones still differentiate, which ones should be paid, and what to build if you are shipping your own product in the category.

Which features are commoditized in web analytics tools?

The commoditized features in web analytics tools are basic reporting, traffic attribution, privacy controls, segmentation, real-time dashboards, and event tracking. Each appears in at least 91 of the 99 tools, which means the credible baseline is much broader than pageview reporting alone.

Website traffic and audience reporting is the clearest table-stakes feature. It appears in 98 tools, so the category has effectively moved past the question of whether a tool can show visitors, pages, devices, locations, and audience trends.

Traffic sources and campaign attribution is equally mature at 98 tools. Builders should treat source, referrer, UTM, and campaign reporting as part of the core analytics surface, not as an advanced add-on.

Privacy consent and data ownership controls are the surprising member of the commoditized group. They appear in every tool, which means even UX behavior tools, B2B visitor identification tools, and server log tools now need a privacy story.

Segmentation and real-time dashboards sit just behind the universal features. Segmentation appears in 97 tools and real-time dashboards appear in 95, which makes custom filtering and live visibility difficult to omit from a modern web analytics product.

Event and goal tracking is slightly less universal but still part of the expected core. It appears in 91 tools, and every general web analytics platform, publisher content analytics tool, UX behavior tool, and B2B visitor identification tool in the dataset includes it.

The builder takeaway is that a web analytics MVP cannot stop at traffic charts. It needs reporting, attribution, segmentation, real-time visibility, privacy controls, and some conversion measurement before buyers will read it as complete.

Which features are usually free by default in web analytics tools?

The features most often free in web analytics tools are privacy controls, website reporting, and server log diagnostics, but none is universally free by default. Website reporting is free in 50.0% of present implementations when free-full and free-limited are combined, while privacy controls are free in 32.4%.

Basic website reporting has the broadest free surface because it is both commoditized and easy to cap. Among tools that offer it, 21.4% make it free-full and 28.6% make it free-limited.

That free availability is not evenly distributed. WordPress analytics plugins such as Koko Analytics, WP Statistics, Slimstat Analytics, and Statify often ship basic reporting as free-full, while many privacy-first SaaS tools such as Plausible, Fathom, Pirsch, and Simple Analytics keep it paid-only.

Privacy controls look more free than conversion or revenue features. They have 27 free-full cases, including open or self-hosted tools such as Umami, GoatCounter, Ackee, and Open Web Analytics, but restricted and unclear cases still make the category harder to read than the headline suggests.

Server log diagnostics has the highest free-full share among specialist features at 41.7% of present implementations. AWStats, GoAccess, Webalizer, W3Perl, and Analog reflect the open-source heritage of that workflow.

Conversion-oriented features are rarely free-full. Event tracking is free-full in only 5.5% of present implementations, ecommerce tracking in 5.5%, heatmaps in 3.3%, and form analysis in 3.6%.

The pattern for builders is to make entry-level reporting free or free-limited if using a freemium motion, but avoid giving away the deeper operational layer. The category expects free access to visibility, not unlimited access to conversion, revenue, or behavior diagnosis.

Which features are most often limited, paywalled, or premium-only in web analytics tools?

The most aggressively gated features in web analytics tools are B2B lead enrichment, real-time dashboards, segmentation, heatmaps, and event tracking. B2B lead enrichment is 80.0% paid-only among tools that offer it, while segmentation and real-time dashboards are paid-only in nearly half of present implementations.

B2B account identification and lead enrichment is the cleanest premium feature in the dataset. It has no free-full cases, no trial-only cases, and 16 of 20 present implementations are paid-only.

Segmentation is a broad feature with premium packaging. It appears in 97 tools, but 47 of those implementations are paid-only, which makes advanced filters, saved segments, and custom report depth a reliable paywall.

Real-time dashboards are also heavily monetized despite being nearly table stakes. Of the 95 tools that offer them, 46 make them paid-only, with only 6 free-full cases.

Behavior analytics uses a different gating mix. Heatmaps and replay are paid-only in 46.7% of present implementations and free-limited in another 40.0%, which means vendors usually expose a small taste or put the feature behind a plan boundary.

Restricted gating mostly affects privacy controls rather than the expected premium features. Privacy and data ownership controls have 12 restricted cases, especially in workflows where implementation depends on consent configuration, deployment choices, or data handling requirements.

Unclear packaging is its own kind of friction. Ecommerce tracking is unclear in 30 of 55 present implementations, so buyers can see that revenue analytics exists but often cannot tell what plan, integration, or setup makes it usable.

Knowing what to charge for is half the job. The other half is getting seen: our database of 450+ businesses breaks down how each one brings in customers.

Which features still set web analytics tools apart?

The strongest differentiators in web analytics tools are ecommerce tracking, heatmaps and replay, form analysis, B2B lead enrichment, publisher analytics, and server log diagnostics. Each feature either sits below 60% overall coverage or is concentrated in a workflow where it defines the product boundary.

Ecommerce tracking is the broadest differentiator because it sits between table stakes and specialist depth. It appears in 55.6% of the dataset, but coverage jumps to 100% in publisher content analytics, 85% in general web analytics platforms, and 78% in WordPress analytics plugins.

Heatmaps and behavior replay differentiate UX behavior tools from the rest of the market. The feature appears in 16 of 17 UX behavior tools, but only 4 of 25 privacy-first analytics tools and 2 of 19 B2B visitor identification tools.

Form analysis is even more concentrated. It appears in 13 of 17 UX behavior optimization tools, while it is absent across publisher content analytics and server log analytics.

B2B account identification is not a quality marker for a generic analytics tool. It is a workflow marker: all 19 B2B visitor identification tools include it, while nearly every other workflow has zero coverage.

Publisher analytics and server log diagnostics work the same way. Publisher analytics appears in all 5 publisher content tools, while server log diagnostics appears in all 11 server log tools, but neither is a general expectation across web analytics tools.

The practical rule is to choose one differentiator that matches the buyer workflow. A privacy-first tool should not chase every specialist feature, but a UX behavior product without replay or form friction analysis looks incomplete.

Which features are rarely offered in web analytics tools?

The rarest features in web analytics tools are publisher content analytics, server log diagnostics, B2B lead enrichment, form analysis, and heatmaps or replay. Publisher analytics appears in only 10.1% of tools, and server log diagnostics appears in only 12.1%.

Publisher content and editorial analytics is the rarest feature because it is not a general analytics need. It matters deeply for tools like Chartbeat, Parse.ly, IO Technologies, Publytics, and Marfeel Compass, but it rarely appears outside publisher and WordPress-adjacent workflows.

Server log diagnostics is similarly narrow. Tools such as AWStats, GoAccess, Webalizer, Sawmill, and Angelfish Software make log parsing central, but the feature is absent from privacy-first, UX behavior, B2B, publisher, and WordPress workflows in this dataset.

B2B lead enrichment appears in 20 tools, but 19 of them are in the B2B visitor identification workflow. That concentration makes the feature rare overall even though it is universal inside its own category.

Form analysis appears in 28 tools and heatmaps or replay appear in 30. Those are not tiny counts, but their concentration in UX behavior tools means they remain rare for someone comparing the entire web analytics market.

Rarity in web analytics tools usually means workflow specificity, not weak demand. A feature can be rare in the overall dataset and still be mandatory inside the niche where buyers expect it.

Which missing features create the biggest opportunity in web analytics tools?

The biggest opportunities in web analytics tools sit at workflow intersections: ecommerce tracking for privacy-first tools, behavior diagnostics for general analytics platforms, and clearer revenue packaging across the category. Ecommerce tracking appears in only 11 of 25 privacy-first tools, while heatmaps appear in only 8 of 13 general platforms.

Privacy-first analytics has the clearest expansion gap. These tools are strong on reporting, attribution, dashboards, segmentation, and privacy, but ecommerce tracking appears in only 44% of the workflow.

That gap matters because privacy-first tools often sell to founders and marketers who still care about revenue. A privacy-first product that makes ecommerce tracking simple and clearly packaged could stand out without abandoning its core promise.

General web analytics platforms have another opportunity around behavior diagnosis. They already cover the analytics core, but only 62% include heatmaps or replay and only 38% include form analysis.

WordPress analytics plugins show a different kind of opening. They have strong free reporting and privacy coverage, but none of the 9 tools includes heatmaps or replay, even though WordPress site owners often need practical page-level diagnosis.

The largest category-wide gap is not just missing ecommerce tracking, but unclear ecommerce tracking. With 30 unclear cases among 55 present implementations, a vendor can differentiate simply by making revenue analytics packaging explicit.

The builder rule is to look for adjacent workflows where the buyer problem is obvious but the feature is not yet normalized. In web analytics tools, those gaps sit around privacy-compatible revenue analytics, lightweight behavior diagnosis, and cleaner ecommerce packaging.

A sharp product still needs a way in front of buyers. See how 450+ businesses did it in our database, channel by channel.

What should be free versus paid in web analytics tools?

In web analytics tools, free should cover basic traffic visibility, lightweight attribution, and simple privacy-safe reporting. Paid should start where the tool creates operational leverage: segmentation depth, real-time alerting, event tracking scale, ecommerce tracking, replay, form analysis, lead enrichment, and specialist diagnostics.

The free surface should be enough for a buyer to trust the data. That usually means pageviews, visitors, referrers, campaigns, devices, top pages, and basic filters, especially if the tool competes with free or open-source alternatives.

Free-limited is safer than free-full for commercial tools. Website reporting already has 28 free-limited cases, which shows the category accepts caps on traffic volume, retention, sites, seats, or reporting depth.

Event tracking belongs on the border between free and paid. It is present in 91 tools, so buyers expect it, but only 5 tools make it fully free, which means a limited free version and paid scale fits the market norm.

Ecommerce tracking should usually be paid or at least tightly limited. It appears in just over half of the dataset and has a high unclear rate, so clear paid packaging can be a strength rather than a drawback.

Behavior and lead features are the safest hard gates. Heatmaps, replay, form analysis, and B2B account identification are either specialist or workflow-defining, so giving them away fully would over-deliver compared with the category.

The cleanest packaging strategy is to make analytics visibility free, make conversion instrumentation limited, and make revenue, diagnosis, enrichment, and advanced reporting paid. That matches how the category already teaches buyers to evaluate and upgrade.

Which features make users upgrade to paid plans in web analytics tools?

Users upgrade in web analytics tools for better segmentation, real-time visibility, conversion tracking, ecommerce tracking, behavior diagnosis, and lead identification. Segmentation and real-time dashboards are both present in more than 95 tools, yet nearly half of their implementations are paid-only.

The first upgrade lever is depth on universal features. Buyers may start with traffic reports, but they pay when they need custom reports, saved filters, alerts, team workflows, or historical depth.

Segmentation is especially effective because it connects basic analytics to action. A user who wants to isolate channels, campaigns, pages, accounts, devices, or cohorts has already moved beyond passive reporting.

Real-time dashboards and alerting drive upgrades when the product becomes operational. A founder may tolerate delayed reports, but a publisher, growth team, or B2B sales team often pays for live signals.

Conversion and ecommerce features create the next upgrade layer. Event tracking is widely expected, while ecommerce tracking is less universal and more ambiguous, which makes clean revenue reporting a strong paid-plan trigger.

Behavior diagnosis and B2B identification are stronger expansion triggers than entry-level upgrades. Hotjar, FullStory, Mouseflow, Lead Forensics, Leadinfo, and Albacross sell a more specific outcome than analytics visibility, so the upgrade is tied to diagnosis or sales intelligence rather than reporting volume alone.

The best paid-plan architecture combines two motions: caps on the analytics core and capability gates on specialist features. That lets lightweight users adopt the product while serious teams pay when the data starts shaping revenue, UX, or sales activity.

What should the MVP of a web analytics tool include and what should it skip?

The MVP of a web analytics tool should include website reporting, traffic attribution, privacy controls, segmentation, real-time dashboards, and event tracking. It should skip specialist features unless the product is explicitly built for UX behavior, B2B visitor identification, publishing, ecommerce, WordPress, or server log analytics.

The six-feature core is the minimum credible baseline. Website reporting, attribution, privacy controls, segmentation, dashboards, and event tracking all exceed 91% coverage in the dataset.

The MVP should also make privacy legible from day one. Because privacy controls appear in all 99 tools, buyers no longer see privacy as a nice-to-have compliance paragraph.

Ecommerce tracking depends on the target buyer. A general analytics platform or WordPress plugin should prioritize it earlier, while a privacy-first traffic tool can launch without it but needs a credible roadmap if it targets commercial sites.

Heatmaps, replay, and form analysis should be skipped unless the product is a UX behavior tool. They are powerful features, but their overall penetration is only around 30%, and building them too early shifts the product into a different competitive set.

B2B enrichment, publisher analytics, and server log diagnostics should be treated as workflow anchors, not generic MVP features. They belong in the first version only when the product's positioning depends on them.

The MVP decision rule is simple: ship the analytics core plus one workflow anchor. A web analytics tool without the core looks incomplete, while a tool with too many specialist anchors looks unfocused.

What are other interesting feature patterns in web analytics tools?

Beyond the headline patterns, web analytics tools reveal several quieter signals about how vendors bundle privacy, revenue, behavior, and workflow-specific capabilities.

Privacy is universal, but it is not packaged consistently. The same broad feature family includes free-full self-hosting, paid-only data ownership promises, restricted consent-dependent controls, and unclear compliance language.

This means privacy should be read as a positioning layer and a packaging layer at the same time. In web analytics tools, saying “privacy-friendly” does not tell you whether the buyer actually controls data, consent, hosting, or retention for free.

Traffic attribution has a surprisingly high ambiguity rate for such a common feature. It appears in 98 tools, but 22 present implementations are unclear, which suggests campaign attribution is often implied in screenshots or docs without clean plan-level packaging.

Publisher analytics tools are unusually complete on the basics but narrow on adjacent capabilities. All 5 include reporting, attribution, events, ecommerce, real-time dashboards, segmentation, and privacy controls, yet none includes heatmaps, form analysis, B2B enrichment, or server log diagnostics.

WordPress analytics plugins look more like product-led freemium businesses than like enterprise analytics platforms. They often give away basic reporting and privacy controls, then monetize events, ecommerce, form-related features, or Google Analytics-style enhancements.

Server log analytics has the clearest old-versus-new split. Free tools such as AWStats, GoAccess, Webalizer, W3Perl, and Analog coexist with paid products such as Angelfish Software, SmarterStats, Sawmill, and Deep Log Analyzer, creating a polarized free-full versus paid-only pattern.