Description
Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).
It helps site owners understand what is happening on their website for monitoring, diagnostics, performance checks, and analytics validation. It also makes this data available to downstream analytics tools.
Quantely Activity runs fully on-site, uses no external services, stores data only briefly, supports cookie-free operation, does not depend on JavaScript, and does not store plain IP addresses.
Key features
Robust traffic monitoring
Quantely Activity captures activity reliably under imperfect conditions.
- Server-side pageview capture (always-on baseline)
- Optional browser signals (clicks, forms, engagement)
- Server-side event capture from plugins, including WooCommerce
- Server and browser alignment via
pv_id - Receive-order recording with preserved origin metadata
- Lightweight deduplication of duplicate signals
Traffic context
Each hit is enriched with context for interpretation and downstream use.
- UTM parameters (
utm_source,utm_medium, etc.) - Click IDs (e.g.
gclid,fbclid) - Channel classification (email, paid, social, ai, search, referral, direct, internal)
- Visitor continuity via cookies and derived identifiers
Engagement signals
Engagement is captured efficiently using milestone-based signals.
- One maximum engagement value per pageview
- Fibonacci-based milestones (
2–89 seconds) - No continuous timers or heavy scripts
Internal traffic filtering
Internal or irrelevant traffic can be excluded without losing visibility.
- Role-based exclusions (e.g. admins)
- IP-based exclusions
- Path-based exclusions
- Hits remain visible but are marked (
is_excluded)
Bot filtering
Automated traffic is detected and classified at capture time.
is_nonhuman,bot_label,bot_reason- Detection based on patterns, endpoints, and behavior
- Reclassification possible as patterns emerge
Privacy
Designed to minimize data exposure and keep control local.
- No plain IP storage
- Short retention window
- GPC / DNT support
- No external tracking services
- Data stored fully on-site
Integrations
Captured data is structured so other tools can use it.
- Activity data can feed downstream analytics tools
- Events remain connected to their original page context
- Compatible with analytics and processing workflows
Quantely Activity exposes a small developer API for integrations and downstream processing.
qmon_hit_before_insert— Filter a normalized hit array before it is stored.qmon_hit_recorded— Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.qmon_event_normalize— Filter a normalized event payload before it is finalized.qmon_event_db_dedupe_window_sec— Filter the database deduplication window for events.qmon_bot_verdict— Filter the bot-classification verdict before it is finalized.
Screenshots
Installation
- Upload the plugin ZIP via WordPress Admin Plugins Add New Upload Plugin
- Activate the plugin
- Open Quantely Activity to confirm that hits are being recorded
- Adjust settings if needed
FAQ
-
What does Quantely Activity record?
-
It records pageviews and interaction events as individual hits.
-
Does it replace analytics tools?
-
No. Quantely Activity is a capture and monitoring layer. It is not a marketing analytics suite and does not aim to replace long-term analytics reporting.
-
Is JavaScript required?
-
No. Server-side capture records pageviews without JavaScript. Browser-side JavaScript extends capture with interaction events and engagement pings.
-
How long is data stored?
-
Raw hits are stored only for a short configurable period, typically between 6 and 48 hours. The plugin is intended for monitoring and diagnostics rather than long-term data warehousing.
-
Does it store IP addresses?
-
No. Plain IP addresses are not stored. The plugin uses derived or hashed values where needed for classification and exclusion logic.
-
Does it send data to external services?
-
No. Captured activity is stored locally in the WordPress database.
Reviews
Contributors & Developers
“Quantely Activity” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Quantely Activity” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.4
- Shows whether the visitor cookie is active in the Activity table.
1.1.3
- Updated the plugin readme with clearer positioning, new tags, and revised feature descriptions.
1.1.2
- Replaced the visible IP (hashed) column in the Activity table with Actor key.
- Added default excluded URL parts for common account and authentication paths.
1.1.1
- Added a separate Date column to the Activity table.
1.1.0
- quant_visit now uses a 35-day lifetime with sliding expiration.
- visitor_key remains a coarse cookie-less fallback, without monthly rotation.
- Fixed an admin warning in Diagnostics by replacing an undefined variable in the 24-hour pv_id check.
1.0.4
- Review hardening for WordPress.org submission
- Improved sanitization, validation, escaping, and internationalization coverage
- Improved REST input sanitization and related code quality refinements
1.0.3
- Improved event correlation and deduplication behavior
- Expanded diagnostics and integration-related improvements
1.0.2
- Refinements to monitoring, exclusions, and settings behavior
- Stability and compatibility improvements
1.0.1
- Minor fixes and internal improvements
1.0.0
- Initial version prepared during pre-release review.





