ICTWorld24

We've just added Visitor Traffic Real Time Statistics to our product lineup — free to download.

Real-time visitor tracking, geolocation, browser/search-engine breakdown, referrers, top p

What it does

EXTERNAL SERVICES This plugin connects to a third-party service to provide visitor geolocation (country/region/city). You can pick which one under *Traffic Stats → Settings → Geolocation provider*: freeipapi.com: [https://freeipapi.com/](https://freeipapi.com/) — [Terms of Use](https://freeipapi.com/terms) / [Privacy Policy](https://freeipapi.com/privacy) ip-api.com: [https://ip-api.com/](https://ip-api.com/) — [Terms of Service](https://ip-api.com/docs/legal) / [Privacy Policy](https://ip-api.com/docs/legal)

This lookup happens automatically as part of the plugin's core tracking feature and cannot be turned off without disabling geolocation entirely. Because visitor IP addresses leave your server either way, mention whichever provider you have selected in your site's own privacy policy. The "Anonymize IP" setting (Settings → Privacy) masks the stored IP address in your own database but does not change what is sent to the geolocation provider for the lookup itself.

FEATURES Free: returning, bounce rate, average session duration cookie) until the visitor has consented, auto-detected from Complianz or CookieYes, or your own consent tool via a filter

Pro (locked behind vtrs_is_pro() — wire up your own licensing/payments):

NOTES FOR DEVELOPERS key, HTTPS, rate limited) with ip-api.com selectable as a legacy alternative — see "External services" above — and caches each IP's result for 7 days via transients. Swap in a MaxMind GeoLite2 local database by adding a case to VTRS_Geo::lookup(). Because the visitor's IP is sent to whichever third-party endpoint is selected, mention it in your site's own privacy policy. tell VTRS the answer yourself (return true/false; returning null, the default, falls through to the built-in Complianz/ CookieYes detection): add_filter( 'vtrs_has_consent', fn() => my_plugin_has_analytics_consent() ); of its own about licensing — it returns false unless something hooks the filter and says otherwise. The **Visitor Traffic Stats Pro** add-on (separate plugin, sold/activated independently) is what actually hooks it: it owns license-key storage/validation and returns true once a site has a valid, active license. This plugin never needs to know how licensing works — it only asks "am I unlocked?" via the filter. Point a license-checking plugin at your own backend (a self-hosted REST endpoint, EDD Software Licensing, Freemius, etc.) and it will "just work" here. never wp_send_json_success() / never echo the *unlocked* rows into a page's HTML (even visually hidden) unless the current request is actually Pro — query with a free-tier row cap instead of fetching everything and hiding the extra rows with CSS. created via dbDelta() on activation. {prefix}vtrs_daily_stats holds one pre-aggregated (visitors, visits) row per completed calendar day — see VTRS_DB::aggregate_day() / catch_up_daily_stats() — and is rebuildable at any time by truncating it and letting the daily cron (or VTRS_DB::catch_up_daily_stats()) repopulate it from raw history. tables if you define VTRS_REMOVE_DATA_ON_UNINSTALL as true in wp-config.php first.

Details

View product details →

Download the plugin (.zip) ↓

Leave a Reply

Your email address will not be published. Required fields are marked *