I Built a Google Analytics Alternative for WordPress Because Analytics Got Too Complicated

There was a time when Google Analytics was straightforward. Universal Analytics, as it is now called to distinguish it from its successor, had a left sidebar with clearly labeled sections: Audience, Acquisition, Behavior, Conversions. Clicking "Audience Overview" showed pageviews, sessions, users, bounce rate, and average session duration on a clean graph with a date range selector. The information was immediately useful. How many people visited the site? Where did they come from? Which pages did they look at? How long did they stay? These are the questions that every website owner asks, and Universal Analytics answered them without requiring a degree in data analytics to interpret the results.

Then Google Analytics 4 arrived, and the simplicity vanished. GA4 replaced the intuitive page-and-session model with an event-based model that treats every interaction as a discrete event. Pageviews are events. Scrolls are events. Clicks are events. The concept of a "bounce rate" was initially removed entirely (it was later reintroduced after overwhelming user backlash, but with a different definition than before). The reporting interface was redesigned around "explorations" and "funnels" and "segments" that are powerful for enterprise analytics teams but bewildering for the small business owner who just wants to know if their blog post got any traffic this week.

The migration from Universal Analytics to GA4 was not optional. Google shut down Universal Analytics and stopped processing data, leaving every website owner with two choices: learn GA4 or find something else. Millions of people chose to learn GA4. Many of them are still learning, years later, because the interface is genuinely complex and the documentation assumes a level of familiarity with analytics concepts that most small site owners simply do not have. The Website Analytics by YEB WordPress plugin exists because the alternative to learning GA4 should not require learning another complex system. It should require installing a plugin and looking at a dashboard that makes sense within thirty seconds of opening it.

What Most Website Owners Actually Need to Know

After running multiple websites across different niches for years, the list of analytics questions that actually influence decisions is remarkably short. How many visitors came today, this week, this month? Which pages are they visiting? Where are they coming from (search engines, social media, direct, referral links)? What countries are they in? What devices are they using? Are the numbers going up or down compared to the previous period? That is genuinely the complete list for the vast majority of website owners. Not funnels. Not cohort analysis. Not custom event tracking with parameter dimensions. Just the basics, presented clearly.

The WordPress plugin was built around this exact list. The dashboard shows a single-page overview with all of these metrics visible without scrolling, clicking, or navigating between reports. Pageviews and unique visitors are displayed as daily counts on a time series chart. Top pages are listed with their view counts. Referrers show where traffic is coming from. Countries and devices are displayed as simple tables. The date range is adjustable, and comparison with the previous period is available for every metric. Everything a typical site owner needs to make informed decisions about their content and marketing is visible in one place, on one screen, without a single moment of confusion about what the numbers mean.

The plugin achieves this simplicity not by being technically inferior to GA4 but by making deliberate choices about scope. GA4 can track custom events, build audience segments, measure e-commerce conversions, and integrate with Google Ads. The YEB analytics plugin does none of those things, and that is a feature rather than a limitation. Every feature that gets excluded is a feature that cannot confuse the user, cannot add visual clutter to the dashboard, and cannot break in a way that requires troubleshooting. The result is a tool that does less but does it better, at least for the audience it was designed for: WordPress site owners who want clear, actionable traffic data without the overhead of an enterprise analytics platform.

Privacy First and Why That Matters More Than Ever

Google Analytics works by loading a JavaScript tracking script from Google's servers on every page of the website. That script collects visitor data and sends it to Google's infrastructure, where it is processed, stored, and used not only for the website owner's analytics but also for Google's own advertising ecosystem. This is why GA4 is free. The product is not the analytics software. The product is the data that flows through it, which helps Google build advertising profiles and improve ad targeting across its network.

For website owners who care about visitor privacy, or who operate in jurisdictions with strict data protection laws like the GDPR in Europe or the CCPA in California, this data flow creates a compliance burden. Cookie consent banners are required in many regions specifically because tools like Google Analytics set tracking cookies that follow visitors across websites. The consent banners themselves degrade the user experience, and a significant percentage of visitors refuse consent, which means the analytics data is incomplete because it only represents the subset of visitors who actively clicked "accept."

The YEB analytics plugin takes a fundamentally different approach. It does not load any third-party scripts. It does not send data to external servers. It does not set tracking cookies. All analytics data is processed and stored on the website's own server, within the WordPress database. Visitor identification uses privacy-preserving techniques that do not involve persistent tracking across sessions or across websites. This design means that the plugin does not trigger cookie consent requirements in most jurisdictions, because there is no cookie to consent to. It also means that 100% of visitors are tracked rather than only the subset who accept a consent banner, which produces more accurate traffic data than a GA4 installation with consent mode enabled.

The privacy architecture extends to the underlying APIs that power the plugin's geolocation and device detection features. The GeoIP API resolves visitor IP addresses to country and city names without sending those IP addresses to third-party geolocation services. The device analysis API identifies browser, operating system, and device type from the user agent string without external lookups. The bot detection API separates verified crawler traffic (Googlebot, Bingbot, and others) from human visits and from fake bots that masquerade as crawlers. All three APIs operate within the same privacy-first architecture, processing data without exposing it to external parties.

The Bot Tab and Why Separating Crawlers From Humans Changes Everything

One of the most underappreciated features of the plugin is the dedicated bot traffic tab. Most analytics tools either exclude bot traffic entirely (which means the website owner never sees it and has no idea how much of their server load comes from crawlers) or include it indiscriminately in the traffic counts (which inflates visitor numbers and makes pageview data unreliable). Neither approach is ideal. Bot traffic is valuable information. Knowing which search engines are crawling the site, how frequently they crawl, and which pages they focus on is essential for SEO. But bot traffic mixed into human visitor counts creates a distorted picture of actual audience engagement.

The bot detection system uses a multi-layered approach to classify traffic. Verified crawlers from major search engines are identified by cross-referencing their claimed identity (the user agent string) with their actual IP address range. A request claiming to be Googlebot but originating from a residential IP address in Romania is flagged as a fake bot, which is itself a valuable security signal. Legitimate crawlers are categorized by search engine (Google, Bing, Yandex, Baidu, DuckDuckGo, and dozens of others) and displayed in their own dedicated tab with crawl frequency, pages crawled, and crawl patterns over time.

The fake bot detection is particularly useful for site owners who are experiencing unusual traffic patterns. A sudden spike in pageviews looks exciting in the analytics dashboard until it turns out to be entirely composed of scrapers, spam bots, or vulnerability scanners. Without bot separation, these spikes can lead to misguided decisions: "our traffic doubled this month" sounds very different from "our bot traffic doubled this month because someone is scraping our content." The dedicated bot tab makes this distinction immediately obvious, and the historical data allows site owners to identify when bot activity patterns change, which can be an early warning sign of security issues or content theft.

Sessions and UTM Tracking and CSV Export

Beyond basic pageview counting, the plugin tracks visitor sessions with entry pages, exit pages, and page-per-session counts. A session represents a continuous visit from arrival to departure, and understanding session behavior reveals how visitors actually interact with the site rather than just which pages they land on. A high page-per-session count suggests engaging content that encourages exploration. A low count with high traffic on a specific page suggests that visitors are finding what they need quickly and leaving, which may be perfectly fine for a FAQ page but concerning for a blog post that is supposed to lead readers deeper into the site.

UTM parameter tracking brings campaign attribution into the plugin without requiring any external tools. UTM parameters (source, medium, campaign, term, content) are the standard method for tracking which marketing campaigns drive traffic, and the plugin captures and reports on them automatically. A link shared in a newsletter with utm_source=newsletter and utm_campaign=march2026 will appear in the referrer data with those campaign labels attached, making it possible to measure the effectiveness of specific marketing efforts. This feature alone replaces a significant chunk of what marketers use Google Analytics for, and it works within the same clean, single-page dashboard without requiring "explorations" or "custom reports."

The CSV export feature addresses the inevitable moment when someone needs to take analytics data outside the dashboard. Whether for a client report, a board presentation, a tax filing that requires website traffic evidence, or simply a backup, the ability to export raw data as a CSV file means the analytics data is never locked inside the plugin. Every metric visible on the dashboard can be exported with full date-range control, producing a spreadsheet that can be opened in Excel, imported into Google Sheets, or processed by any data analysis tool. This portability is a deliberate design choice. The data belongs to the website owner, not to the analytics tool, and exporting it should be as easy as clicking a button.

The plugin is available on the official WordPress plugin repository, which means installation is the standard WordPress experience: search, install, activate. No account creation on an external platform. No JavaScript snippets to paste into theme files. No DNS verification or property configuration. The dashboard appears in the WordPress admin sidebar immediately after activation, and data collection begins on the next pageview. For site owners who have spent hours trying to connect GA4 to their WordPress installation through tag managers, verification steps, and data stream configurations, the simplicity of "install and it works" is not just convenient. It is a relief.