VISITOR VISUAL
Visitor Visual compatibility with REEID Translate
Visitor Visual compatibility with REEID Translate is being evaluated from available plugin evidence. Adds a Visitor Visual tracker script to every page of the WordPress site (via theme-file-free injection). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Visitor Visual.
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
Visitor Visual is documented in the Analytics category with 8 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 Visitor Visual 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
- Adds a Visitor Visual tracker script to every page of the WordPress site (via theme-file-free injection).
- Requires a Visitor Visual account and a user-provided Tracking ID that is pasted into the plugin’s WordPress settings page.
- Enqueues the tracker script on every request using `wp_enqueue_scripts`, intended to work alongside standard page-caching plugins.
- Loads the tracker script asynchronously using `async defer` so it does not block page rendering.
- Provides frontend analytics capabilities including detection of VIP visitors and returning visitors.
- Supports purchase/conversion celebration behavior by enabling a user to add one line to a checkout confirmation page (implying purchase event tracking integration at checkout confirmation).
- Includes GDPR-related controls described as IP anonymization and one-click visitor data deletion.
- (Exact implementation details are not provided in the supplied evidence.)
CONTENT BOUNDARY
Visitor Visual 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
Visitor Visual and REEID Translate FAQ.
What does Visitor Visual do according to the available plugin evidence?
Visitor Visual has 8 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 Visitor Visual?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Visitor Visual?
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 Visitor Visual in a multilingual WordPress workflow.
REEID documents Visitor Visual 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.