VISITORTRAIL ANALYTICS
VisitorTrail Analytics translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what VisitorTrail Analytics does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
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.
Distinctive features
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.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what VisitorTrail Analytics does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
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.
Does the current evidence establish translation scope for VisitorTrail Analytics?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.