
STATABLE ANALYTICS
Statable Analytics compatibility with REEID Translate
Statable Analytics compatibility with REEID Translate is being reviewed using official plugin documentation. Injects a lightweight (~2 KB), deferred tracking script on the frontend to collect pageview and engagement events without setting cookies. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Statable Analytics does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Statable Analytics is documented in the Analytics category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Statable Analytics compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Injects a lightweight (~2 KB), deferred tracking script on the frontend to collect pageview and engagement events without setting cookies.
- Uses pseudonymous visitor identification by hashing IP address and user-agent with a server-side secret that rotates daily, ensuring no persistent identifiers are stored.
- Provides native wp-admin statistics dashboards displaying visitors, pageviews, bounce rate, top pages, sources, countries, devices, custom events, goals, properties, and funnels via API queries.
- Excludes logged-in administrators from tracking by default and allows configuration to exclude additional WordPress user roles.
- Supports public display widgets (visitor map, 3D globe, live counter) inserted via Gutenberg blocks or shortcodes, which fetch aggregated statistics from Statable APIs.
- Includes compatibility markers for caching and optimization plugins (WP Rocket, SiteGround Optimizer, Autoptimize, Cloudflare Rocket Loader, WP Meteor) to prevent script minification or deferral issues.
- Honors Do Not Track and Global Privacy Control signals automatically and provides a shortcode-based opt-out mechanism for visitors.
TRANSLATION BOUNDARY
Statable Analytics capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Statable Analytics and REEID Translate FAQ.
What does Statable Analytics do?
Statable Analytics has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Statable Analytics have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Statable Analytics?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Statable Analytics in a multilingual WordPress workflow.
REEID documents Statable Analytics functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.