Live Traffic Analytics - Real-Time Visitor & Bot Tracking - Google Analytics Alternative

The plugin tracks page views, sessions, visitor countries, referrers, devices, browsers, top pages and bot activity. It also records first-landing UTM attribution and visits to WordPress 404 pages.

Visitor Comparison shows today's visitor total against yesterday's, side by side, with a percentage change indicator and an hour-by-hour comparison chart, so you can see whether traffic is trending up or down.

Yes. The plugin works as a live visitor tracker and shows active traffic in the WordPress dashboard using recent activity data from your own site.

Yes. The admin dashboard refreshes automatically, so you can monitor active sessions, live activity, top pages, and bot traffic in near realtime.

Yes, but localhost traffic commonly uses private IP addresses such as 127.0.0.1 or ::1, so country and map data may appear as unknown during local testing.

Yes. The plugin stores analytics data in dedicated custom tables for activity, sessions, and page statistics.

The plugin uses dedicated tables for activity logs, session paths, and page statistics so analytics queries stay separate from standard WordPress content tables.

Yes. The Top Pages section shows page URLs, total views, and latest visit timestamps, with a 10/20/30 rows-per-page selector and pagination so you can browse large sites comfortably.

Yes. The User Journey section groups multiple page visits into a session path so you can understand how visitors move through your website.

Yes. Live activity and session tracking can include referrer data when it is available from the visitor request.

The admin dashboard uses lightweight refresh requests to show near realtime analytics updates.

Yes. The plugin includes bot detection using user-agent checks and suspicious request pattern scoring.

The plugin can identify common bots through user-agent patterns and can also flag suspicious automated traffic based on repeated request behavior.

It depends on your needs. Live Traffic Analytics is useful for lightweight realtime visibility inside WordPress, but full enterprise analytics platforms may still offer broader reporting, attribution, and historical analysis.

The plugin is designed to be lightweight and uses optimized storage and scoped tracking, but every analytics system adds some overhead. It is best practice to test on your own hosting stack before production rollout on very high traffic sites.

No. The tracking flow avoids admin requests and other noisy request types where possible to keep analytics cleaner.

Open Campaign / UTM Reports and use the campaign link builder. Create a tagged link and view recorded sessions by source, medium, campaign, content and term. Tagged links are recorded even within an existing session. Each session counts once per UTM combination and can appear under different campaigns. Reload report fetches fresh results. Reports count sessions rather than ad clicks, sales or conversions; older mid-session campaign visits are not backfilled.

New tracker visits count time while the page is visible. Time spent in a background tab is excluded. A return after an expired session starts a new session unless another active tab is keeping the shared session alive. Historical records are kept as previously recorded.

Cloudflare visitor IP headers are accepted when the direct peer belongs to its verified proxy ranges. Other proxies must be explicitly trusted through the wplta_trusted_proxy_peer filter or an existing WPLTA_TRUST_PROXY integration. The proxy must overwrite client-supplied forwarding headers. The wplta_client_ip filter remains available for custom integrations.

404 Visit Reports show recorded visits to actual WordPress 404 pages, grouped by path and referring site. They do not crawl your site for broken links or create redirects. Reports start with visits recorded after the feature is installed and its database upgrade completes.

Yes. Add [wplta_active_users] to a shortcode block or another shortcode-enabled area to display the active-user count as text. Full-page caching can delay updates to the displayed count.

Open Traffic Analytics → SEO Preview + Health. Select a published page to view its search preview and health checks. Choose Scan site for a page-by-page overview with duplicate metadata checks. Use Edit to make changes in WordPress or your SEO plugin, then Rescan page to fetch fresh HTML.

No. It reads your published pages and WordPress settings. It does not provide Google search queries, clicks, impressions, rankings or verified indexing status. The preview is an estimate, and intentional noindex or canonical rules should be reviewed before changing them.

SEO Preview + Health inspects the published output of your theme and SEO plugin. It does not generate metadata, change canonical URLs, create sitemaps or automatically fix SEO issues. Continue editing those settings in your existing tools.

Open Traffic Analytics → Settings → Export analytics. Choose PDF for a report with graphs and tables, or CSV for the underlying data in Section/Record/Field/Value columns. Exports use the saved dashboard window and include zero values. Settings save automatically; wait for any changes to finish saving before exporting. The report labels live, last-24-hours and comparison metrics separately. Top lists and recent records keep the dashboard's row limits; this is a dashboard report, not a complete database backup. Files are generated locally in your browser; PDF generation does not send your data to a third-party service.

The plugin is designed to remain lightweight and privacy-conscious. On some environments, exact latitude and longitude precision may depend on the hosting or proxy headers available to WordPress.

Yes. It can be useful for blogs, agency sites, company websites, landing pages, and ecommerce stores that want lightweight live analytics inside WordPress.

Yes. The plugin uses a modular structure with separate admin, public, and include layers, which makes future feature expansion easier.

After activating the plugin, open the Traffic Analytics menu in WordPress admin. Visit a few frontend pages first if you want to immediately generate test data.

Existing analytics tables update automatically in small background steps. Opening WordPress admin also advances the update when scheduled tasks are delayed. Existing tracking continues, and the progress notice disappears when the update finishes. You normally do not need to click Retry or configure cron. If an update reports an actual failure, check its message before retrying. A large database index build can still take time and use server resources.