
SERVIT ANALYTICS
SERVIT Analytics compatibility with REEID Translate
SERVIT Analytics compatibility with REEID Translate is being reviewed using official plugin documentation. Server-side, cookieless visitor tracking that stores session IDs in browser sessionStorage and uses daily-rotating SHA-1 hashes for unique visitor identification without storing IP addresses. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What SERVIT 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
SERVIT Analytics is documented in the Analytics category with 6 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 SERVIT 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
- Server-side, cookieless visitor tracking that stores session IDs in browser sessionStorage and uses daily-rotating SHA-1 hashes for unique visitor identification without storing IP addresses.
- Local data processing with no external API calls or CDN dependencies; all analytics data is stored in custom WordPress database tables and charts are rendered as inline SVG.
- Automatic conversion tracking integrations for WooCommerce, Easy Digital Downloads, Fluent Forms, and FluentBooking via PHP hooks that activate only when the respective plugins are installed.
- Campaign attribution using UTM parameters and click IDs (gclid, fbclid, etc.) stored in localStorage to track ad spend, calculate ROAS/CPA, and separate paid traffic sources from organic ones.
- Dashboard visualization of visitor flow via Sankey diagrams, traffic sources, device breakdowns, and KPI tiles for sessions, pageviews, bounce rates, and live online visitors.
- Migration tool for importing historical data from Statify, mapping dates, paths, and referrers while preserving source and page type information despite Statify's lack of session/device data.
TRANSLATION BOUNDARY
SERVIT 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
SERVIT Analytics and REEID Translate FAQ.
What does SERVIT Analytics do?
SERVIT Analytics has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does SERVIT 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 SERVIT 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 SERVIT Analytics in a multilingual WordPress workflow.
REEID documents SERVIT 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.