內容簡介
Quantely 是一款以隱私為首的 WordPress 分析外掛，無需使用 cookies 或第三方連結，能夠即時追蹤網站流量來源、頁面瀏覽及轉換路徑，並提供詳細報告，幫助網站擁有者了解訪客行為。
【主要功能】
• 無需 cookies 的流量分析
• 詳細的來源、渠道與活動報告
• 排除機器人及特定用戶流量
• 可導出 CSV 格式的報告
• 支援多種時間範圍的數據查詢
外掛標籤
開發者團隊
② 後台搜尋「Quantely – Privacy-first WordPress Analytics」→ 直接安裝（推薦）
原文外掛簡介
See which sources bring meaningful visits, which pages people view, the paths they take and where they convert—without cookies, visitor profiles or third-party connections. Quantely runs entirely inside WordPress and starts collecting immediately.
Reports can be broken down by source, channel, campaign (UTM) and device. Traffic from bots, administrator-selected logged-in user roles and user-defined IP addresses or ranges is excluded.
Quantely does not set analytics cookies, count or profile visitors, expose a public integration API or send analytics data to a third party.
Analytics
The Analytics page contains three reports:
Overview — a monthly sessions and conversion-rate chart, qualified, converted and all-session metrics, filters, a year selector and a rolling twelve-month Average.
Pages — pageviews, median active time, sessions, entry rate and exit rate for qualified sessions.
Journeys — grouped page sequences for qualified sessions, sortable by sessions or journey length.
Device, Channel, Source and Campaign are shared across the three Analytics reports and Traffic, and saved per administrator. Applying them on any of these pages updates the same selection everywhere. Year is saved with them but only applies to Overview. Pages, Journeys and Traffic keep their report-specific controls local and temporary. Pages and Journeys offer 7- and 30-day time windows, plus 90, 180 and 365 days when supported by the configured history retention.
Overview can be exported as a UTF-8 CSV file using the filters currently applied.
The Overview chart shares its month labels with the first table and always shows qualified sessions for the selected year across all devices, channels, sources and campaigns. Blue bars show sessions, and a solid sand-colored line shows the total conversion rate. The total series keep their normal colors with or without shared filters. When any Device, Channel, Source or Campaign filter is active, alone or in combination, a lighter blue area marks the selected-session portion inside each bar and a thinner, lighter sand-colored line shows the selected conversion rate. Both conversion lines are solid, with subtle outlines and no monthly point markers. The vertical legend sits to the left of the plot, above the first two table columns. Qualified sessions and Conversion rate each have Totals and Selected controls underneath; both numeric scales sit close together beside the legend without repeated scale titles. Both conversion rates share the same percentage scale. Each rate uses its own qualified-session denominator and counts each converted session once, even when it completes multiple types. Conversion lines appear when at least one conversion type is configured. The tables and CSV export follow the active filters, and the rolling Average stays outside the graph. Hovering a month shows only the visible graph values: qualified sessions and conversion rate, including the selection when filters are active. Use the legend to show or hide each series and the monthly tables for the full report.
Traffic has its own Quantely > Traffic page with recent raw captures, page-level active-time milestones, capture method, actor, browser, device, hashed IP, attribution, UTMs and bot assessment. Actor pills distinguish excluded, human and automatic traffic. Actor and Path or IP contains are applied separately inside the Traffic panel. When a retained session is classified as nonhuman, every Traffic row linked to that session is displayed as automatic traffic while the raw request evidence remains unchanged.
Configured conversion snippets are used for conversion matching. The WordPress Dashboard widget shows qualified sessions for the current and previous five months and, when configured, the conversion rate.
Sessions and qualification
An optional daily rotating first-party fingerprint connects pageviews into sessions. The session gap determines when a new session starts.
A session qualifies when it reaches two or three pageviews, reaches an enabled visible-time threshold of 2, 3, 5 or 8 seconds, or converts. Pageview and time qualification can be enabled independently; conversion qualification is automatic.
Engagement
Optional engagement measurement records the highest visible-time milestone reached per pageview: 2, 3, 5, 8, 13, 21, 34, 55 or 89 seconds. Hidden-tab time is ignored and no continuous heartbeat is sent.
Pages reports median active time. Overview can show active time and session duration. These metrics remain hidden when engagement measurement is disabled.
Conversions and attribution
Up to three conversion types can be defined and named by the administrator. Each type has up to three alternatives joined with OR. Within each alternative, up to three case-insensitive URL-path snippets are joined with AND. Every filled snippet in one alternative must occur in the session; matching any alternative completes that type.
The configured names are used in the separate Converted sessions table on Overview and in the Journeys conversion filter. Overview shows newly defined conversions by default. Each visible type has a session-count row followed by its own conversion-rate row, including the rolling Average. When multiple types are configured, Sessions with conversion has the same two-row layout for the deduplicated total. Journeys can show all sessions, sessions with any conversion or sessions with a specific configured type; the Any conversion option appears only when multiple types are active. Completing any active type automatically qualifies the session.
Acquisition attribution is stored at session level. The Channel filter offers Organic as a combined selection for Search, Referral, Social and AI, while retaining each channel as an individual choice. Organic sources use referrer domains; Paid and Email sources prefer captured utm_source values. Campaign is an independent filter based only on captured utm_campaign, so one campaign can span multiple channels. Ordered rules under Quantely > Settings > Channels can override classification using referrer hosts or UTM values.
Capture, bots and privacy
Server-side capture and the JavaScript pageview fallback are enabled by default. The browser fallback can recover pageviews when full-page caching bypasses WordPress; server and browser captures are deduplicated. Browser prefetch and prerender requests are ignored until a page is actually activated.
Deterministic user-agent signatures plus request- and session-level heuristics classify traffic. Bot sessions are excluded from analytical reports. Administrators can optionally enable Journey review controls and mark retained Journey groups as bots, immediately correcting Overview, Pages and Journeys without altering Traffic.
Analytics data remains in the WordPress database.
No analytics cookies or third-party analytics endpoints are used.
Plain IP addresses, WordPress user IDs and roles are not retained in Traffic.
IP hashes are shortened with the plugin’s local secret.
No persistent visitor history or visitor count is produced.
Global Privacy Control and Do Not Track are honored by default.
Configuration
Publication defaults
New installations enable the JavaScript pageview fallback, time qualification at 3 seconds, engagement measurement and daily rotating session fingerprinting. Pageview qualification uses a two-page threshold. Journey removal remains disabled, and GPC and DNT headers are honored.
Disabling session fingerprinting makes every pageview a separate session, so multi-page qualification and Journeys cannot connect pageviews across a visit.
Retention, exclusions and languages
Raw Traffic retention: 6, 12, 24 or 48 hours.
Session, Page and Journey retention: 30, 90, 180 or 365 days.
Exclusions can match logged-in roles, IP addresses, CIDR ranges and path fragments.
The interface includes English, Dutch, German, French, Italian, Spanish and Portuguese, with optional label overrides.
Data storage
Quantely uses three WordPress database tables: the short-retention traffic stream, retained sessions and their ordered pages. Reports are calculated directly from retained session data. Status summarizes collection, database readiness, data integrity and automatic cleanup; technical storage and bot details remain available under Advanced diagnostics.
The Data tab can purge retained page and Journey detail while preserving session summaries, or reset all Quantely Analytics data and settings. By default, uninstalling preserves stored data and settings; enable the uninstall cleanup option on the Data tab to remove all dedicated tables and settings without leaving a trace. Deactivation preserves data.
