內容簡介
Omea Analytics 是一款專為快速 WordPress 網站設計的簡約分析外掛，提供隱私優先的追蹤功能，無需儲存 IP 位址或持久的跨會話識別碼。它能追蹤頁面瀏覽量、互動、引薦來源、UTM 活動及轉換，並透過 REST API 提供快速報告。
【主要功能】
• 隱私優先的無餅乾追蹤
• 伺服器端會話歸因及短期第一方餅乾選項
• 追蹤頁面瀏覽量、互動時間及滾動深度
• 每日聚合以快速查詢控制台
• 轉換及事件追蹤（客戶端 + 可選伺服器端鉤子）
• 設備分類於粗略隱私安全層級
外掛標籤
開發者團隊
原文外掛簡介
Omea Analytics measures your WordPress site without sending anything to third parties – the data stays in your own database. Without consent it is cookieless (the same approach as Matomo’s cookieless mode); with a visitor’s Statistics consent it also recognises returning visitors and credits conversions to the campaign that first brought them.
It is built to be the fastest analytics plugin for WordPress: a 1.8 KB tracker (gzip) that sends two requests per page, a collector that stores hits without loading WordPress, and reports read from daily rollups – a 30-day dashboard on a busy site loads in milliseconds, and history stays exact after visit-level data is deleted.
What you get
Visits, visitors, pageviews, bounce and engagement rate, time on page and scroll depth, in your site’s time zone.
Channels aligned with GA4 – including AI Assistants (ChatGPT, Perplexity, Gemini, Copilot, Claude) – plus source, medium, campaign, term and content, referring domains and ad click IDs (Google, Microsoft, Meta, TikTok, LinkedIn, X).
Entry and exit pages, page detail with where visitors came from and went next.
Goals and conversions from page visits, clicks, forms and custom events (omea.trackEvent(), data-omea-event), with conversion rate and revenue per goal and channel. WooCommerce purchases, checkouts and add-to-carts are recorded on the server – a purchase counts even when the buyer never returns to the thank-you page.
Countries, regions and cities from a local database on your server; browsers, operating systems (including Windows 11) and screen sizes.
New vs returning visitors and visit frequency for visitors who gave Statistics consent.
Bot traffic filtered before anything is stored – crawlers, scripts, automated browsers and vulnerability scanners – with a counter of what was filtered.
Automatic outbound-link, download, email/phone-click and site-search tracking, pages not found (404), and Content reports by author, category and post type.
AI crawlers: how often GPTBot, ClaudeBot, PerplexityBot and others fetch your pages – next to the visits AI assistants send you.
Core Web Vitals from real visitors (sampled): LCP, INP, CLS and TTFB per page.
Import your history from Koko Analytics, WP Statistics, Burst Statistics, Independent Analytics, Statify, Slimstat, Jetpack Stats, Plausible or Google Analytics 4.
CSV export of every report, chart notes, saved segments, a weekly email report, a dashboard widget, a Views column, a Popular posts block, WP-CLI, a read-only Reporting API (Google Sheets, Looker Studio) and MCP abilities for AI assistants.
View-only access for the roles you choose; multisite network overview.
A “Get set up” checklist that tells you when something needs attention: geolocation database, tracking, collector, visitor IP behind a CDN, consent setup, conversions, privacy policy.
Privacy
Without consent (default): cookieless. Nothing is stored in the browser – no cookies, no localStorage. The tracker reads a few values in the browser (screen-width bucket, touch support, referrer, scroll depth and active time) and sends them to your own server. A visit is recognised on your server by a one-way hash of the IP address (the /64 network for IPv6), browser, language and site under a random key that is replaced every day; the old key is deleted half an hour after midnight, after which visits can’t be linked across days or matched to an IP address. Omea Analytics never stores the IP address. Whether this needs consent depends on your country: some regulators, such as France’s CNIL and Spain’s AEPD, exempt audience measurement from consent when strict conditions are met (your own site only, aggregated statistics, nothing combined with other data); others, such as Germany’s and Finland’s, generally expect consent. Omea Analytics is designed with those conditions in mind, but no regulator has approved it – check your country’s rules.
You choose what a “no” stops (Settings › Privacy): count every visit cookieless (default – also after a visitor rejects Statistics), stop counting a visitor who rejects Statistics (the rejection works as an objection, as the UK statistics exception requires), or record nothing before Statistics consent. Both stricter modes are enforced on the server too. Optionally, IPv4 addresses are shortened (last part dropped) before hashing.
With Statistics consent: returning visitors. When a visitor explicitly accepts Statistics in Omea Consent or a plugin that uses the WordPress Consent API, the server sets a first-party HttpOnly cookie omea_vid holding a random ID (13 months by default; 1–25 months, or turn it off). Only a keyed hash of that ID is stored. Withdrawing consent removes the cookie.
What is stored: page path (no query string), referrer host and path, UTM parameters, the type of ad click ID (never its value), coarse device type, OS and browser family, screen-size bucket, ISO country code, region and city. No IP addresses, no coordinates. Server-side events (purchases, sign-ups) store no user, order or contact IDs in the analytics tables. With WooCommerce, each order stores the ID of the visit it came from (order meta _omea_analytics_session), so an order can be connected to that visit’s pages and source – or, with “Link orders only with Statistics consent”, only for buyers who allowed Statistics.
Retention: visit-level hits are deleted after 30 days and visits after 395 days by default (both configurable); daily reports without visitor data are kept.
External services
Omea Analytics makes no external requests while it measures – visits are recognised on your server, and locations come from a local database file or your host’s/CDN’s headers.
DB-IP City Lite (default geolocation) – After activation, when you select DB-IP, and once a month when a new release is published, the plugin downloads the free DB-IP City Lite database from https://download.db-ip.com/free/ via WP-Cron. Only the download request is made: no visitor data and no site address is sent. Lookups then run locally. The file is stored in a private, randomly named folder in uploads. Choose “Proxy / CDN headers only” in Settings › Geolocation to avoid this. IP geolocation by DB-IP (https://db-ip.com), licensed under CC BY 4.0.
MaxMind GeoLite2 / GeoIP2 (optional) – Only when selected and your own MaxMind account ID and licence key are entered: the database is downloaded from https://download.maxmind.com/ and refreshed weekly. MaxMind’s licence requires using a release no older than 30 days, so a copy that cannot be updated for 30 days is removed. Terms: https://www.maxmind.com/en/geolite2/eula
Jetpack Stats import (optional) – Only when an administrator starts an import from Jetpack Stats on a site connected to WordPress.com: the plugin asks WordPress.com, through Jetpack’s own connection, for that site’s daily views, visitors, top posts, referrers and countries. Nothing else is sent. WordPress.com terms: https://wordpress.com/tos/ – privacy: https://automattic.com/privacy/
Upgrade to Pro checkout (optional) – The “Upgrade to Pro” admin page and the dashboard’s Pro card offer the paid Omea Analytics Pro add-on (or the Omea Pro bundle). Clicking “Start free trial” opens a window (or, as a fallback, a new tab) with the checkout page at account.cultmetrics.com (operated by Cultmetrics Oy), where payment is handled by Stripe. The page receives the site’s domain, the admin address it was opened from and the plugin version, so it can show the new license key in that window. Nothing is loaded or sent until an administrator clicks the button; card details are entered only in Stripe’s fields, never inside WordPress. Hide the upsell with the omea_analytics_show_pro_upsell filter. Cultmetrics terms of sale: https://www.cultmetrics.com/terms/ – privacy: https://www.cultmetrics.com/privacy-policy/ – Stripe terms: https://stripe.com/legal – Stripe privacy: https://stripe.com/privacy
Files the plugin writes
omea-analytics-collect.php in the site root – a few lines that pass tracker hits to the plugin’s collector without loading WordPress (the same approach as other fast analytics plugins). It is removed when the plugin is deactivated. If the site root isn’t writable, or on multisite, hits go to the plugin’s REST endpoint instead. Define OMEA_ANALYTICS_NO_COLLECTOR to turn it off.
wp-content/omea-analytics/ – the collector’s settings and a short-lived buffer of hits (stored into the database every minute), in randomly named files that deny web access.
wp-content/uploads/omea-analytics/ – the geolocation database.
