
KITESTRING ANALYTICS FOR UMAMI
Kitestring Analytics for Umami compatibility with REEID Translate
Kitestring Analytics for Umami compatibility with REEID Translate is being reviewed using official plugin documentation. Injects the configured Umami tracking script into public WordPress pages, with tracking disabled by default until a Script URL and Website ID are provided. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Kitestring Analytics for Umami 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
Kitestring Analytics for Umami 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 Kitestring Analytics for Umami 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 the configured Umami tracking script into public WordPress pages, with tracking disabled by default until a Script URL and Website ID are provided.
- Supports all Umami v3.4 tracker attributes, including performance monitoring, distinct visitor IDs, fetch credentials control, and separate automatic pageview management.
- Provides optional dashboard integration displaying aggregate statistics (pageviews, visitors, bounces) via self-hosted username/password or Umami Cloud API key authentication.
- Enables opt-in loading of recorder.js for heatmaps and session replay, allowing configuration of custom recorder URLs and collection host overrides.
- Facilitates native custom events, revenue tracking, and pseudonymous identity data using official Umami tracker APIs such as umami.track() and umami.identify().
- Offers WordPress filters (kitestring_umami_tracker_attributes, kitestring_umami_tracking_allowed, kitestring_umami_recorder_enabled) to dynamically modify data attributes or gate script emission per page.
TRANSLATION BOUNDARY
Kitestring Analytics for Umami 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
Kitestring Analytics for Umami and REEID Translate FAQ.
What does Kitestring Analytics for Umami do?
Kitestring Analytics for Umami has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Kitestring Analytics for Umami 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 Kitestring Analytics for Umami?
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 Kitestring Analytics for Umami in a multilingual WordPress workflow.
REEID documents Kitestring Analytics for Umami 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.