VAGO ANALYTICS
Vago Analytics compatibility with REEID Translate
Vago Analytics compatibility with REEID Translate is being evaluated from available plugin evidence. Self-hosted analytics storage in a dedicated SQLite database file under `wp-content/uploads/vago-analytics/`, separate from the WordPress (MySQL) database (sessions/events and tracked pageviews/clicks/checkout events). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Vago Analytics.
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
Vago Analytics is documented in the Analytics category with 7 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 Vago Analytics 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
- Self-hosted analytics storage in a dedicated SQLite database file under `wp-content/uploads/vago-analytics/`, separate from the WordPress (MySQL) database (sessions/events and tracked pageviews/clicks/checkout events).
- Tracks analytics events including unique visitors, pageviews, traffic sources with UTM campaign tracking, and a conversion funnel from visit through purchase with step-by-step drop-off and “biggest leak” detection.
- Provides session-level detail with a chronological event trail per visitor, plus path branching and top path patterns for WooCommerce stores (WooCommerce-dependent features).
- Captures on-site search keyword tracking and coupon attempt tracking (success/fail).
- Offers geographic breakdown (country/city) and device/browser breakdown, with datacenter/hosting-IP traffic excluded from reports; geographic lookups use a locally stored MaxMind GeoLite2 City database when a MaxMind license key is configured.
- Frontend/dashboard access via an optional “External Access” friendly URL outside wp-admin, where login uses the normal WordPress login (`wp_signon()`), and access is limited to users with `manage_options` capability.
- Bundled local libraries for charts and GeoLite2 DB reading (no CDN-loaded libraries stated), and outbound network requests limited to downloading/updating the GeoLite2 database from `download.maxmind.com` using the user-provided license key (no visitor IP/tracked data included in that download request).
CONTENT BOUNDARY
Vago Analytics 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
Vago Analytics and REEID Translate FAQ.
What does Vago Analytics do according to the available plugin evidence?
Vago Analytics has 7 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 Vago Analytics?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Vago Analytics?
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 Vago Analytics in a multilingual WordPress workflow.
REEID documents Vago Analytics 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.