Module · Statistics
ExpertPress Statistics
ExpertPress Statistics gives every specialist a private statistics page with their earnings, sessions, client path from page view to completed session, complaints, reviews and reliability. It counts anonymous page views of specialist profiles and services, shows verified platform facts ("badges") on public profiles, and gives the site team a reliability report that marks clients and specialists who often cancel, reschedule or leave requests unanswered with a yellow card. All counting and storage happen in your own WordPress database; nothing is sent to outside analytics services.
Key capabilities
- Statistics page in the specialist cabinet: earnings, completed sessions, new and returning clients, average check, sessions by day, the client path (views, requests, confirmed, paid, completed), per-service figures, complaints, reviews and the specialist's own reliability status, for a period the specialist chooses.
- Honest page-view counting for specialist profiles and service pages: repeat views by the same visitor within a time window, staff roles, the specialist's own visits and known bots are not counted. Counts are stored as hourly totals per page, never per visitor.
- View statistics for the team: total page views for the whole marketplace, views by day, the top 50 specialists by views, and a per-specialist breakdown by service.
- Reliability yellow cards: the site recalculates each specialist's and client's behaviour (unanswered requests, late cancellations and reschedules, justified complaints) against thresholds you set, and lists everyone who crosses them. A yellow card is a signal for the team; it never blocks anyone by itself.
- Moderation actions: remove a specialist from search with a reason (and return them), remove a yellow card manually with a reason, export the list as CSV.
- Yellow-card emails to the team and to the specialist, editable and switchable.
- Platform facts on public profiles: up to four automatically earned facts — Fast reply, No disruptions, Stable rating, Many completed sessions — that specialists cannot buy or set themselves.
- Data retention rules for page-view history and reliability history, managed together with the core plugin's retention settings.
Requirements
- ExpertPress (the core plugin) must be installed and active (
Requires Plugins: expertpress). Without it the module does nothing. - WordPress 6.0 or newer, PHP 7.4 or newer.
- A MySQL or MariaDB database with InnoDB tables (the WordPress default). If the module's tables cannot be created as InnoDB, the module stays inactive.
- WordPress scheduled tasks (WP-Cron or a real server cron) must run. The reliability recalculation and the data cleanup run in the background; if they stop, the Reliability screens show a warning (see Reliability and yellow cards).
- No third-party services or accounts are needed.
- Money figures in the specialist statistics (earned, average check, commission rate, refunds) come from the marketplace's money records. They are most complete with the ExpertPress Payments module; how they look on a site that only marks payments by hand depends on the records the core keeps.
What changes for each audience
Clients and site visitors
- Specialist profiles may show a Facts about the specialist (Факти про спеціаліста) section with the platform facts the specialist has earned, each with a one-line explanation and the footnote "Based only on platform activity. These facts do not confirm professional qualifications or guarantee results." If a specialist has earned no facts, the section is not shown. The same facts are added to the public specialist profile in the REST API (
platform_facts). - Visiting a profile or service page may be counted as one page view. The visitor's browser may receive a first-party cookie
ep_stats_vid(see Privacy below). - Clients do not see their own reliability status and receive no yellow-card emails.
Specialists
- A new Statistics (Статистика) item in the specialist cabinet, at
/specialist/statistics/by default (the last part of the address is set under Pages and terms). The same data is also available to the specialist through the core's private statistics read used by the mobile app. - The page shows, for the chosen period (by default 7, 30, 90 or 365 days, in the specialist's own calendar time zone), with a comparison to the previous period where it makes sense:
- Earned (Заробили), Consultations (Консультацій), New clients (Нових клієнтів, with how many came back), Average check (Середній чек) and the current commission rate when one applies;
- Consultations by day — a bar chart; tapping a bar shows the amount for that day;
- Client path (Шлях клієнта) — profile and service page views, requests, confirmed, paid and completed, each with its share of the previous step;
- Reliability (Надійність) — All good or a Yellow card notice that lists the rules triggered, plus the figures behind them;
- Complaints (Скарги) — complaints filed, upheld against the specialist, refunds paid through complaints, and the specialist's own complaints about clients;
- Services — per-service figures;
- Reviews (Відгуки) — new approved reviews and the average rating for all time;
- Where this data comes from (Звідки ці дані) — a plain explanation of how each figure is counted.
- The site team decides which of these blocks appear and in what order (Cabinet & rules).
- The cabinet overview shows a yellow-card notice while a card is active.
- When a yellow card is issued, the specialist receives an email listing the triggered rules; when the team removes it manually, they receive another email. When the team removes them from search or returns them, the core sends its own email with the reason.
- Their own visits to their profile and services are not counted as views (by default).
The site team
- A Reliability (Надійність) item in the Modules group of the ExpertPress admin app, with a counter of people currently under watch. Tabs: Under watch, Specialists, Clients (administrators only), Removed from search, View statistics, and for managers and administrators Badges, Thresholds, Cabinet & rules and Page views. See Settings and admin screens.
- Team emails when someone gets a yellow card (to the addresses you set, or the core's team mailbox).
- Four new emails in Settings → Email templates under the group Statistics / reliability (Статистика / надійність).
- Reliability events (card issued, cleared automatically, cleared manually) appear in the participant history (dossier), with a Reliability cards summary line.
- New rows on Settings → Data retention.
Who can use what
| Action | Administrator | Manager | Moderator | Accountant |
|---|---|---|---|---|
| Open Reliability: Under watch, Specialists, Removed from search, View statistics; CSV export | yes | yes | yes | no |
| Clients tab and client CSV | yes | no | no | no |
| Remove from search / return to search | yes | yes | yes | no |
| Remove a yellow card manually | yes | yes | no | no |
| Badges, Thresholds, Cabinet & rules, Page views settings | yes | yes | no | no |
Roles are described in Roles and access.
Privacy and data storage
Nothing is sent to external services. The module has no third-party analytics, tracking pixels or outside API calls. Emails go through the core plugin's normal mail queue.
Visitor cookie. On public pages the module sets a first-party cookie ep_stats_vid for every visitor, either when the page is generated or through a small script that calls the site's own REST address /wp-json/expertpress-statistics/v1/visitor-cookie (so it also works behind a page cache). The cookie holds a random identifier signed by the site, lasts two years, is HttpOnly and SameSite=Lax, and is used only to avoid counting the same browser twice within the deduplication window. If your site uses a cookie-consent tool, classify this cookie yourself; the module does not ask for consent. When a request has no valid cookie, a one-way hash of the IP address and browser user agent is used for that request instead; the IP address itself is not stored. The cookie endpoint is rate-limited per IP address and per visitor.
What is stored locally:
- Page views: one row per page per hour with a count. No visitor ID, IP address or user agent is kept with the counts.
- Short-lived deduplication keys (a hash of the visitor token and the page) with an expiry time equal to the deduplication window; expired keys are deleted by the core's scheduled cleanup.
- Reliability state for each specialist and client: whether a card is active, since when, and the counted figures.
- Reliability history: card issued, cleared automatically, cleared manually (with the operator and the reason), each with a snapshot of the figures and thresholds at that moment.
- A journal of changes to the reliability thresholds and badge settings (who changed what, when).
- Cached statistics pages and badge results (for up to the cache time, 5 minutes by default).
How long it is kept. By default, everything is kept until you set a retention period. Under Settings → Data retention the module adds:
| Row | What is deleted | Default |
|---|---|---|
| Hourly page views (Почасові перегляди сторінок) | Hourly view counters older than the period; only fully expired hours are removed. Old views disappear from reports. | keep indefinitely |
| Reliability history (Історія надійності) | Automatic card changes older than the period. Current cards and records still needed as evidence (for example for a complaint or the dossier) are kept. | keep indefinitely |
| Settings version history (Історія версій налаштувань) | Earlier versions of the reliability and badge settings. The current version, and every version a saved yellow card was based on, are kept. | keep indefinitely |
| Manual yellow card removals (Ручні зняття жовтих карток) | Records of cards removed by the team, with the reason and operator. Minimum period 30 days. | keep indefinitely |
On older core versions without the shared retention screen, the first two periods are set on the module's Page views tab instead.
Uninstalling. Deleting the plugin from Plugins cancels its unsent emails and then removes all module tables, settings and cached data. If any step cannot be confirmed, the cleanup stops and keeps the remaining data, leaving a note (expertpress_statistics_uninstall_incomplete option) that says at which stage it stopped. Deactivating only stops the background tasks; it does not delete data.