VISITORTRAIL ANALYTICS
VisitorTrail Analytics compatibility with REEID Translate
VisitorTrail Analytics compatibility with REEID Translate is being evaluated from available plugin evidence. Self-hosted visitor journey analytics stored in the site’s own WordPress database (no external analytics account/service required). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for VisitorTrail 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
VisitorTrail Analytics 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 VisitorTrail 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 visitor journey analytics stored in the site’s own WordPress database (no external analytics account/service required).
- Browser-to-site event collection via REST API endpoints on the same WordPress site; events are stored in the site database.
- First-party cookie usage for session continuity and returning-visitor identification (default cookie names: `visian_session` and `visian_visitor`), with optional gating until a consent cookie condition is met.
- Privacy controls for IP handling (does not store raw IP; stores a reduced IP value as a one-way salted/HMAC hash) and optional exclusion of logged-in administrators from tracking.
- Configurable tracking modules covering session journey and engagement signals (entry/exit pages, referrers, UTM parameters, pages viewed, time on tracked pages, scroll depth, link/button clicks, outbound link clicks, form submission events without storing submitted field values, comment events, on-site search queries/result counts, rage-click and dead-click signals).
- Optional WooCommerce ecommerce tracking when WooCommerce is active and ecommerce tracking is enabled (product views, add-to-cart/remove-from-cart, checkout starts, purchases, cart abandonment signals, conversion metrics, and revenue attributed to tracked sessions).
- Optional, opt-in WooCommerce checkout email capture and abandoned-cart reminder email functionality (disabled by default); can store the checkout email against the tracked session and send one reminder after abandonment, with reminder links to the WooCommerce cart page.
- WordPress privacy/data tooling integration: supports WordPress personal-data export/erasure for VisitorTrail data and adds suggested disclosure text to WordPress Privacy Policy guidance; includes configurable raw-data retention with scheduled cleanup and an option to delete plugin data on uninstall.
CONTENT BOUNDARY
VisitorTrail 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
VisitorTrail Analytics and REEID Translate FAQ.
What does VisitorTrail Analytics do according to the available plugin evidence?
VisitorTrail Analytics 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 VisitorTrail 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 VisitorTrail 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 VisitorTrail Analytics in a multilingual WordPress workflow.
REEID documents VisitorTrail 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.