外掛標籤
開發者團隊
② 後台搜尋「Visitrix – Lightweight Visitor Analytics」→ 直接安裝（推薦）
原文外掛簡介
Visitrix gives you a clean, informative traffic summary right in the WordPress admin – without third-party services or heavy scripts, and without cookies by default. Open Statistics in the admin menu and see where your visitors come from, what devices they use and how engaged they are.
Plugin homepage with screenshots and setup steps (in Russian): genius-bot.ru/plugins/visitrix/
What you get
Key metrics – visits, visitors, pageviews, bounce rate, page depth, time on site and share of new visitors, each compared with the previous period.
Traffic chart – by hour for short periods, by day for longer ones. Toggle visits, visitors, pageviews and new visitors.
Traffic sources – direct traffic, search engines, social networks, messengers, AI assistants (ChatGPT, Perplexity, Gemini and others), links from other sites, ads (UTM tags, yclid, gclid) and internal traffic.
Search engines – Google, Yandex, Bing, DuckDuckGo, Mail.ru, Baidu and others.
New and returning visitors – bounce rate, page depth and time on site for each group, plus loyalty (how many times visitors came back).
Online now – visitors active during the last 5 minutes.
Devices – PC, smartphone or tablet, plus browsers and operating systems.
Goals without setup – form submissions (Contact Form 7, WPForms, Elementor and regular forms), clicks on phone numbers, e-mails and messengers, file downloads and outbound links, with conversion by traffic source.
Scroll map – see how far visitors scroll each page, right on top of the page, separately for PC, smartphones and tablets.
WordPress content – most read posts, categories, tags and authors, with read depth.
Content – popular pages, landing pages and UTM campaigns.
Periods – today, yesterday, 3 days, week, month or any custom date range.
Dashboard widget with today’s numbers.
How metrics are calculated
A visit is a sequence of pageviews with no more than 30 minutes of inactivity. Arriving from a different external source starts a new visit.
A bounce is a visit with a single pageview that lasted less than 15 seconds.
Time on site is measured with lightweight engagement pings while the page is visible.
A new visitor is a visitor whose first visit falls within the selected period; everyone else is returning. Each visitor belongs to exactly one group.
With the robot filter (on by default) a visit is counted after the first real interaction: scroll, tap, click, key press or a second pageview.
Lightweight
The tracker script is about 2 KB gzipped, loaded with defer and sent with navigator.sendBeacon, so it does not slow pages down.
Beacons are handled right after plugins load – without the theme, init hooks or the REST API – so each hit costs a fraction of a page render.
About 3 requests per pageview: the pageview, a ping at 15 seconds and one when the visitor leaves (plus one every 3 minutes on long reads).
Works with page caching plugins – the front-end needs no nonces or PHP sessions.
Compact database tables with automatic cleanup of old records.
Optional separate database – MySQL/MariaDB or ClickHouse – to keep the statistics out of the WordPress database (see below).
The dashboard is plain JavaScript with built-in SVG charts – no external libraries, no CDN.
Visitor identification
Choose the mode that fits your privacy policy:
Without cookies (default) – a random anonymous ID in localStorage.
Accurate – the ID is also kept in a first-party HttpOnly cookie set by your own server. Returning visitors are recognized in Safari after 7+ days and across www/non-www.
Anonymous – nothing is stored in the browser. Pageviews are grouped into visits with a hash of IP and user agent that changes daily; the IP itself is never stored.
Works with the WP Consent API: until a visitor allows statistics in your cookie banner, their visits are counted in the anonymous mode.
Separate database (optional)
By default the statistics are stored in the WordPress database. On hosting with a small database quota, or to keep the statistics away from the site content, Visitrix can write them to a separate MySQL or MariaDB database:
a second database of your hosting;
a cloud MySQL-compatible database: Yandex Managed Service for MySQL, VK Cloud, Selectel, Timeweb Cloud, Amazon RDS and Aurora, Google Cloud SQL, Azure Database for MySQL, DigitalOcean, PlanetScale, TiDB Cloud and others.
Or to ClickHouse – ClickHouse Cloud, Yandex Managed Service for ClickHouse, Altinity or your own server. Visitrix talks to it over the HTTP(S) interface, so no PHP extension is needed. ClickHouse stores an append-only event log; visits, pages and goals are assembled from it by views with the same rules as in MySQL, so the reports are identical. Old events expire automatically after the retention period (TTL).
The connection is checked before it is saved, SSL/TLS with your provider’s CA certificate is supported for MySQL, and earlier statistics can be copied to the new database in one click, after which the WordPress tables can be emptied. If the external database becomes unreachable, visits are not recorded (they never fall back into the WordPress database) and a notice is shown on the Visitrix pages.
Privacy
No cookies by default; nothing at all is stored in the anonymous mode.
IP addresses are not stored.
All data stays in your own database (the WordPress one or a database you choose) and is never sent to third parties.
Optional respect for the browser Do Not Track signal.
Suggested text is added to the WordPress Privacy Policy guide.
Support the development
Visitrix is free and has no ads or paid limits. If it saves you time, you can thank the developer with a small donation on genius-bot.ru – it helps release updates, translations and new free plugins.
Additional Information
Developer
Visitrix is developed and maintained by genius-bot.ru.
Plugin page: genius-bot.ru/plugins/visitrix/
Website: genius-bot.ru
Telegram: t.me/Alex_mlr_dev – questions, bug reports and feature requests.
Requirements
WordPress 6.2 or later
PHP 7.4 or later
MySQL 5.7+ or MariaDB 10.3+
WordPress REST API must be reachable (it is enabled by default)
Languages
Visitrix is fully translatable. Translations are delivered automatically from translate.wordpress.org – you can help translate it into your language.
Data stored
{prefix}visitrix_visits – one row per visit: start time, duration, pageviews, source, landing page, UTM tags, device type, browser and OS.
{prefix}visitrix_hits – one row per pageview: page path and title.
{prefix}visitrix_visitors – one row per known visitor: anonymous ID, first and last visit, number of visits.
{prefix}visitrix_goals – one row per reached goal: type, target (form name, phone number, file, domain) and page.
Records older than the retention period (365 days by default) are removed daily. With a separate database the same tables are created there with the prefix you choose; deleting the plugin never touches the external database.
Developer hooks
visitrix_should_track (filter) – return false to skip tracking on the current page.
visitrix_source_rules (filter) – add or change search engines, social networks, messengers and AI services.
visitrix_view_capability (filter) – capability required to view reports.
visitrix_client_ip (filter) – client IP used for the anonymous daily hash (for sites behind a proxy).
