
WEBDIG.DEV ANALYTICS
WebDig.DEV Analytics compatibility with REEID Translate
WebDig.DEV Analytics compatibility with REEID Translate is being reviewed using official plugin documentation. Integrates with self-hosted Umami servers (v3.2+) to display visits, page views, and bounce rates via a dedicated dashboard widget and reports page. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What WebDig.DEV 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
WebDig.DEV 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 WebDig.DEV 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
- Integrates with self-hosted Umami servers (v3.2+) to display visits, page views, and bounce rates via a dedicated dashboard widget and reports page.
- Collects Core Web Vitals metrics (LCP, INP, CLS, FCP, TTFB) using official Umami real-user monitoring, displaying performance ratings within WordPress.
- Tracks WooCommerce events including product views, cart actions, checkouts, and purchases, with support for HPOS and server-side purchase tracking to bypass ad blockers.
- Automatically records page views and configurable user interactions such as link clicks, button presses, downloads, form submissions, and scroll milestones.
- Provides campaign attribution by preserving UTM parameters and ad click IDs while stripping non-essential query parameters and order keys from tracked URLs.
- Supports consent management integration with WP Consent API, Complianz, CookieYes, and Cookiebot, allowing optional gating of tracker loading based on user consent status.
- Enforces staging protection by restricting data collection to configured production domains and environments, preventing test sites from sending analytics data.
TRANSLATION BOUNDARY
WebDig.DEV 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
WebDig.DEV Analytics and REEID Translate FAQ.
What does WebDig.DEV Analytics do?
WebDig.DEV Analytics has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does WebDig.DEV 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 WebDig.DEV 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 WebDig.DEV Analytics in a multilingual WordPress workflow.
REEID documents WebDig.DEV 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.