Quantely Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Quantely records first-party page requests and reports traffic, sessions, pages, journeys and conversions inside WordPress. Learn more at https://www.erravi.com/quantely/.
It does not set analytics cookies, produce visitor totals, collect arbitrary interaction events, expose a public integration API or send analytics data to a third party.
Analytics
The Analytics page contains three reports:
- Overview — monthly 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 reports and saved per administrator. Year is saved with them but only applies to Overview. Pages and Journeys keep their report-specific controls local and temporary.
Traffic has its own Quantely > Traffic page with recent raw captures, capture method, actor, browser, device, hashed IP, attribution, UTMs and bot assessment.
Configured conversion snippets are used for conversion matching without visually marking paths in Pages or Journeys. 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
One conversion type can be defined and named by the administrator. It 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 the type.
The configured name is used in the separate Converted sessions table on Overview and in the Journeys conversion filter. Overview shows a newly defined conversion by default and reports its session count and conversion rate, plus the overall converted-session total. Journeys can show all sessions or sessions with the configured type; an Any conversion option appears only when multiple types are active. Completing the 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.
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.
Uninstalling the plugin through WordPress removes its settings, scheduled task and dedicated tables. Deactivation alone preserves data.
Screenshots
No screenshots provided
