VisitorTrail Analytics compatibility with REEID Translate

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.