Module · Statistics
Statistics: settings and admin screens
Where: ExpertPress admin app → Modules → Reliability (Надійність)
Everything the module adds to the admin lives on one screen with tabs. The menu item shows a counter with the number of people currently under watch (specialists, plus clients for administrators).
| Tab | Ukrainian label | Who sees it | What it is for |
|---|---|---|---|
| Under watch | Під наглядом | moderators, managers, administrators | Everyone with an active yellow card, with the figures and actions. Opens by default. |
| Specialists | Спеціалісти | moderators, managers, administrators | Specialists with a yellow card, paged, with CSV export. |
| Clients | Клієнти | administrators only | Clients with a yellow card, paged, with CSV export. |
| Removed from search | Прибрані з пошуку | moderators, managers, administrators | Remove a specialist from search by ID or email; history of removals and returns. |
| View statistics | Статистика переглядів | moderators, managers, administrators | Page-view report for the whole marketplace and per specialist. |
| Badges | Значки | managers, administrators | Conditions for the platform facts shown on public profiles. |
| Thresholds | Пороги | managers, administrators | Yellow-card thresholds and yellow-card emails. |
| Cabinet & rules | Кабінет і правила | managers, administrators | The specialist statistics page layout, metric definitions, reliability rule options and background task timing. |
| Page views | Перегляди сторінок | managers, administrators | What counts as a page view, and (on older cores) how long view and reliability history is kept. |
Moderators, managers and administrators are described in Roles and access. Accountants do not see the Reliability item.
How yellow cards are calculated, issued and removed is explained in Reliability and yellow cards.
Saving
Each settings tab has its own Save button and saves only its own form. After saving you return to the same tab with a green message (Saved. or Settings saved.) or a red one.
- Numbers outside the allowed range are not refused: they are brought to the nearest allowed value (for example 500 becomes 365 for an observation window).
- Thresholds and Badges keep a version number. If someone else saved the same tab after you opened it, your save is refused with "Another administrator changed the settings. Refresh the page."; if two people save at the same moment, one sees "Another administrator is saving right now. Try again." Every save of these two tabs is written to the module's settings journal with the old and new values and who made the change.
- A theme or site plugin can change the built-in defaults of most options. The defaults below are those of the module itself.
Admin screens
Under watch
Where: Reliability → Under watch (Під наглядом)
The header says "Who often cancels, reschedules, or does not reply. A hint for the operator: the system does not block anyone on its own." Under it: Last run: with the time of the last background recalculation, and a warning if it has not run for too long (see Background recalculation).
Each person with an active card is shown as a card (up to 20 specialists and, for administrators, 20 clients):
- Name, role and email; a pill Under watch since with the date the card was issued; the list of triggered rules in plain words.
- A button Open specialist bookings or Open client bookings, which opens the core Bookings list filtered to that person.
- Meters with the figures: for specialists No reply (N of M requests — X%, threshold Y%), Own late cancellations (N in D days, threshold T) and Justified complaints; for clients Rescheduling and cancellations. The black tick on a meter is the threshold; orange means the value is at or above it.
- A hint box What you can do with a suggested next step.
- For specialists: the search state (in search, or removed
, ), and the actions:- Remove yellow card (managers and administrators) — needs a Reason for removal of 5–1000 characters and a confirmation. See Removing a card manually.
- Remove from search with a Reason for the specialist, or Restore with a Comment for the specialist if they are already removed — 5–1000 characters, with a confirmation.
When nobody has a card: "No clients or specialists with a yellow card."
Managers and administrators also see a side panel Threshold settings (Налаштування порогів) with the same ten thresholds as the Thresholds tab, and a link Badge conditions and thresholds. Saving the side panel changes only the thresholds; email settings are kept.
Buttons in the header: Refresh.
Specialists and Clients
Where: Reliability → Specialists / Clients
The same cards as on Under watch, for one type of person, 50 per page with page links. Export CSV downloads every flagged person of this type as a semicolon-separated UTF-8 file:
- Specialists:
user_id; name; email; entered_at; rules; overdue; no_reply_pct; late_own; complaints. - Clients:
user_id; name; email; entered_at; rules; client_actions; complaints.
entered_at is in UTC. The note under the list reminds: "A yellow card does nothing automatically. Moderation decides." For clients there are no actions on this screen: discuss the case with the client by email or act on their bookings from the Bookings screen.
Removed from search
Where: Reliability → Removed from search (Прибрані з пошуку)
- Remove from search by ID or email: type the Specialist ID or email and a Reason (the specialist will receive it), 5–1000 characters, then Remove from search and confirm "Remove the specialist from search? New bookings will stop coming to them." This works for any specialist, with or without a yellow card.
- History: every removal with Specialist, Removed (date and who), Reason, Returned (date and who, or a dash while still removed), Comment, and for active removals a Restore form with a comment for the specialist. 50 rows per page.
The removal itself is performed by the core plugin: the specialist stops appearing in the catalog and search, so new bookings stop coming to them, and the core sends the specialist an email with the reason. Removal from search is independent of the yellow card: removing a card does not return a specialist to search, and returning them does not remove the card. Messages: "The specialist was removed from search; the email has been sent.", "The specialist is back in search; the email has been sent.", "Already set; nothing was changed." If the core is too old to support removal from search, the tab shows "Core schema 54 is required."
View statistics
Where: Reliability → View statistics (Статистика переглядів)
A read-only report of page views of specialist profiles and service pages. "These are page views, not unique visitors."
- Period chips — the same day counts as Allowed periods (days) on Cabinet & rules; the default chip is the Default period. Days are counted in the site's time zone; the date range and zone are shown under the totals.
- Total page views, Attributed, Unattributed (deleted services), Profile pages, Service pages, and Views by day.
- Top specialists by page views — up to 50 specialists with Profile, Service, total Views and an Open button.
- Open shows one specialist: their totals, views per service and views by day, with Back to platform views.
Views of services that were deleted later are counted as Unattributed; archived services that still exist stay with their specialist. Old hours removed by data retention no longer appear.
Badges
Where: Reliability → Badges (Значки) — managers and administrators
"Platform facts appear only on the specialist profile. Specialists cannot buy or assign them." The site checks each published specialist against these conditions when their profile is shown and keeps the result for up to 5 minutes. A specialist with an active yellow card never shows No disruptions. Facts appear in the Facts about the specialist section of the public profile, each with an explanation built from your numbers (for example "Average reply to booking requests within 12 hours, at least 5 replies in the last 30 days."). Saving this tab refreshes the public catalog cache.
Maximum facts shown
- Where: Reliability → Badges, top of the form
- What it does: How many earned facts a profile shows at most. Facts are taken in priority order.
- Default: 3.
- Values / limits: 1–4.
- When to change it: 4 to show every earned fact; 1 or 2 for a calmer profile layout.
- Related: Priority
Enabled
- Where: Reliability → Badges → each fact (Fast reply, No disruptions, Stable rating, Many completed sessions)
- What it does: Turns the fact on or off for every specialist. A disabled fact is never calculated or shown.
- Default: on for all four.
- Values / limits: on / off.
- When to change it: turn off Stable rating while your site has few reviews; turn off Fast reply if specialists confirm requests through an outside channel.
Priority
- Where: Reliability → Badges → each fact
- What it does: Order of the facts on the profile. "Lower priority numbers appear first. Equal numbers use the default badge order." The default order is Fast reply, No disruptions, Stable rating, Many completed sessions.
- Default: 10, 20, 30, 40 in the order above.
- Values / limits: 0–999.
- When to change it: put Stable rating first if ratings matter most to your clients.
- Related: Maximum facts shown
Fast reply: Maximum average reply (hours)
- Where: Reliability → Badges → Fast reply (Швидка відповідь)
- What it does: The specialist earns the fact when their average time to reply to booking requests in the observation window is at most this many hours.
- Default: 12.
- Values / limits: 1–720.
- When to change it: 4–6 hours for a marketplace of same-day sessions; 24 hours if sessions are booked weeks ahead.
Fast reply: Minimum booking replies
- Where: same fact
- What it does: The fact needs at least this many replies in the window, so one quick reply is not enough.
- Default: 5.
- Values / limits: 1–100000.
Observation window (days)
- Where: Fast reply, No disruptions and Many completed sessions
- What it does: How many recent days are counted for that fact. The profile shows it as Last N days.
- Default: 30 for Fast reply and No disruptions; 90 for Many completed sessions.
- Values / limits: 1–3650.
- When to change it: longer windows (90–180) on a young site with few bookings, so facts do not appear and disappear week to week.
No disruptions: Minimum completed sessions
- Where: Reliability → Badges → No disruptions (Без зривів)
- What it does: The fact requires no late cancellations or reschedules caused by the specialist in the window, no active yellow card, and at least this many completed sessions. "Late" uses “Late” means less than … hours before start from Thresholds; the allowed number of late changes is always 0 and cannot be changed.
- Default: 3.
- Values / limits: 1–100000.
- When to change it: raise it so a specialist needs a real track record before showing the fact.
- Related: “Late” means less than
Stable rating: Minimum verified average (1–5)
- Where: Reliability → Badges → Stable rating (Стабільна оцінка)
- What it does: The fact needs an average rating from published verified reviews of at least this value. Counted over all time; the window cannot be changed.
- Default: 4.5.
- Values / limits: 1–5, two decimals.
Stable rating: Minimum published verified reviews
- Where: same fact
- What it does: The fact needs at least this many published verified reviews.
- Default: 10.
- Values / limits: 1–100000.
- When to change it: lower it (for example 5) on a young site, raise it once specialists have many reviews.
Many completed sessions: Minimum completed sessions
- Where: Reliability → Badges → Many completed sessions (Багато проведених сеансів)
- What it does: The fact needs at least this many completed sessions in the window.
- Default: 20.
- Values / limits: 1–100000.
Thresholds
Where: Reliability → Thresholds (Пороги) — managers and administrators. The first ten fields are also on the Threshold settings side panel of Under watch.
A person gets a yellow card when at least one rule reaches its threshold, and loses it automatically when all rules are below their thresholds again (see Reliability and yellow cards). A threshold of 0 turns that rule off. A change applies from the next recalculation; existing cards are not rewritten, but a save starts a recalculation right away.
Specialist observation window
- Where: Reliability → Thresholds
- What it does: Specialist rules count events of the last N days, in the specialist's own time zone. The specialist's email and statistics page name this number.
- Default: 30 days.
- Values / limits: 1–365.
- When to change it: 60–90 days on a site with few bookings per specialist; 14 days if you want cards to clear quickly after improvement.
Client observation window
- Where: same tab
- What it does: Client rules count events of the last N days, in the client's time zone.
- Default: 30 days.
- Values / limits: 1–365.
“Late” means less than
- Where: same tab (unit: hours before start)
- What it does: A cancellation or reschedule by the specialist counts as late when it happens less than this many hours before the session start. Also used by the No disruptions fact.
- Default: 24 hours.
- Values / limits: 1–168.
- When to change it: 48 hours if clients need time to rearrange their day; 12 hours for a marketplace of short-notice sessions.
- Related: Booking times and rules
No reply — from
- Where: same tab (unit: % of requests)
- What it does: "Share of requests the specialist did not answer in time." The share is unanswered (expired) requests divided by all closed requests (confirmed, declined or expired) in the window. The rule triggers at this percentage or more.
- Default: 20 %.
- Values / limits: 0–100; 0 turns the rule off.
- When to change it: 10 % if quick answers are central to your service; 30–40 % while specialists are still learning the cabinet.
- Related: Minimum closed requests for the percentage, Maximum specialist response time
Specialist late cancellations — from
- Where: same tab (unit: times)
- What it does: Triggers when the specialist cancelled, or moved with the client's agreement, this many sessions late in the window. Late moves count only while Count specialist-initiated late rescheduling toward the yellow card is on; changes made by staff on the specialist's behalf also count.
- Default: 2.
- Values / limits: 0–100; 0 turns the rule off.
- Related: Cabinet & rules → Reliability rules
Client rescheduling and cancellations — from
- Where: same tab (unit: times)
- What it does: Triggers when the client cancelled bookings, or had reschedules they requested accepted, this many times in the client window (any timing, not only late), including changes staff made and attributed to the client.
- Default: 3.
- Values / limits: 0–100; 0 turns the rule off.
Overdue ≥ (0 to turn off)
- Where: same tab
- What it does: Triggers when this many booking requests expired without the specialist's decision in the window.
- Default: 3.
- Values / limits: 0–100.
- When to change it: turn it off (0) if you prefer the percentage rule alone, so busy specialists are not flagged for a few misses among many requests.
Minimum closed requests for the percentage
- Where: same tab
- What it does: The No reply percentage rule only applies once the specialist has at least this many closed requests in the window, so one missed request out of one is not 100 %.
- Default: 5.
- Values / limits: 1–1000.
Justified complaints about the specialist ≥
- Where: same tab
- What it does: Triggers when this many client complaints filed in the window were decided by the team with the specialist at fault.
- Default: 2.
- Values / limits: 0–100; 0 turns the rule off.
- Related: Complaints
Justified complaints about the client ≥
- Where: same tab
- What it does: Triggers when this many specialist complaints about the client filed in the client window were decided with the client at fault.
- Default: 2.
- Values / limits: 0–100; 0 turns the rule off.
Yellow-card letters
These options are on the Thresholds tab under Yellow-card letters (Листи про жовту картку). The same four emails also appear in Settings → Email templates in the group Statistics / reliability:
| Email templates label | Sent to | When | |
|---|---|---|---|
| Team letter — specialist | Yellow card — team (specialist) | team addresses | a specialist gets a card |
| Team letter — client | Yellow card — team (client) | team addresses | a client gets a card |
| Specialist letter | Yellow card — specialist | the specialist | they get a card (once per card) |
| Card removed letter | Yellow card cleared — specialist | the specialist | the team removes their card manually |
No email is sent when a card clears automatically, and clients never receive a yellow-card email.
Which setting wins. Once the on/off state or a text of one of these emails has been saved on the Email templates tab, that value is used; the fields on this tab are used only while the Email templates tab has nothing saved for that email. On the Email templates tab, one on/off switch (on the specialist team email) covers both team emails.
Notify the team
- Where: Reliability → Thresholds → Yellow-card letters
- What it does: Sends the team letter for every new specialist or client card.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if your team checks Under watch daily anyway.
Notify the specialist
- Where: same section
- What it does: Sends the specialist an email when they get a card, listing the rules in plain words and explaining that the card goes away when the figures improve.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if you prefer to contact specialists personally first.
Notify when the card is removed
- Where: same section
- What it does: Sends the specialist an email when the team removes their card manually.
- Default: on.
- Values / limits: on / off.
Team addresses
- Where: same section
- What it does: Who receives team letters. One address per line, or separated by commas, semicolons or spaces; invalid entries are ignored.
- Default: empty — the core's team mailbox (the address used for complaints), or the WordPress administration email if the core has none.
- Values / limits: any number of valid emails.
- When to change it: send cards to the moderators' shared mailbox instead of the general one.
- Note: while team letters are on, a card can only be recorded when at least one valid address is found. Keep this list (or the core team mailbox) valid.
Letter subjects and bodies
- Where: same section: Team letter — specialist yellow card (subject) / (body), Team letter — client yellow card (subject) / (body), Specialist yellow-card letter (subject) / (body), Yellow card cleared letter (subject) / (body)
- What it does: Replaces the standard subject or text of that email. Empty means the standard text in the recipient's language.
- Default: empty. The standard texts are:
- team letters: subject Specialist yellow card or Client reliability breach; the text gives the type, ID, name, triggered rules, the window and a link to the Reliability list;
- specialist letter: subject Reliability yellow card; the text lists the rules triggered in the last N days, says the platform team may take action and that the card is removed automatically when the figures fall below the thresholds, with a link to the statistics page;
- card removed letter: subject Yellow card removed; the text says when the team removed the card and that figures now count from that moment.
- Values / limits: plain text. Placeholders:
{rules}(triggered rules, one per line),{days}(window in days),{url}(link: the Reliability list for team letters, the specialist's statistics page for specialist letters),{name},{id},{when}(time of manual removal),{brand},{site}. An unknown placeholder makes the save fail with "Thresholds saved, but letter settings could not be saved." — the thresholds are saved, the letter fields are not. - When to change it: add your support contacts to the specialist letter; write the team letter in your team's working language.
- Related: Email templates (per-language texts and preview)
Cabinet & rules
Where: Reliability → Cabinet & rules (Кабінет і правила), page title Statistics cabinet — managers and administrators
Layout of the specialist's statistics page, how some figures are defined, reliability rule options and background task timing. One Save button for the whole tab. Changes reach specialists after their cached statistics expire (see Cabinet cache TTL).
Block order
- Where: Reliability → Cabinet & rules → Blocks
- What it does: Which blocks the specialist statistics page shows and in what order, one key per line, top to bottom. Blocks not listed are hidden.
- Default:
tiles,days,funnel,reliability,complaints,services,reviews,source(all blocks). - Values / limits: "Allowed: tiles, days, funnel, reliability, complaints, services, reviews, source." Unknown keys and repeats are dropped; an empty list shows all blocks. Keys:
tiles— Earned, Consultations, New clients, Average check;days— Consultations by day;funnel— Client path with page views;reliability— yellow card status;complaints;services;reviews;source— Where this data comes from. - When to change it: remove
funnelif you do not want specialists to see view figures; movereliabilityto the top to stress punctuality.
Hide groups
- Where: Reliability → Cabinet & rules → Blocks
- What it does: Passes a "hide groups" flag to the statistics page template. The standard template does not use it, so it has no visible effect unless your theme's statistics template reads it.
- Default: off.
- Values / limits: on / off.
Hide complaints
- Where: same section
- What it does: Hides the Complaints block from specialists even if
complaintsis in the block order. - Default: off.
- Values / limits: on / off.
- When to change it: while you are not handling complaints through the site.
Hide no-shows
- Where: same section
- What it does: Passes a "hide no-shows" flag to the statistics page template. Like Hide groups, it has no visible effect in the standard template.
- Default: off.
- Values / limits: on / off.
Allowed periods (days)
- Where: Reliability → Cabinet & rules → Periods
- What it does: "Comma-separated day counts, e.g. 7,30,90,365. Chips in the cabinet come from this list." The same list is used for the chips on View statistics.
- Default: 7, 30, 90, 365.
- Values / limits: whole numbers 1–3660; repeats removed, sorted ascending. An empty or invalid list falls back to the default.
- When to change it: add 14 for specialists who plan in two-week cycles; remove 365 on a site younger than a year.
Default period (days)
- Where: same section
- What it does: The period selected when the statistics page (or View statistics) opens.
- Default: 30.
- Values / limits: must be one of the allowed periods; otherwise 30 is used if allowed, else the shortest allowed period.
Funnel stages
- Where: Reliability → Cabinet & rules → Metric definitions
- What it does: Which steps the Client path shows and in what order. Each step shows its share of the previous one.
- Default:
views,requested,accepted,paid,completed. - Values / limits: "Allowed: views, requested, accepted, paid, completed. Order matters." Unknown keys are dropped; an empty list shows all steps.
- When to change it: drop
paidon a site where payment is marked by hand and is not reliable; dropviewsto show only the booking steps.
Returning client
- Where: same section
- What it does: How the statistics page decides that a paying client is "returning" (shown as N came back again under New clients).
- Default: Any prior booking with this specialist (current behaviour).
- Values / limits: Any prior booking with this specialist or Prior booking within N days, with N from 1 to 3650 (default 365).
- When to change it: choose N days (for example 180) if a client returning after several years should count as new.
Average order value
- Where: same section (shown to specialists as Average check)
- What it does: What the average check is based on, for orders with their first payment in the period, minus refunds.
- Default: Specialist net (after commission splits, current behaviour).
- Values / limits: Specialist net or Client payment sum (what clients paid, before commission).
- When to change it: choose the client sum if specialists compare prices with other platforms.
Count specialist-initiated late rescheduling toward the yellow card
- Where: Reliability → Cabinet & rules → Reliability rules. "Changing these rules does not rewrite past yellow cards — only the next recalculation."
- What it does: When on, a session the specialist moved late (and the client accepted) counts toward Specialist late cancellations. A moved group meeting counts once, not once per participant. When off, only late cancellations count.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if your specialists often move sessions at clients' informal request.
- Related: Specialist late cancellations — from
Do not count seats cancelled by a cancelled group meeting
- Where: same section
- What it does: When on, seats cancelled because the whole group meeting was cancelled do not count as the specialist's late cancellations. A single seat the specialist cancelled earlier still counts.
- Default: off. A site plugin can fix this value; the box is then greyed out with "Set by site policy."
- Values / limits: on / off.
- When to change it: turn on if group meetings are often cancelled for lack of participants.
No-reply events
- Where: same section
- What it does: Which events count as "no reply" for the Overdue and No reply rules.
- Default:
expired_ttl(the request expired without a specialist decision). - Values / limits:
expired_ttlis currently the only token; other words are dropped. Leave empty to count none — then both rules never trigger.
Yellow card minimum life (days)
- Where: same section
- What it does: A card stays at least this many days even if the figures improve earlier. "0 = clear as soon as metrics fall below thresholds." A manual removal is not affected.
- Default: 0.
- Values / limits: 0–365.
- When to change it: 7 days so a card does not flicker on and off when a specialist hovers around a threshold.
Cabinet cache TTL (seconds)
- Where: Reliability → Cabinet & rules → Service (Службове)
- What it does: How long a specialist's computed statistics page is kept before it is recalculated. Booking and complaint changes clear the cache for the people involved earlier.
- Default: 300 (5 minutes).
- Values / limits: 0–86400; 0 = do not cache.
- When to change it: raise it (900–1800) on a large site where statistics pages load slowly; 0 while testing.
Reliability sweep interval (seconds)
- Where: same section
- What it does: How often the background task re-checks everyone's reliability, in addition to the immediate recalculation after each booking event.
- Default: 300 (5 minutes).
- Values / limits: 60–86400.
- When to change it: 900–3600 on shared hosting to reduce load.
Reliability sweep batch size
- Where: same section
- What it does: How many people one background pass recalculates before continuing in the next pass.
- Default: 40.
- Values / limits: 1–500.
- When to change it: lower it if background runs time out; raise it on a fast server with many specialists.
Sweep stale warning (seconds)
- Where: same section
- What it does: If the background task has not run for this long, the Reliability screens show "The background recalculation has not run for over N minutes. Ask a technical administrator to set up a server schedule (cron)."
- Default: 900 (15 minutes).
- Values / limits: 60–86400. Keep it above the sweep interval.
Page views
Where: Reliability → Page views (Перегляди сторінок) — managers and administrators
"Honest page-view counting and retention." Only normal page loads (GET requests) of public specialist profiles and service pages are counted; admin, AJAX, REST, feed and preview requests and requests without a browser user agent never count. Other ExpertPress modules can register their own page types into the same counter. Changes apply to new views only; past counts are not recalculated.
Deduplication (minutes)
- Where: Reliability → Page views → Honesty (Чесність підрахунку)
- What it does: "One counted view per visitor per page within this window." The visitor is recognised by the
ep_stats_vidcookie (see Privacy). - Default: 30.
- Values / limits: 0–10080 (one week). 0 = count every page load.
- When to change it: 1440 (one day) so a client comparing specialists all afternoon counts once per page per day.
Roles excluded from the count
- Where: same section
- What it does: Signed-in users with any of these WordPress roles are not counted.
- Default:
administrator,expertpress_manager,expertpress_moderator,expertpress_accountant. - Values / limits: one role slug per line or comma-separated. An empty field excludes nobody.
- When to change it: add
editororauthorif your content team browses profiles often.
Do not count the specialist viewing their own page or service
- Where: same section
- What it does: A signed-in specialist's visits to their own profile and services are not counted.
- Default: on.
- Values / limits: on / off.
Count views from logged-in clients (on by default)
- Where: same section
- What it does: When off, no signed-in user is counted at all — only guests. When on, signed-in users count unless excluded by role or as the page owner.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if most traffic from signed-in users is your own testing.
Bot user agents
- Where: same section
- What it does: "One token per line. Requests whose User-Agent contains any token are not counted." Matching ignores letter case.
- Default:
bot,crawl,spider,slurp,facebookexternalhit,preview,curl/,wget,python-requests,httpclient,headless,googlebot,bingbot,yandex,baiduspider. - Values / limits: any text tokens. If you save an empty field, the default list is restored.
- When to change it: add a monitoring service that loads your pages regularly (for example
uptimerobot).
Hourly page views (days)
- Where: Reliability → Page views → Retention (Зберігання)
- What it does: How long hourly view counts are kept. On current core versions this period is managed on Settings → Data retention as Hourly page views; this tab then shows the current period and a Data retention link instead of an input.
- Default: 0 = keep forever.
- Values / limits: 0–36500 days (on the core screen: 1–36500 days or 1–1200 months, or keep indefinitely). Older hours are deleted in background batches; existing totals are not recalculated, so old periods simply show fewer views.
- When to change it: 730 days to keep two years of history for comparisons and drop the rest.
Reliability journal (days)
- Where: same section
- What it does: How long automatic reliability history is kept. On current core versions managed on Data retention as Reliability history. Active cards and records still needed for complaints or the dossier are kept.
- Default: 0 = keep forever.
- Values / limits: 0–36500 days (core screen: as above).
- When to change it: set a period that matches your privacy policy, for example 365 days.
- Related: Data retention also lists Settings version history and Manual yellow card removals for this module; see Privacy and data storage.