Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce

Ask me! is a question-first dashboard. Instead of learning which report answers which question, you pick a question in plain language and Statnive shows the answer inline with the same date range you set everywhere else. It ships with 120 questions across 10 categories (Traffic, Real-time, Pages, Referrers, Campaigns, Geography, Devices, Engagement, Revenue, Events) and lets you pin your favourite 10 to the home tab so the answers load the moment you open Statnive. Common starter questions include How much traffic this week?, Where is my traffic coming from?, Which pages get the most views?, What countries are my visitors from?, Is my traffic mobile or desktop?, How many people are on my site right now?, Is my tracking working?

No. The 120 questions are pre-built and live entirely inside the plugin. Each question maps to a SQL query that runs locally against your WordPress database, exactly the same SQL the dedicated reports use. There is no AI, no LLM, no chat API, and nothing about your traffic ever leaves your server.

No. Statnive is 100% cookie-free. Visitor identification is a daily-rotating salted hash that cannot be used to track individuals across days or sites.

Statnive is designed to support GDPR, CCPA, APPI, and PIPL compliance: no cookies, no PII storage, daily rotating hashes, configurable retention, WordPress Privacy API export/erase, and server-side respect for GPC and DNT signals. Final compliance always depends on your configuration and your privacy policy.

A salted SHA-256 hash of the visitor's anonymized IP plus User-Agent. The salt rotates daily, so the same visitor gets a different hash tomorrow — cross-day stitching is impossible while daily uniques stay accurate.

In your WordPress database, in tables prefixed statnive_. Nothing leaves your server unless you explicitly enable the optional MaxMind or DB-IP GeoIP downloads (one-time database files, never visitor data). When you uninstall the plugin, all tables and uploaded GeoIP files are removed.

Yes — Statnive ships a full WooCommerce Revenue Report. Net revenue, orders, AOV, refund rate, revenue by channel (UTM + referrer + AI assistants), top products, and the cart → checkout → purchase funnel — all inside WordPress, on the Statnive → Revenue Report page. The Revenue Report is read-only against WooCommerce (the Recorder only ever calls $order->get_*() getters; it never writes to a WooCommerce table or order meta) and is compatible with HPOS and Block Checkout. If you install Statnive on a store that already has orders, the historical data is imported automatically in the background via Action Scheduler. No CLI required, but wp statnive wc-backfill is available if you prefer to drive it manually.

The tracker script is small (~2 KB gzipped) and loads asynchronously, so it does not block your page render. The hit endpoint writes a single row per pageview. Dashboard queries run against pre-aggregated daily summaries rather than raw events.

Yes. Statnive is fully independent. Many users run Statnive as their primary privacy-friendly analytics and keep GA4 for advertising attribution.

Common causes: ad blockers, aggressive page caching, CSP rules blocking fetch/sendBeacon (allow connect-src 'self'), GPC or DNT enabled, or DISABLE_WP_CRON without a system cron. Exclude /wp-json/statnive/v1/hit and admin-ajax.php?action=statnive_hit from page caches.

Four tiers, falling through automatically: (1) browser timezone → country, ~80% accurate, no external call; (2) CDN country headers (Cloudflare, CloudFront, Vercel) when present; (3) optional one-click DB-IP IP-to-City Lite (free, CC-BY 4.0); (4) optional MaxMind GeoLite2 (free with an account). Tiers 3 and 4 are opt-in via a discrete user click.

No. ~200 server-side bot UA patterns and tracker-side fingerprints (webdriver, automation flags) bucket bots separately, so "Visitors" and "Pageviews" reflect humans only.