STATNIVE
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce compatibility with REEID Translate
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Cookieless, privacy-first analytics with all analytics/revenue data stored locally in the WordPress database (tables prefixed `statnive_`), with no visitor data sent to third-party trackers. No specific visitor-facing translation surface is currently confirmed.
Visit Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce ↗
AWAITING VERIFICATION
What the available evidence establishes for Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce is documented in the Analytics category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Cookieless, privacy-first analytics with all analytics/revenue data stored locally in the WordPress database (tables prefixed `statnive_`), with no visitor data sent to third-party trackers.
- Visitor identification via a daily-rotating salted SHA-256 hash of anonymized IP plus User-Agent; cross-day stitching is prevented by daily salt rotation.
- WooCommerce Revenue Report that is read-only against WooCommerce order data (uses `$order->get_*()` getters, does not write to WooCommerce tables or order meta), including net revenue, orders, AOV, refund rate, revenue by channel, top products, and a cart→checkout→purchase funnel with drop-off rates; compatible with HPOS and Block Checkout.
- Automatic backfill/import of existing WooCommerce orders into Statnive in the background when the Revenue Report is opened, using Action Scheduler (with an optional WP-CLI command `wp statnive wc-backfill`).
- Real-time analytics capabilities including active visitor count, active pages, and a live pageview feed.
- Custom events and engagement tracking including link clicks (and tagged button clicks via `statnive-event-*` classes), form submissions, downloads, outbound links, time on page, and scroll depth.
- Bot vs human separation using server-side bot UA patterns and tracker-side automation fingerprints, with bots bucketed separately from human visitors.
- Optional geography enrichment via user-enabled GeoIP downloads: MaxMind GeoLite2-City (requires user-provided license key; downloads `GeoLite2-City.mmdb`) and DB-IP IP-to-City Lite (one-shot enable; downloads `dbip-city-lite-YYYY-MM.mmdb.gz`), with no visitor data transmitted to these services.
CONTENT BOUNDARY
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce and REEID Translate FAQ.
What does Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce do according to the available plugin evidence?
Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce in a multilingual WordPress workflow.
REEID documents Statnive – Privacy-first Analytics + Revenue Reports for WooCommerce functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.