Codersly Visitor Tracker

By Codersly

10+ active installationsVersion 1.1.3

Privacy-aware visitor tracking with local visitor logs, referrer details, and human/bot classification.

Description

Codersly Visitor Tracker records visitor activity in a dedicated table in your WordPress database and displays the information inside the WordPress admin area.

The WordPress.org plugin is free and fully functional. No functionality implemented by this package requires a license key, payment, trial period, quota, time limit, or upgrade.

Free features

  • Visitor dashboard with online, daily, 7-day, 30-day, 90-day, total, human, and bot counters.
  • Clean, responsive visitor list with human-readable visitor, location, activity, device, source and page columns.
  • Page title/path, referrer, browser, approximate location, masked IP details, and visit-time records.
  • Human, suspected bot, verified bot, and unknown traffic classification.
  • Exclusion of selected logged-in WordPress user roles.
  • Local storage of visitor records in the site’s WordPress database.
  • Optional approximate city/country lookup through documented external GeoIP providers.

Separate add-on information

The admin navigation contains informational placeholders for Analytics, Live Visitors, Campaigns, Reports, and Clear Data. The Visitors and Settings screens also describe advanced filters and bot-record suppression available through the separately distributed Pro add-on.

These placeholders contain no Pro feature implementation, license validation, disabled local functionality, trial code, quotas, or time limits. When the separate add-on is installed, it replaces the informational callbacks and supplies its own functionality.

Privacy

This plugin can store visitor information in the site’s WordPress database. Depending on settings and request data, records may include:

  • IP address
  • User agent and browser name
  • Page path and landing page
  • Referrer information
  • Visit date and time
  • Logged-in WordPress user ID, username and display name
  • Human/bot classification details
  • Approximate city and country when GeoIP lookup is enabled

The plugin does not send visitor analytics data to Codersly.

Approximate location lookup is enabled in this build so visitor city/country can be filled in automatically. A site administrator can disable it at any time. When enabled, a visitor IP address may be sent in the background to one of the documented GeoIP providers. Site owners are responsible for providing appropriate privacy notices and obtaining any consent required by applicable law.

External services

This plugin can optionally connect to external GeoIP services to obtain approximate visitor location data from an IP address. The feature is enabled in this build and can be disabled by the site administrator under Visitors Tracker → Settings.

Supported providers:

  • ipwho.is — API: https://ipwhois.io/documentation — Terms: https://ipwhois.io/terms — Privacy: https://ipwhois.io/privacy
  • ipapi.co — API: https://ipapi.co/api/ — Terms: https://ipapi.co/terms/ — Privacy: https://ipapi.co/privacy/
  • DB-IP — API: https://db-ip.com/api/doc.php — Terms: https://db-ip.com/tos.php — Privacy: https://db-ip.com/privacy.php

IPWhois is used by default. The ipapi.co and DB-IP integrations can use HTTPS credentials configured with the vtrt/geo/ipapico_key and vtrt/geo/dbip_key filters. Enabled services receive only the public IP address for this lookup and may return country, region, city and timezone. GeoIP is paused when IP anonymization is enabled. Results are cached locally to reduce requests. The lookup runs through WordPress Cron, with up to 200 uncached IP lookups per UTC day by default. Pro’s IPGeolocation.io lookups use the provider plan’s quota separately.

Installation

  1. Upload the plugin to /wp-content/plugins/codersly-visitor-tracker/, or install it through the WordPress Plugins screen.
  2. Activate Codersly Visitor Tracker.
  3. Open Visitors Tracker → Dashboard.
  4. Review privacy and tracking options under Visitors Tracker → Settings.

FAQ

Is every implemented feature in this package free?

Yes. The plugin’s tracking features work without a plugin license, payment or upgrade. Optional third-party services have their own account requirements and limits.

Why are Pro-labelled pages visible?

They are informational navigation placeholders. They contain no Pro implementation or disabled built-in controls. Installing the separately distributed add-on replaces those callbacks with the add-on’s pages.

Where are visitor records stored?

Visitor records are stored locally in a dedicated table in the site’s WordPress database.

Does the plugin send analytics data to Codersly?

No. It does not send visitor analytics data to Codersly. Optional GeoIP lookup can contact the selected provider when the administrator enables that setting.

Is approximate location lookup enabled by default?

Yes, in this build it is enabled so the Location column can populate automatically. It can be turned off under Visitors Tracker → Settings.

Are exclusions kept when reinstalling the plugin?

Deleting the plugin through WordPress keeps the excluded IP addresses, excluded user roles, trusted proxy settings and visitor records for a reinstall. For an intentional data purge, define VTRT_DROP_TABLES_ON_UNINSTALL as true or set vtrt_drop_on_uninstall before deleting the Free plugin.

Screenshots

Changelog

1.1.3

  • Validate, unslash and sanitize the bot-review screen and request-method inputs before use, addressing the four reported Plugin Check input warnings.
  • Recognize anonymous direct desktop visits to product-tag/product-category archives across the bundled hosting networks, including rotated IPv4/IPv6 addresses, custom WooCommerce taxonomy slugs and plain permalinks. Matching visits are suspected bots, not DNS-verified crawlers; country alone is never used.
  • Add Visitors > Recheck bot labels to review existing records in resumable batches of 100, retaining all records. Login, mobile, referral and paid-context safeguards apply to the stored visit, not the reviewing administrator. No GeoIP API calls are needed.
  • Reuse a complete city result for the same IP and location source from a separate location cache.
  • Keep IP and user-role exclusions and trusted proxy settings when the plugin is deleted and reinstalled.
  • Sanitize request paths and referrers while retaining percent-encoded values.
  • Resolve IPv4 and IPv6 through recognized Cloudflare edge ranges or configured trusted proxies.
  • Preserve usable city estimates and retry missing cities in recent records. Conflicting city estimates require a majority among available city results.
  • Separate the observed referrer URL from inferred campaign and app sources. Preserve encoded paths and query parameters.
  • Classify named crawlers and browser automation consistently and improve rapid sequential scan checks.
  • Allow multiple server-tracked bot visits under the unique page-view index.

1.1.2

  • Version aligned with Codersly Visitor Tracker Pro 1.1.2. No functional changes.

1.1.1

  • Fixed visitors from Meta/Facebook ads not being recorded when the landing URL (long fbclid + UTM parameters) exceeded 255 characters and the database insert failed.
  • Widened the path, landing_page and current_page columns to 2048 characters (automatic upgrade).
  • Added safe per-column truncation and a fallback retry so a long value can never drop a visitor again.

1.1.0

  • Added logged-in WordPress user ID, username and display-name association for visitor records.
  • Added anonymous-to-registered visitor/session identity merging after login.
  • Added REST cookie authentication support so logged-in users are recognized by the browser beacon.
  • Added cached background city, region, country, country-code and timezone lookup with provider fallbacks.
  • Improved Cloudflare, trusted-proxy and forwarded-IP resolution.
  • Rebuilt the Visitors screen with clean human-readable columns, masked technical details and responsive mobile cards.
  • Added visible settings-save confirmation and Saving state.
  • Reduced false bot classifications for paid/social visitors.
  • Kept the public plugin version and Pro compatibility at 1.1.0.