MYVITALASSISTANT
MyVitalAssistant compatibility with REEID Translate
MyVitalAssistant compatibility with REEID Translate is being evaluated from available plugin evidence. Requires explicit account connection and remains inert until the MyVitalAssistant account is linked in the plugin settings. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for MyVitalAssistant.
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
MyVitalAssistant 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 MyVitalAssistant 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
- Requires explicit account connection and remains inert until the MyVitalAssistant account is linked in the plugin settings.
- Implements first-party tracking via a site-local path (/vt/) that forwards to the MyVitalAssistant collector, intended to keep the attribution cookie on the site’s own domain.
- On page load, sends visitor tracking beacons including page URL, referrer, ad click identifiers and UTM parameters, plus an anonymous visitor id, through the /vt/ path to the collector.
- Captures and forwards attribution with form submissions for multiple supported form plugins (e.g., Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms, Formidable, Elementor Pro, Keap Opt-in Forms), sending submitted email/name/phone together with the visitor’s attribution cookie.
- Optionally syncs WooCommerce order events (paid orders, status changes, refunds) to the MyVitalAssistant service when an order sync key is provided; otherwise order syncing is off.
- Provides a daily “heartbeat” to the collector including account id, plugin version, and WordPress version; when WooCommerce is present, it also sends WooCommerce version/store currency and active commerce/CRM plugin identifiers for dashboard warnings.
- Supports placing MyVitalAssistant forms via block editor or shortcode; the form script is loaded from the collector and submitted visitor input is sent to the collector (with the form stored by the service rather than on the site).
CONTENT BOUNDARY
MyVitalAssistant 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
MyVitalAssistant and REEID Translate FAQ.
What does MyVitalAssistant do according to the available plugin evidence?
MyVitalAssistant 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 MyVitalAssistant?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for MyVitalAssistant?
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 MyVitalAssistant in a multilingual WordPress workflow.
REEID documents MyVitalAssistant 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.