Title: Quantely – Privacy-first WordPress Analytics
Author: erravi
Published: <strong>25, Setiembre de 2026</strong>
Last modified: 4, Ochobre de 2026

---

Guetar plugins

![](https://ps.w.org/quantely-lite/assets/icon-256x256.png?rev=3727766)

# Quantely – Privacy-first WordPress Analytics

 By [erravi](https://profiles.wordpress.org/erravi/)

[Download](https://downloads.wordpress.org/plugin/quantely-lite.1.1.3.zip)

 * [Details](https://ast.wordpress.org/plugins/quantely-lite/#description)
 * [Reviews](https://ast.wordpress.org/plugins/quantely-lite/#reviews)
 *  [Installation](https://ast.wordpress.org/plugins/quantely-lite/#installation)
 * [Development](https://ast.wordpress.org/plugins/quantely-lite/#developers)

 [Support](https://wordpress.org/support/plugin/quantely-lite/)

## Description

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.

## Screenshots

[⌊Overview — View monthly qualified sessions, pageviews and conversions with shared
filters and selectable metrics.⌉⌊Overview — View monthly qualified sessions, pageviews
and conversions with shared filters and selectable metrics.⌉[

**Overview** — View monthly qualified sessions, pageviews and conversions with shared
filters and selectable metrics.

[⌊Pages — Compare pageviews, active time, sessions, entry rates and exit rates for
qualified sessions.⌉⌊Pages — Compare pageviews, active time, sessions, entry rates
and exit rates for qualified sessions.⌉[

**Pages** — Compare pageviews, active time, sessions, entry rates and exit rates
for qualified sessions.

[⌊Journeys — Explore grouped page sequences and filter sessions by path or conversion
type.⌉⌊Journeys — Explore grouped page sequences and filter sessions by path or 
conversion type.⌉[

**Journeys** — Explore grouped page sequences and filter sessions by path or conversion
type.

[⌊Traffic — Review recent requests, page-level active time, attribution, capture
details and bot assessment.⌉⌊Traffic — Review recent requests, page-level active
time, attribution, capture details and bot assessment.⌉[

**Traffic** — Review recent requests, page-level active time, attribution, capture
details and bot assessment.

[⌊Collection — Configure qualification, engagement, capture, privacy and data retention.⌉⌊
Collection — Configure qualification, engagement, capture, privacy and data retention
.⌉[

**Collection** — Configure qualification, engagement, capture, privacy and data 
retention.

[⌊Conversions — Name up to three conversion types and define their URL-path matching
rules.⌉⌊Conversions — Name up to three conversion types and define their URL-path
matching rules.⌉[

**Conversions** — Name up to three conversion types and define their URL-path matching
rules.

[⌊Language — Select an interface language and optionally override individual labels.⌉⌊
Language — Select an interface language and optionally override individual labels
.⌉[

**Language** — Select an interface language and optionally override individual labels.

[⌊Exclusions — Exclude selected user roles, IP addresses, IP ranges and path fragments.⌉⌊
Exclusions — Exclude selected user roles, IP addresses, IP ranges and path fragments
.⌉[

**Exclusions** — Exclude selected user roles, IP addresses, IP ranges and path fragments.

## Installation

 1. Upload the plugin zip through **Plugins > Add New > Upload Plugin**, or copy the`
    quantely-lite` directory to `/wp-content/plugins/`.
 2. Activate **Quantely**. Collection starts immediately with privacy-first recommended
    defaults.
 3. Select **Start setup** in the welcome notice to confirm collection, choose role
    and IP exclusions, optionally define a first conversion and select the interface
    language.
 4. Generate one logged-out test session. Quantely shows collection progress until 
    the first qualified session is available. Administrators can also close this progress
    guide permanently for their own account.
 5. Review the complete configuration later under **Quantely > Settings**.

Updates preserve the existing `flow_*` settings and retained analytics data.

## FAQ

### Does Quantely use cookies?

No. Quantely does not set analytics cookies.

### Does Quantely count visitors?

No. It deliberately reports requests, sessions, page statistics and journeys without
creating visitor statistics or persistent visitor histories.

### Why can a request appear in Traffic but not in Pages or Journeys?

Traffic is the short-retention request log. A request may be excluded, classified
as a bot or belong to an unqualified session. Pages and Journeys only use qualified,
non-excluded human sessions.

### Why is Journeys empty?

Check that session fingerprinting is enabled, at least one qualification method 
is enabled, the selected device and channel filters match, and the test request 
is not excluded by role, path or IP. Test while logged out or in a private browser
window.

### Can Quantely measure a single-page session duration without browser signals?

No. Server timestamps alone cannot establish how long a visitor viewed a single 
page. Enable engagement measurement when active-time and duration metrics are needed.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Quantely – Privacy-first WordPress Analytics” is open source software. The following
people have contributed to this plugin.

Contributors

 *   [ erravi ](https://profiles.wordpress.org/erravi/)

[Translate “Quantely – Privacy-first WordPress Analytics” into your language.](https://translate.wordpress.org/projects/wp-plugins/quantely-lite)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/quantely-lite/), check
out the [SVN repository](https://plugins.svn.wordpress.org/quantely-lite/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/quantely-lite/) 
by [RSS](https://plugins.trac.wordpress.org/log/quantely-lite/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.1.3

 * Added a permanent, per-administrator close button to the first-qualified-session
   guide. The preference survives plugin updates and requires an authorized, nonce-
   protected request.
 * Replaced the eye icon in the WordPress admin menu with the standard bar-chart
   icon.
 * Added 180- and 365-day windows to Pages and Journeys when the configured history
   retention supports them. Report and Journey-review windows cannot exceed retained
   history.
 * Localized report-window labels and the close-button label in all bundled languages.
 * Preserved analytics data, settings, the Overview chart, conversion calculations
   and the separate conversion-rate rows; no database migration is required.

#### 1.1.2

 * Added a monthly Overview chart using Quantely’s favicon colors, with qualified-
   session bars and deduplicated conversion-rate lines when conversions are configured.
 * Kept total qualified sessions and conversion rate visible across all traffic 
   for the selected year; active Device, Channel, Source and Campaign filters add
   a selected-session portion inside the bars and a selected conversion-rate line,
   including combinations of filters.
 * Used blue for session bars and sand for solid conversion-rate lines, with subtle
   outlines and no monthly point markers. Totals keep their normal colors with or
   without shared filters. Selected sessions use a lighter blue area inside the 
   bars, and the selected conversion rate uses a thinner, lighter sand-colored line.
   Placed a vertical legend to the left of the plot, with Totals and Selected controls
   underneath Qualified sessions and Conversion rate. Kept both scales compact on
   the left and removed repeated scale titles.
 * Aligned the graph to the first table’s month columns, sharing one set of month
   labels and keeping the rolling Average outside the graph.
 * Preserved filtered tables, rolling averages and CSV export calculations. Each
   conversion rate uses its own qualified-session denominator; the chart comparison
   uses one additional monthly query only while a shared filter is active and requires
   no external chart libraries.
 * Added responsive column alignment, independent keyboard-accessible legend controls
   and all bundled translations. Monthly values remain available to screen readers.
   Hover details contain only visible session and conversion-rate values.
 * Preserved missing months and undefined conversion rates as gaps instead of displaying
   fabricated zeroes.
 * Placed conversion rates on separate rows below each visible conversion type and
   the Sessions with conversion total, for every month and the rolling Average.

#### 1.1.1

 * Repositioned the WordPress.org listing around privacy-first WordPress analytics,
   clearer search terms and the core Sources, Pages, Journeys and Conversions outcomes.
 * Added a four-step first-run setup guide for collection defaults, logged-in role
   exclusions, optional current-IP exclusion, an optional first conversion and interface
   language.
 * Added a first-success panel that confirms collection and explains exactly how
   to create the first qualified session.
 * Added a nonce-protected UTF-8 CSV export beside the Overview Metrics control,
   using the shared filters currently applied.
 * Protected exported text cells against spreadsheet-formula execution.
 * Preserved existing settings and analytics data; the setup guide is shown only
   on new installations or when opened manually from Collection.
 * Removed the unintended space between the Overview Metrics and Export CSV buttons.
 * Simplified the report period selector so the active period is plain text while
   the alternatives remain links.
 * Right-aligned the Journeys period selector to match Pages.
 * Added blue, green and red Actor pills for excluded, human and automatic Traffic,
   with matching Actor filters.

#### 1.1.0

 * Added page-level Active time (s) to Traffic when engagement measurement is enabled;
   each row shows its highest retained milestone or a dash before the first signal.
 * Prevented browser prefetch, prerender and other non-navigation HTML requests 
   from being recorded as pageviews, and delayed browser capture until a prerendered
   document is activated.
 * Made Traffic display and filter by the effective session actor, including a clear
   assessment when bot status is inherited from the retained session.
 * Gave active shared filters a subtle light-blue state across Analytics and Traffic
   while filters set to Any remain neutral.
 * Moved the Overview Metrics control below the visible tables and made the Overview,
   Pages and Journeys tabs equally wide.
 * Preserved all existing analytics data, report calculations and saved selections;
   no database migration is required.

#### 1.0.30

 * Added a one-time first-install notice confirming that collection has started 
   and linking directly to conversion setup.
 * Added practical confirmation-page and multi-page conversion examples to the notice.
 * Shortened the WordPress.org Short Description to stay within the 150-character
   limit.
 * Added a Data settings tab for purging retained session detail, resetting Quantely
   Analytics and controlling uninstall cleanup.
 * Added explicit confirmation prompts and protected all destructive data actions
   with administrator permissions and nonces.
 * Renamed the first Settings tab to Collection and reordered the tabs to Collection,
   Exclusions, Conversions, Channels, Language, Data and Status.
 * Shared the saved Device, Channel, Source and Campaign filters between Analytics
   and Traffic so applying them on either page updates the other reports.
 * Kept Traffic’s Path or IP contains and Actor controls local and temporary under
   their own blue Apply action.

#### 1.0.20

 * Expanded the active conversion configuration from one to three independently 
   named types while retaining three OR alternatives of up to three AND snippets
   per type.
 * Added extension hooks for Quantely add-ons without changing the default Lite 
   interface.
 * Added reserved country-code storage and report filtering support for optional
   extensions.
 * Made the number of exposed conversion slots extensible while Lite continues to
   expose three by default.
 * Rebuilt retained conversion state during the schema 19 upgrade so newly active
   and extension-provided types appear consistently in Overview and Journeys.

#### 1.0.19

 * Reworked the short and detailed plugin descriptions to explain visit metrics,
   breakdowns and exclusions more clearly.
 * Updated captions for the eight WordPress.org screenshots.

#### 1.0.18

 * Enabled browser fallback, three-second time qualification, engagement measurement
   and session fingerprinting by default for new installations.
 * Marked session fingerprinting as highly recommended in Settings. Existing saved
   settings remain unchanged.

#### 1.0.17

 * Kept conversion counts and whole-number rates on one line in Overview and tightened
   metric-table spacing.
 * Added eight screenshot captions for future WordPress.org assets.

#### 1.0.16

 * Clarified plural translations and explicit output escaping for Overview metrics.
 * Documented the verified nonce boundary for Channel settings and shortened a historical
   upgrade notice.

#### 1.0.15

 * Hid the redundant Sessions with conversion total on Overview when exactly one
   conversion type is configured.

#### 1.0.14

 * Published under the Quantely product name, with product information at https://
   www.erravi.com/quantely/.
 * Updated the plugin listing and documentation; tracking, reports, settings and
   stored data are unchanged.

#### 1.0.13

 * Replaced the technical-first Diagnostics tab with a reassurance-first Status 
   view and collapsed Advanced diagnostics.
 * Compared the installed and required schemas, added duplicate-pageview-ID checks
   and summarized collection, integrity, cleanup and retention health.
 * Made newly defined conversion metrics visible on Overview by default while preserving
   later user choices.
 * Hid the redundant Any conversion Journey option when only one conversion type
   is active.
 * Removed conversion-path highlighting from Pages and Journeys without changing
   conversion matching or filtering.

#### 1.0.12

 * Added a selectable Organic aggregate across analytics reports, combining Search,
   Referral, Social and AI while retaining the four individual channel filters.

#### 1.0.11

 * Restyled the shared analytics action as a quieter Filter button.
 * Moved the Overview metric Apply action into the Metrics flyout.

#### 1.0.10

 * Moved the saved Device, Channel, Source and Campaign controls above the report
   panels and shared them across Overview, Pages and Journeys; Year remains Overview-
   only.
 * Kept Pages and Journeys report-specific controls inside their panels with independent,
   temporary Apply actions.
 * Shortened the Pages entry/exit basis and Campaign defaults while retaining qualified-
   session-only rate calculations.
 * Gave every numeric Pages metric column an equal width.

#### 1.0.9

 * Kept the rolling conversion rate empty when no conversion type is configured 
   instead of reporting zero.
 * Registered the purge callback directly during plugin bootstrap so hourly retention
   cleanup always has its handler.

#### 1.0.8

 * Moved Traffic from the Analytics tabs to its own Quantely administration page
   while redirecting old Traffic-tab links.
 * Moved channel override rules to a dedicated Channels settings tab.
 * Added a default-disabled setting that controls Journey selection and manual session
   removal, with server-side enforcement.
 * Limited the interface to one active conversion type with three OR alternatives
   while preserving the four hidden type definitions for a future release.
 * Rebuilt retained conversion state during the schema 17 upgrade so hidden types
   and alternatives no longer affect reports.

#### 1.0.7

 * Centralized conversion slot limits, column names and Journey filter validation
   in the settings model.
 * Removed duplicate filter normalizers and obsolete single-rule conversion labels
   without changing stored data, schema or report behavior.
 * Retained automatic migration of earlier conversion settings and grouped-rule 
   path highlighting.

#### 1.0.6

 * Added five independently named conversion types, each with five OR alternatives
   of up to three AND URL snippets.
 * Added a separate Overview table with counts and qualified-session conversion 
   rates for each configured type and a deduplicated any-conversion total.
 * Added Journeys filtering for all sessions, any conversion or a specific user-
   named conversion type.
 * Preserved the configured conversion labels across settings, Overview and Journey
   filters.
 * Migrated the previous single conversion rule into the first named type and retained
   compatibility for companion tools using the legacy flattened rule interface.

#### 1.0.5

 * Added an independent Campaign filter based strictly on captured `utm_campaign`
   values.
 * Applied Campaign filtering to Traffic, Overview, Pages, Journeys and Journey 
   bot review.
 * Made Overview calendar-month grouping independent of the database session timezone.
 * Restored a missing hourly purge schedule automatically while retaining a single
   registered callback.
 * Cleared derived qualification, conversion and Journey state whenever a session
   is excluded or classified as non-human.

#### 1.0.4

 * Grouped Search, Referral, Social and AI under Organic in report filters.
 * Added source filtering from captured referrer domains and UTM sources for Organic,
   Email and Paid channels.
 * Recognized common email providers from captured source and referrer signals.

#### 1.0.3

 * Made session assembly atomic under concurrent page requests.
 * Added unique pageview-ID and session-position constraints with idempotent retry
   handling.
 * Added a one-time repair of retained duplicate IDs, overlapping sessions, page
   positions and session counters.

#### 1.0.2

 * Propagated scanner evidence from any request to its complete session.
 * Added deterministic detection of rapid unique-path enumeration by disguised crawlers.
 * Added a one-time reclassification of retained scanner and crawler sessions.
 * Expanded common automation user-agent detection while preserving standard WordPress
   PHP endpoints.

#### 1.0.1

 * Centralized nonce and administrator capability checks before processing settings
   and Journey review requests.
 * Added explicit nonce and capability validation when saving Overview metric preferences.
 * Restricted the anonymous browser-capture REST route to validated first-party 
   requests and added strict payload validation.
 * Removed the unavailable Plugin URI from the plugin header.

#### 1.0.0

 * Initial release of Quantely.
 * Added first-party Traffic, Overview, Pages and Journeys reports.
 * Added qualified sessions, conversions, attribution, exclusions and deterministic
   bot analysis.
 * Added optional browser capture, visible-time qualification, engagement milestones
   and session fingerprinting.
 * Added manual Journey bot classification and WordPress Dashboard reporting.
 * Added multilingual administration and configurable label overrides.
 * Removed unused daily aggregate tables and six unconsumed Traffic fields to reduce
   writes and storage.

## Meta

 *  Version **1.1.3**
 *  Last updated **2 díes ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.2**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/quantely-lite/)
 * Tags
 * [analytics](https://ast.wordpress.org/plugins/tags/analytics/)[google analytics](https://ast.wordpress.org/plugins/tags/google-analytics/)
   [privacy](https://ast.wordpress.org/plugins/tags/privacy/)[statistics](https://ast.wordpress.org/plugins/tags/statistics/)
   [website statistics](https://ast.wordpress.org/plugins/tags/website-statistics/)
 *  [Advanced View](https://ast.wordpress.org/plugins/quantely-lite/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/quantely-lite/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/quantely-lite/reviews/)

## Contributors

 *   [ erravi ](https://profiles.wordpress.org/erravi/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/quantely-lite/)