WordPress Analytics: Track Traffic, Engagement, and Revenue

WordPress does not ship with built-in analytics on self-hosted installs; you choose a tool. The three practical options are Google Analytics 4 (free, event-based, the most flexible and the most common), built-in stats (Jetpack Stats on self-hosted sites, or WordPress.com Stats on the hosted platform, both giving you pageviews and top content), and privacy-first plugins (Independent Analytics, Plausible, Fathom, or self-hosted Matomo, which avoid GA4's complexity and cookie-consent overhead). The gap nearly every default setup leaves open: it tracks where traffic lands but not what traffic does, so you can see that a service page got 2,000 visits without knowing whether any of them became customers. Closing that gap is what separates analytics that informs decisions from analytics that just decorates a dashboard.

This guide compares the tools, lays out the events to track, maps the four funnel stages, and shows how to read the patterns without guessing.

Which Tracking Tool to Use on WordPress

The right tool depends on whether you need deep funnel tracking, simple privacy-friendly counts, or zero-setup stats. Here is the comparison that decides most sites.

The default mistake is installing a stats plugin, checking pageviews and bounce rate, calling a page "performing well," and never connecting that to revenue. GA4 is the most practical free path to closing that gap because its event-based model fits funnel tracking far better than the old session-based Universal Analytics. If your priority is privacy and a clean cookie story, Plausible or Independent Analytics get you most of the value with less setup. The WordPress.com analytics support docs cover the built-in stats, and the r/WordPress community consensus is consistent: GA4 for depth, a privacy-first plugin for simplicity, and almost never the bare Jetpack number alone for a commercial site.

Why Pageview-Only Analytics Misses the Point

Standard WordPress analytics measure consumption, not progression, which is why a page can look healthy and produce nothing. Picture a service page with 2,000 visits a month, a 2:30 average session, and a 55% bounce rate: by the dashboard it is winning. Then you check the CRM and that page produced three leads last month and none closed. It is a traffic success and a commercial failure, and pageview-only analytics cannot tell the two apart.

The fix is to reframe the question from "how many people visited?" to "how many people moved from awareness to evaluation to action, and where did the rest drop off?" This matters most on theme-driven sites where one layout repeats across many pages. If you run twenty service or location pages on the same template, you need per-page funnel data to separate the pages that generate pipeline from the ones that only accumulate traffic. Two pages with identical templates and similar traffic can have wildly different revenue outcomes, and only stage-by-stage tracking reveals which is which.

The Four Funnel Stages to Define First

Before instrumenting anything, define the stages a visitor moves through. A practical model for WordPress pages has four, and each one maps to a measurable signal.

Stage 1, Entry: the visitor arrives. Capture which page, which keyword drove them (from Search Console), and the device and location. Stage 2, Engagement: the visitor interacts beyond landing: scrolling past 50%, clicking an internal link, opening an FAQ accordion, or spending over 30 seconds. A two-second bounce and a three-section read both count as a "visit," but they are not equivalent. Stage 3, Micro-conversion: the visitor takes a step that signals intent without converting: clicking "Get a Quote," starting a form, clicking a phone number, or navigating to a pricing page. These are the leading indicators that your layout is working. Stage 4, Conversion: the visitor completes the primary action: form submission, phone call, booking, or purchase. This is the number that ties to revenue.

Most tools give you Stage 1 out of the box. The whole value of funnel analytics is connecting all four per page and per template type, so you know which patterns produce conversions and which produce traffic that goes nowhere. For high-intent landing pages, these stages map directly onto the section sequence: the hero is Stage 1, the proof section drives Stage 2, the CTA drives Stage 3, and form completion is Stage 4.

Setting Up GA4 Events on WordPress

GA4's event model is the engine of funnel tracking, and the cleanest way to deploy events on WordPress is through Google Tag Manager (GTM) rather than hardcoding them into theme files, so your marketing team can adjust tracking without touching code.

The events worth configuring, mapped to funnel stages:

Use the page_location parameter on every event so each one attributes to a specific page. In GTM, the core triggers are a scroll-depth trigger (25/50/75/100%), a click trigger on a CSS class (.cta-primary, .faq-toggle), a form-submission trigger on your plugin's success event, and a timer trigger for time-on-page milestones. Then connect the Google Search Console API so you can see which keywords drive engaged progression versus bounces; the Search Console API documentation walks through access setup. For phone-heavy businesses, add dynamic number insertion (CallRail, WhatConverts) to attribute calls to specific pages the same way form submissions are attributed. The Intent Analytics Dashboard aggregates these metrics per page and per template type so you can compare a service-page template against a location-page template without stitching three tools together.

Connecting Page Performance to Revenue

Raw conversion counts are useful; connecting them to downstream outcomes is where analytics earns its keep. A page generating fifty form fills sounds great until you learn only two were qualified. Closing that loop needs two things.

Source-page attribution in your CRM. Every form submission should carry the URL of the page where it happened. Most form plugins (Gravity Forms, WPForms, Contact Form 7 with a hidden field) can append the page URL, so when the lead lands in your CRM you can trace it to the specific page and template. Outcome tagging on closed deals. When a lead becomes a customer or gets disqualified, tag the record. Over time this gives you a conversion rate per page that extends from "form fill" to "actual customer acquired."

A concrete example shows why this matters. An HVAC company runs thirty location pages on one template. Funnel analytics shows Location Page A (Dallas) at 800 visits, 40 form fills, 12 qualified leads, 4 customers; Location Page B (Austin) at 1,200 visits, 60 form fills, 8 qualified leads, 1 customer. Page B has more traffic and more form fills but worse business outcomes. Without attribution connecting page performance to lead quality, the team would optimize the wrong page. Per Google's Core Web Vitals documentation, performance metrics influence ranking, but ranking without conversion is expensive vanity. For multi-location brands, this page-to-revenue link is the only honest way to prioritize which pages need work.

Reading the Data Without Guessing

Once data flows, interpretation is the hard part. Here are the patterns to look for and what each one means for your theme.

High traffic, low engagement (high bounce, shallow scroll): the page ranks but the above-the-fold content is not establishing relevance, usually a hero headline too generic for the keyword driving traffic. Good engagement, low micro-conversion (people scroll but do not click the CTA): the content is interesting but the CTA is weak or badly placed; test moving the primary CTA directly after your strongest proof section instead of the page bottom. High micro-conversion, low conversion (people click the CTA but do not submit the form): friction in the form itself, usually too many fields, no expectation-setting, or slow load. Good conversion, low lead quality: the page converts the wrong audience; review the keyword, the headline promise, and add a section stating who the offer is not for. Conversion drops after a theme change: if you pushed a template change and conversions fell at the same traffic, the change caused it; roll back or A/B test the specific section.

Build a monthly review cadence: pull funnel data per template type, compare which structural patterns produce the best Stage 2 to Stage 3 progression, then drill into outliers. Pair quantitative GA4 data with a qualitative heatmap tool like Microsoft Clarity (free) or Hotjar to see not just where visitors drop off but what they interact with first. Use the SaaS templates analytics as a benchmark when comparing multiple template designs.

Turning Analytics Into Theme Decisions

Funnel data should drive your roadmap, not aesthetic preference or competitor mimicry. Four rules translate analytics into changes.

Prioritize by revenue impact. Rank pages by downstream revenue (using CRM-connected data) and fix top-revenue pages first, even if lower-performing pages have more obvious design flaws. Test one section at a time. If the proof section is not driving engagement, change only the proof pattern (swap a testimonial carousel for one detailed case study) and measure Stage 2 to Stage 3 over two to four weeks. Build template variants for different profiles. If service pages convert best with proof above the fold but blog posts convert best with proof mid-page, build separate patterns; the WordPress redesign guide covers scheduling these iterations without disrupting live pages. Feed analytics back into content. Deep engagement that drops at the CTA often signals a missing proof element or FAQ answer, not a design flaw; the SEO outline generator helps identify content gaps for a keyword so rewrites target the actual drop-off point.

The Content Refresh Automation feature acts on funnel data by flagging pages with dropping engagement so analytics drives improvements instead of sitting in a dashboard. For SaaS marketing teams and competitive verticals, this data-driven approach prevents wasted cycles by investing development time where the gap between traffic and revenue is largest.

FAQ about wordpress analytics

Does WordPress have built-in analytics?

Self-hosted WordPress does not include analytics by default; you add a tool. The hosted WordPress.com platform includes Stats, and self-hosted sites can install the Jetpack plugin for similar built-in pageview tracking. For anything beyond pageviews (engagement, conversions, revenue attribution), most sites add Google Analytics 4 or a privacy-first plugin like Independent Analytics, Plausible, or Matomo.

What is the best analytics tool for WordPress?

There is no single best; it depends on your need. Google Analytics 4 is the most flexible and the most common, with free event-based tracking that supports full funnel analysis, at the cost of a learning curve and cookie consent. Plausible and Fathom are best for privacy-first sites that want a clean cookie story. Jetpack or WordPress.com Stats are best for quick pageviews with zero setup. For commercial sites that need to connect pages to revenue, GA4 plus a CRM source field is the practical answer.

How do I add Google Analytics to WordPress?

The cleanest method is through Google Tag Manager: create a GTM container, add the GTM snippet to your theme (or use a plugin like Site Kit by Google or a header-scripts plugin), then configure your GA4 tag and events inside GTM. This keeps tracking changes out of theme code. A simpler but less flexible alternative is the official Site Kit plugin, which connects GA4 and Search Console directly with a guided setup and no GTM.

What is the single most important metric to track on a WordPress site?

For commercial pages, the Stage 3 to Stage 4 conversion rate: the percentage of visitors who click a CTA and then complete the form or call. It isolates your page's performance from traffic quality. If traffic is strong and CTA clicks are healthy but form completions are low, the problem is almost certainly your form or post-click experience, which is directly within your control. Pageviews and bounce rate, by contrast, tell you almost nothing about whether a page makes money.

Ready to connect your WordPress pages to real revenue data? Join wp0 early access and start tracking what actually matters.