Title: VisitorTrail Analytics Author: makitsolutions Published: Juko 31, 2026 Last modified: Juko 31, 2026 --- Search plugins ![](https://ps.w.org/visitortrail-analytics/assets/banner-772x250.png?rev=3675042) ![](https://ps.w.org/visitortrail-analytics/assets/icon-256x256.png?rev=3675042) # VisitorTrail Analytics By [makitsolutions](https://profiles.wordpress.org/makitsolutions/) [Download](https://downloads.wordpress.org/plugin/visitortrail-analytics.1.7.2.zip) * [Details](https://fuc.wordpress.org/plugins/visitortrail-analytics/#description) * [Reviews](https://fuc.wordpress.org/plugins/visitortrail-analytics/#reviews) * [Installation](https://fuc.wordpress.org/plugins/visitortrail-analytics/#installation) * [Development](https://fuc.wordpress.org/plugins/visitortrail-analytics/#developers) [Support](https://wordpress.org/support/plugin/visitortrail-analytics/) ## Description Developed by MAK IT Solutions — https://makitsol.com/ VisitorTrail Analytics helps site owners understand how visitors move through a WordPress website without requiring an external analytics service. It records first-party analytics data in your WordPress database and presents it in an admin dashboard designed around individual visitor journeys, content engagement, traffic campaigns, conversion funnels, and WooCommerce activity. #### Visitor journey analytics VisitorTrail Analytics can record a chronological session journey including: * Entry and exit pages * Referrer information * UTM source, medium, campaign, term, and content parameters * Pages viewed during a session * Time spent on tracked pages * Scroll depth * Configurable link and button clicks * Outbound link clicks * Form submission events without storing submitted field values * WordPress comment events * On-site search queries and result counts * Rage-click and dead-click signals #### Analytics dashboard The dashboard and reports include: * Active visitors based on recent session activity * Sessions and returning visitor segmentation * Average session duration * Bounce rate * Top entry pages * Top exit pages * Top referrers * Device reporting * Individual visitor journey timelines * Content engagement insights * Top site searches * Rage-click reports * UTM campaign reporting * Custom page-based conversion funnels #### WooCommerce analytics When WooCommerce is active and ecommerce tracking is enabled, VisitorTrail Analytics can record: * Product views used by the product report * Add-to-cart events * Remove-from-cart events * Checkout starts * Purchases * Cart abandonment signals * Product conversion metrics * Revenue attributed to tracked sessions WooCommerce is optional. The main visitor and content analytics features work without it. #### Optional cart recovery features Checkout email capture and abandoned-cart reminder emails are disabled by default. If a site administrator enables them, VisitorTrail Analytics can store the email address entered on the WooCommerce checkout page against the tracked session and send one reminder after the cart is considered abandoned. The current recovery email links to the WooCommerce cart page. Guest cart availability still depends on WooCommerce session persistence, so a cart is not guaranteed to be restored on another browser or device. #### Data ownership and privacy controls Analytics data is stored in the site’s own WordPress database. VisitorTrail Analytics does not require an account with an external analytics provider and does not send analytics data to a VisitorTrail service. The plugin includes controls to help site owners configure tracking for their privacy requirements: * Raw IP addresses are not stored. The detected IP is reduced before a one-way salted hash is stored. * A WordPress user ID may be associated with a tracked session when WordPress identifies a logged-in visitor. * Browser Do Not Track can be respected. * Logged-in administrators can be excluded from tracking. * Tracking can be gated behind a consent cookie created by another consent-management plugin. * Raw analytics retention is configurable and older records are removed automatically. * Data can optionally be removed when the plugin is deleted. * Checkout email capture and recovery email features are opt-in and disabled by default. * WordPress personal-data export and erasure tools include VisitorTrail data that can be associated with an email address or WordPress account. * Suggested VisitorTrail disclosure text is added to WordPress Privacy Policy guidance. VisitorTrail Analytics uses first-party cookies to maintain a session identifier and a returning-visitor identifier. Website owners are responsible for determining whether consent or privacy-policy updates are required for their jurisdiction and configuration. ### Developer VisitorTrail Analytics is developed and maintained by MAK IT Solutions. Website: https://makitsol.com/ ## Screenshots [⌊Dashboard overview with sessions, conversion rate, revenue, top entry and exit pages, referrers, and device breakdown.⌉⌊Dashboard overview with sessions, conversion rate, revenue, top entry and exit pages, referrers, and device breakdown.⌉[ Dashboard overview with sessions, conversion rate, revenue, top entry and exit pages, referrers, and device breakdown. [⌊Journeys screen showing individual visitor sessions, entry pages, duration, device, and purchase status.⌉⌊Journeys screen showing individual visitor sessions, entry pages, duration, device, and purchase status.⌉[ Journeys screen showing individual visitor sessions, entry pages, duration, device, and purchase status. [⌊Content Insights report with page views, average time on page, scroll depth, exits, and exit rate.⌉⌊Content Insights report with page views, average time on page, scroll depth, exits, and exit rate.⌉[ Content Insights report with page views, average time on page, scroll depth, exits, and exit rate. [⌊Campaigns report grouping traffic by UTM source, medium, and campaign, with conversions and tracked revenue.⌉⌊Campaigns report grouping traffic by UTM source, medium, and campaign, with conversions and tracked revenue.⌉[ Campaigns report grouping traffic by UTM source, medium, and campaign, with conversions and tracked revenue. [⌊Products report showing product views, add-to-cart performance, purchase counts, conversion rates, and revenue.⌉⌊Products report showing product views, add-to-cart performance, purchase counts, conversion rates, and revenue.⌉[ Products report showing product views, add-to-cart performance, purchase counts, conversion rates, and revenue. [⌊Settings screen for tracking modules, privacy controls, consent-cookie support, and weekly digest options.⌉⌊Settings screen for tracking modules, privacy controls, consent-cookie support, and weekly digest options.⌉[ Settings screen for tracking modules, privacy controls, consent-cookie support, and weekly digest options. ## Installation 1. Upload the `visitortrail-analytics` folder to the `/wp-content/plugins/` directory, or install the plugin ZIP through Plugins > Add New > Upload Plugin. 2. Activate VisitorTrail Analytics through the Plugins screen in WordPress. 3. Open VisitorTrail Analytics > Settings. 4. Review the tracking modules, retention period, Do Not Track option, administrator exclusion, and consent-cookie settings before collecting production analytics. 5. If WooCommerce is installed, choose whether ecommerce tracking should be enabled. 6. Only enable checkout email capture or cart recovery email after reviewing your site’s privacy and consent requirements. VisitorTrail begins collecting new analytics after activation. It does not reconstruct visitor activity that happened before installation. ## FAQ ### Does VisitorTrail Analytics require an external account? No. The analytics reporting in this version is self-hosted and stored in your WordPress database. ### Does the plugin send visitor analytics to a third-party service? No external analytics service is required by the plugin. Tracking events are sent from the visitor’s browser to REST API endpoints on the same WordPress site and are stored in that site’s database. Normal WordPress, hosting, SMTP, payment, WooCommerce, or other plugins on the site may independently communicate with their own services. Those services are outside VisitorTrail Analytics. ### Does it use cookies? Yes. VisitorTrail Analytics uses first-party cookies for session continuity and returning-visitor recognition. By default the tracker uses `visian_session` for the current session and `visian_visitor` for the returning-visitor identifier. A site administrator can configure VisitorTrail Analytics to wait for a consent cookie before tracking begins. ### Does VisitorTrail Analytics store IP addresses? It does not store the raw client IP address. The plugin reduces the address and then creates a one-way HMAC hash using a secret from the WordPress installation before storing the resulting value. ### Does it work without WooCommerce? Yes. Visitor journeys, page engagement, clicks, forms, comments, searches, campaigns, content reports, and funnels can work without WooCommerce. Ecommerce reports and events are only available when WooCommerce is active. ### What form data is recorded? The form tracking module records a form submission event and identifying context for the form/page. It does not intentionally collect the values entered into form fields. ### What happens if I enable checkout email capture? The email address entered on the WooCommerce checkout page can be stored with the visitor session. This option is disabled by default and is intended to support the optional abandoned-cart reminder feature. ### Does the abandoned-cart link restore a guest cart on another device? Not necessarily. The current reminder links to the WooCommerce cart page and relies on WooCommerce cart/session persistence. Cross-device cart reconstruction is not included in this version. ### How long is analytics data kept? The raw-data retention period is configurable in VisitorTrail Analytics > Settings. The default is 90 days. Scheduled cleanup removes older raw records; summarized session records may be retained slightly longer for reporting continuity. ### Can I exclude my own administrator visits? Yes. The setting to exclude logged-in users who can view the VisitorTrail Analytics dashboard is enabled by default. ### Can I use a cookie consent plugin with VisitorTrail Analytics? Yes. In Settings you can enter the name of a consent cookie and, optionally, a required value. Tracking will be blocked until that cookie condition is present. Compatibility depends on the cookie format used by the consent plugin. ### Does VisitorTrail support WordPress personal-data requests? Yes. VisitorTrail registers with WordPress Tools > Export Personal Data and Tools > Erase Personal Data. Data that can be associated with the requested email address or its WordPress user account can be exported or erased. WooCommerce orders themselves are not deleted by VisitorTrail’s eraser; VisitorTrail’s own analytics rows and its session-link metadata are removed. ### Does VisitorTrail add Privacy Policy guidance? Yes. VisitorTrail adds suggested disclosure text to WordPress Settings > Privacy so site owners can adapt it to their own configuration and legal requirements. ### Does uninstalling the plugin delete analytics data? Not by default. There is an option to delete VisitorTrail Analytics tables and settings when the plugin is deleted. Enable that option before deletion if you want the plugin to remove its stored data. ### Who can access the reports? The plugin uses its own `visian_view_analytics` capability for the analytics admin screens. Administrators receive access during plugin activation. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “VisitorTrail Analytics” is open source software. The following people have contributed to this plugin. Contributors * [ makitsolutions ](https://profiles.wordpress.org/makitsolutions/) [Translate “VisitorTrail Analytics” into your language.](https://translate.wordpress.org/projects/wp-plugins/visitortrail-analytics) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/visitortrail-analytics/), check out the [SVN repository](https://plugins.svn.wordpress.org/visitortrail-analytics/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/visitortrail-analytics/) by [RSS](https://plugins.trac.wordpress.org/log/visitortrail-analytics/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.7.2 * Refactored dashboard visitor-segment filtering so dynamic SQL fragments are no longer concatenated into prepared queries. * All segment values are now passed exclusively through wpdb::prepare() placeholders. #### 1.7.1 * Fixed WordPress input-handling warnings for current and legacy session cookies by unslashing and sanitizing them at the point of access. * Documented and scoped the one-time legacy table migration database calls so Plugin Check recognizes the intentional direct schema access. * Updated the WordPress compatibility header to Tested up to 7.1. #### 1.7.0 * Migrated plugin-owned declarations and stored identifiers to the unique `VISIAN_`/` visian_` prefix required by WordPress.org naming-collision guidance. * Added a one-time compatibility migration for legacy `ji_*` options, custom tables, capabilities, scheduled hooks, cookies, and WooCommerce linkage metadata. * Renamed admin CSS selectors and JavaScript globals to use VisitorTrail-specific prefixes. * Preserved existing analytics data during the prefix migration. #### 1.6.0 * Improved WordPress.org Plugin Check compatibility for SQL identifier handling, input/output sanitization, translator notes, and translation loading. * Kept the custom analytics-table architecture and existing reporting behavior intact. #### 1.5.0 * Removed the REST authentication override that could bypass site-wide anonymous REST restrictions. * Kept VisitorTrail ingestion routes intentionally public through route-level permission callbacks for normal anonymous analytics traffic. * Added REST payload-size limits, stricter URL/session validation, rate limiting safeguards, and sensitive event-key filtering. * Prevented click and rage-click tracking from reading values typed into text, email, password, checkout, textarea, select, or contenteditable fields. * Added WordPress personal-data exporter integration for sessions associated with an email address or WordPress account. * Added WordPress personal-data eraser integration for VisitorTrail sessions, pageviews, events, ecommerce analytics rows, and VisitorTrail order-session linkage metadata. * Added suggested Privacy Policy disclosure text through WordPress privacy tools. * Clarified the Settings privacy section and made built-in IP reduction/hashing visibly always-on. * Preserved existing analytics tables, options, reporting, WooCommerce tracking, funnels, and visitor journey behavior. #### 1.4.0 * Redesigned analytics tables with a modern card-based visual system. * Added stronger color hierarchy for engagement, conversion, revenue, and warning metrics. * Improved table headers, row states, filters, responsive scrolling, and report readability. * Refined dashboard panels, KPI cards, badges, and analytics surfaces. #### 1.3.0 * Renamed the plugin to VisitorTrail Analytics. * Updated the proposed WordPress.org slug and text domain to `visitortrail-analytics`. * Reworked the readme for the WordPress.org Plugin Directory format. * Expanded installation, FAQ, privacy, data-storage, cookie, and WooCommerce documentation. * Preserved existing analytics data and functionality through the product rename. #### 1.2.0 * Refreshed the admin interface across dashboards, journeys, reports, funnels, and settings. * Improved responsive KPI cards, panels, tables, badges, filters, timeline, forms, and pagination. #### 1.1.0 * Added UTM campaign reporting and WooCommerce product reports. * Added new-versus-returning visitor segmentation, weekly digest emails, site-search reporting, active visitor count, and rage-click detection. * Added opt-in checkout email capture and abandoned-cart reminder email support. #### 1.0.0 * Initial release. ## Meta * Version **1.7.2** * Last updated **19 hours ago** * Active installations **Fewer than 10** * WordPress version ** 5.8 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/visitortrail-analytics/) * Tags * [analytics](https://fuc.wordpress.org/plugins/tags/analytics/)[conversion](https://fuc.wordpress.org/plugins/tags/conversion/) [tracking](https://fuc.wordpress.org/plugins/tags/tracking/)[web analytics](https://fuc.wordpress.org/plugins/tags/web-analytics/) [woocommerce](https://fuc.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://fuc.wordpress.org/plugins/visitortrail-analytics/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/visitortrail-analytics/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/visitortrail-analytics/reviews/) ## Contributors * [ makitsolutions ](https://profiles.wordpress.org/makitsolutions/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/visitortrail-analytics/)