{"id":11945,"date":"2026-10-15T23:38:33","date_gmt":"2026-10-15T15:38:33","guid":{"rendered":"https:\/\/aeosub.com\/onlygrow-analytics\/"},"modified":"2026-10-15T23:38:33","modified_gmt":"2026-10-15T15:38:33","slug":"onlygrow-analytics","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/onlygrow-analytics\/","title":{"rendered":"OG Analytics"},"content":{"rendered":"
\"OG<\/div>\n
\n
LethaldiranMX Insight<\/div>\n
\n
\n

OG Analytics provides a privacy-first, self-hosted telemetry engine designed to deliver real-time traffic tracking directly inside WordPress without relying on third-party services. By decoupling visit recording from full database queries through a lightweight file-based queuing system, it maintains low ingestion overhead while remaining fully compatible with front-end page caching. It is ideal for site owners, editorial teams, and privacy-conscious organizations requiring strict data sovereignty alongside immediate post-level performance insights.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin serves as a first-party analytics engine for site administrators who want to eliminate external tracking scripts while keeping metrics close to their content creation workflow. It solves the operational drag of context-switching between external dashboards by placing real-time view counts, 404 monitors, and campaign attribution directly within the WordPress dashboard, admin bar, and block editor sidebar. It fits seamlessly into publishing platforms, corporate sites, and privacy-focused organizations seeking complete local control over visitor telemetry.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> Storing event data locally means that high-volume traffic will naturally increase database storage requirements over time, making database maintenance an operational factor despite the plugin’s daily summary aggregation logic. Additionally, hosting environments with overly restrictive file-write permissions or ephemeral file systems may disrupt the file-queue processing mechanism. Beyond these infrastructure considerations, none identified based on available information.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"OG <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nonlygrow<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv0.2.02<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.5 \/ 7.1.3<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-10-15 3:36pm GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
See every visit the second it happens \u2014 fast even with millions of views, and stored only in your own database.<\/div>\n

OnlyGrow Analytics (OG Analytics) records how people use your site and keeps everything in your own WordPress database. Nothing is sent to a third party.<\/p>\n

What it records<\/h4>\n
    \n
  • Page views, sessions and time on page \u2014 today’s numbers include the visits that just happened, no waiting for a cron.<\/li>\n
  • Missing pages (404): which removed or mistyped addresses still get visits.<\/li>\n
  • Traffic sources: referrers, UTM campaigns and click IDs (fbclid, gclid, ref).<\/li>\n
  • Devices, browsers and operating systems.<\/li>\n
  • Downloads, outbound links and custom events.<\/li>\n
  • Bounce rate, daily totals and weekly\/monthly retention.<\/li>\n
  • A sortable “Views” column in your posts and pages lists.<\/li>\n<\/ul>\n

    What you see<\/h4>\n
      \n
    • A dashboard with the visits chart, today’s key numbers compared with the same time yesterday (or the previous period), visitors online, and the top pages, sources, devices and countries with a world map.<\/li>\n
    • Reports for visitors, pages and entry pages, with filters.<\/li>\n
    • Inside WordPress: the views of each post in the admin bar, a chart of the post in the block editor sidebar and a chart on the WordPress dashboard.<\/li>\n<\/ul>\n

      How it works<\/h4>\n

      A small script (about 2 KB) sends each event to your own site, which queues it in a file and processes the queue in batches. Recording a visit does not load WordPress: it costs one file write, not a set of database queries. Because the script runs in the visitor’s browser, counting keeps working when pages are served from a cache.<\/p>\n

      Reports read daily summaries for past days and the raw data only for today, so they stay fast as your site grows. The processing adapts to traffic spikes on its own: nothing to configure.<\/p>\n

      Days and hours follow your site’s timezone (Settings \u2192<\/span> General). Speed testers such as PageSpeed and automated browsers are not counted.<\/p>\n

      Referrer spam and known bots are left out of your numbers out of the box: visits from more than 2,000 known spam sites (the public domain list maintained by the Matomo community) and from known bots are detected and kept apart, so they never inflate your statistics. The spam list ships inside the plugin and is updated with each release, so nothing is downloaded. You can view it, or choose to count these visits, in Settings \u2192<\/span> Exclusions.<\/p>\n

      You can also leave out content types, IP addresses and custom rules (Settings \u2192<\/span> Exclusions). Excluded visits are not saved.<\/p>\n

      Ad blockers often block addresses that contain words like “analytics”. With ghost mode (on by default, Track settings), the script and the address that receives visits use a neutral name unique to your site. Your data still never leaves your site.<\/p>\n

      Logged-in users are counted too, including you: visit your site and your own visit shows up right away, so you can check it works.<\/p>\n

      Privacy<\/h3>\n

      All visitor data stays in your own database. No visitor data is ever sent to a third party.<\/p>\n

        \n
      • Visitors are identified by a random ID kept in the browser’s local storage. No cookies are set by default.<\/li>\n
      • The visitor’s IP address is stored without its last part (203.0.113.0) by default, as Google Analytics does. The country and city are found with the full address before it is stored, so nothing is lost. You can turn this off in Settings \u2192<\/span> Data \u2192<\/span> “Anonymize IP addresses”.<\/li>\n
      • Browser fingerprinting is off by default.<\/li>\n<\/ul>\n

        External services<\/h4>\n

        To show countries and cities, the plugin downloads the free IP to City Lite database from DB-IP (https:\/\/db-ip.com) once after activation and then once a month. The file is stored in your uploads folder and every lookup happens on your own server: no IP address is sent anywhere. Only the database file is downloaded; nothing about your site or visitors is uploaded.<\/p>\n

          \n
        • Source: https:\/\/download.db-ip.com\/free\/<\/li>\n
        • License: Creative Commons Attribution 4.0 (https:\/\/creativecommons.org\/licenses\/by\/4.0\/) \u2014 IP Geolocation by DB-IP (https:\/\/db-ip.com)<\/li>\n
        • Terms and privacy: https:\/\/db-ip.com\/legal<\/li>\n<\/ul>\n
          Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>","protected":false},"excerpt":{"rendered":"

          See every visit the second it happens \u2014 fast even with millions of views, and stored only in your own database.<\/p>","protected":false},"author":1,"featured_media":11946,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[760,1014,787,762,3142,555],"class_list":["post-11945","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-analytics","tag-page-views","tag-privacy","tag-statistics","tag-utm","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11945","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11945"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11945\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/11946"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11945"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11945"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11945"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}