WordPress Analytics: Best Plugins and Privacy-Friendly Setup
How to install analytics on WordPress in 2026: plugins vs direct snippet, the `wp_head` action, footer.php fallback, GDPR setup, and the pitfalls of MonsterInsights and Site Kit.
TL;DR
- 1.WordPress has no native analytics. Jetpack Stats is the closest thing and it is too shallow for serious work.
- 2.Most "WordPress analytics plugins" (MonsterInsights, Site Kit, ExactMetrics) are wrappers around GA4 — installing them does not solve GA4's cookie banner or speed problems.
- 3.For privacy-first analytics, the cleanest install is a `wp_head` action in your child theme — no plugin needed.
- 4.If you cannot edit PHP, paste the snippet into `footer.php` or use a small "Insert Headers and Footers" plugin.
- 5.Skip plugins that bundle analytics with SEO, social, and ads — they always slow your site down.
WordPress and the analytics-plugin trap
WordPress runs roughly 40% of the web, and that scale has produced a crowded plugin ecosystem. Search "WordPress analytics" in the plugin directory and you get hundreds of options — most of them are wrappers around Google Analytics with extra UI on top of the same GA4 data.
The trap is that installing one of these plugins feels like solving the analytics problem when it actually adds work: GA4's consent-banner requirement is still on you, the plugin's own scripts add 50–200 KB to every page, and the dashboard inside WP Admin is a copy of the GA4 dashboard with fewer features.
For most WordPress sites in 2026, the right answer is either a single lightweight plugin from a privacy-first analytics provider, or a direct snippet via `wp_head`. We will cover both.
The mental model worth holding: every plugin you install is code that runs on every page load, with database queries, admin hooks, and update cycles you have to maintain. A snippet pasted into `functions.php` adds zero of those costs. So the question for any analytics plugin should be "what does this plugin do that I cannot do with three lines of PHP?" — and for most analytics plugins, the honest answer is "not much."
What WordPress gives you natively (almost nothing)
Out of the box, WordPress has no analytics. There is no built-in dashboard for visitors, page views, or referrers. WordPress.com (the hosted product) ships with Jetpack Stats, but self-hosted WordPress.org users get nothing unless they install a plugin.
Jetpack Stats itself is okay for tracking which posts are popular, but it does not give you device breakdowns, web vitals, real-time funnels, or anything past the basics. It is also tied to a Jetpack/WordPress.com account, which many self-hosters prefer to avoid.
- No native dashboard for visitors / pageviews on self-hosted WordPress
- Jetpack Stats: requires a WP.com account, basic only, no event tracking
- No native event tracking — every form submit, click, or download needs custom code
- No web vitals — and Google ranking quietly punishes slow LCP
The honest take on the big WordPress analytics plugins
The pattern: GA4-wrapper plugins solve a UI problem at the cost of weight and consent overhead. Privacy-first vendor plugins solve the install problem with one script tag and stay out of the way.
- MonsterInsights — the most-installed WordPress GA plugin. Free tier is functional; paid tier gates the features that justify the install. Adds ~100 KB and bundles upsells in the dashboard.
- Google Site Kit — official Google plugin that pipes GA4, Search Console, AdSense into WP Admin. Useful if you live in WP Admin. Does not solve GA4's consent or speed problems.
- ExactMetrics — same business model as MonsterInsights, similar weight, similar gating.
- Independent Analytics — a plugin that stores analytics data inside your WordPress database. Privacy-friendly but blows up your DB on busy sites.
- Plausible / Fathom / Simple Analytics / Sleek — official plugins from privacy-first vendors that drop in the script tag and nothing else. These are the cleanest option.
Install via `wp_head` — the cleanest method, no plugin
If you have a child theme (and you should), the right place for an analytics snippet is a `wp_head` action in `functions.php`. This guarantees the snippet sits inside `<head>` on every page, survives theme updates if you use a child theme, and adds zero extra plugins to maintain.
<?php
/**
* Inject Sleek Analytics in <head> on every front-end page.
* Place this in a child theme's functions.php so it survives parent updates.
*/
add_action( 'wp_head', function () {
if ( is_admin() ) {
return; // never load analytics in WP Admin
}
?>
<script async src="https://getsleek.io/v1.js" data-site="YOUR_SITE_KEY"></script>
<?php
}, 1 );Tracking custom events on WordPress — forms, downloads, outbound links
Once the base script is in place, custom events are JavaScript. WordPress does not need anything special — you bind a listener in a `wp_enqueue_scripts` hook or inline it after the analytics snippet.
The events worth tracking on a typical content / lead-gen WordPress site are: contact form submits (Contact Form 7, WPForms, Gravity Forms, Fluent Forms), PDF downloads, outbound link clicks, and clicks on the primary CTA in the navbar.
<?php
add_action( 'wp_footer', function () {
if ( is_admin() ) return;
?>
<script>
// Outbound link clicks
document.addEventListener('click', function (e) {
var a = e.target.closest('a');
if (!a || !a.href) return;
var sameHost = a.host === location.host;
if (sameHost) return;
if (typeof window.sleek === 'function') {
window.sleek('track', 'outbound_click', { url: a.href });
}
});
// Contact Form 7 success event
document.addEventListener('wpcf7mailsent', function (e) {
if (typeof window.sleek === 'function') {
window.sleek('track', 'form_submit', { form_id: e.detail.contactFormId });
}
});
</script>
<?php
});Pitfalls that bite WordPress sites
- Caching plugins fight you. WP Rocket, W3 Total Cache, and Litespeed Cache will sometimes cache the analytics script in a way that breaks site keys. Add the analytics domain to the "ignore" list.
- Page builders strip scripts. Elementor and Divi can re-render templates and lose inline scripts. Always inject via `wp_head` or `wp_footer`, never via the visual editor.
- AMP pages are a separate world. If you serve AMP, you need a separate analytics integration — most AMP plugins support `<amp-analytics>` for the major providers.
- Theme updates wipe direct edits. Use a child theme. Always.
- Multisite networks need per-site keys. If you run WP Multisite, each subsite is a different domain to your analytics tool. Configure the snippet to read the site key from a network option or `get_current_blog_id()`.
Recommended setups by site type
- Personal blog (1–10K visits/mo): one privacy-first plugin (Sleek, Plausible, Fathom) and nothing else.
- Content site (10K–500K visits/mo): direct `wp_head` snippet + a privacy-first dashboard. Skip MonsterInsights.
- WooCommerce store (any size): privacy-first analytics for traffic, plus the native WooCommerce reports for revenue. Add a `purchase` event from the thank-you page.
- Lead-gen / agency site: privacy-first analytics + form-submit events. Skip the all-in-one SEO/social/analytics suite plugins.
- Membership site (MemberPress, LearnDash): privacy-first analytics for traffic, plus the platform's native reports for course completion and renewal.
Alternatives to Google Analytics on WordPress
For most WordPress sites, the right move in 2026 is to skip GA4 entirely and use a privacy-first analytics tool. The cookie-banner overhead and the data loss from declined consent make GA4 worse than the alternatives for non-paid-ads use cases.
The strong alternatives all ship official WordPress plugins that wrap a single script tag — they do not add weight beyond the analytics script itself. Pick whichever has the dashboard your team actually wants to look at on Monday morning.
A note on Matomo, which often comes up in WordPress conversations: Matomo is a powerful self-hosted option that gives you GA4-level depth without sending data to Google. The catch is that you are running another database and another web app to maintain. For technical teams that want the depth and own their stack, it is a real option. For everyone else, the hosted privacy-first tools are less work.
- Sleek — AI chat plus a polished real-time view, native Stripe for WooCommerce
- Plausible — open source, mature, most popular in the WordPress community
- Fathom — privacy-first, EU-hosted option, simple dashboards
- Simple Analytics — single-page dashboard, very lightweight
- Independent Analytics — stores data in your WP DB; good for tiny sites that do not want a third party at all
- Matomo — self-hosted GA4-depth alternative, more maintenance overhead
Frequently asked questions
Does WordPress have built-in analytics?
No. Self-hosted WordPress.org has no native analytics. WordPress.com sites and Jetpack-connected sites get Jetpack Stats, which is basic. For real analytics, install either a privacy-first vendor plugin or paste a snippet via `wp_head`.
Is MonsterInsights worth it?
MonsterInsights is a wrapper around Google Analytics 4 that adds dashboards inside WP Admin. It does not solve GA4's consent-banner problem and adds plugin weight. If you already use GA4 and want a friendlier UI inside WP Admin, it is fine. If you are starting fresh, a privacy-first tool with its own dashboard is usually a better fit.
Where should I add a tracking script in WordPress?
In `<head>`, via a `wp_head` action in your child theme's `functions.php`. If you cannot edit PHP, use `footer.php` or a small "Insert Headers and Footers" plugin. Avoid pasting into page-builder code blocks — they strip scripts on re-render.
Do I need a cookie banner on WordPress?
Only if you use cookies for tracking. GA4 and Meta Pixel both set cookies and need consent in the EU. Cookieless analytics tools (Sleek, Plausible, Fathom) do not require a banner under GDPR.
What is the lightest WordPress analytics plugin?
Vendor plugins from Plausible, Fathom, Simple Analytics, and Sleek all add a single ~1 KB script tag and nothing else. They are essentially as light as pasting the snippet manually, with the convenience of a settings page in WP Admin.
How do I track form submits in WordPress?
Bind to the form library's success event. Contact Form 7 fires `wpcf7mailsent`, WPForms fires `wpformsAjaxSubmitSuccess`, Gravity Forms fires `gform_confirmation_loaded`. From the handler, call your analytics SDK's track function with a `form_submit` event name.
Will analytics slow down my WordPress site?
A modern privacy-first analytics tool adds 1–3 KB and runs async — the impact on LCP is unmeasurable. The plugins that slow WordPress sites down are the all-in-one suites that bundle analytics with SEO, social, and 30 other features. Stick to a single-purpose plugin or a direct snippet.
Track your own growth loop
Sleek Analytics gives you visitors, sources, pages, devices, and real-time behavior with one lightweight script. No cookies, no GDPR banners.
Related reading
Shopify Analytics in 2026: A Complete Guide
How to set up analytics on Shopify in 2026: native reports, GA4 limits, cookieless options, theme.liquid install, custom checkout events, and the pitfalls that bite store owners.
PlatformWebflow Analytics: Track Visitors Without Cookies
Install analytics on a Webflow site in 2026: Project Settings custom code, page-level snippets, native Webflow form submit tracking, GDPR-friendly setup, and the limits of Webflow Analyze.
ComparisonsSleek vs Plausible (2026): Which Privacy-First Analytics Tool Wins?
Sleek Analytics vs Plausible in 2026: pricing, features, real-time capabilities, AI chat, revenue tracking, and migration paths. Honest comparison from a competitor.