Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
Quantely Activity captures activity reliably under imperfect conditions.<\/p>\n\n
pv_id<\/code><\/li>\n- Receive-order recording with preserved origin metadata<\/li>\n
- Lightweight deduplication of duplicate signals<\/li>\n<\/ul>\n\n
Traffic context<\/h4>\n\n
Each hit is enriched with context for interpretation and downstream use.<\/p>\n\n
\n- UTM parameters (
utm_source<\/code>, utm_medium<\/code>, etc.)<\/li>\n- Click IDs (e.g.
gclid<\/code>, fbclid<\/code>)<\/li>\n- Channel classification (email, paid, social, ai, search, referral, direct, internal)<\/li>\n
- Visitor continuity via cookies and derived identifiers<\/li>\n<\/ul>\n\n
Engagement signals<\/h4>\n\n
Engagement is captured efficiently using milestone-based signals.<\/p>\n\n
\n- One maximum engagement value per pageview<\/li>\n
- Fibonacci-based milestones (
2\u201389 seconds<\/code>)<\/li>\n- No continuous timers or heavy scripts<\/li>\n<\/ul>\n\n
Internal traffic filtering<\/h4>\n\n
Internal or irrelevant traffic can be excluded without losing visibility.<\/p>\n\n
\n- Role-based exclusions (e.g. admins)<\/li>\n
- IP-based exclusions<\/li>\n
- Path-based exclusions<\/li>\n
- Hits remain visible but are marked (
is_excluded<\/code>)<\/li>\n<\/ul>\n\nBot filtering<\/h4>\n\n
Automated traffic is detected and classified at capture time.<\/p>\n\n
\nis_nonhuman<\/code>, bot_label<\/code>, bot_reason<\/code><\/li>\n- Detection based on patterns, endpoints, and behavior<\/li>\n
- Reclassification possible as patterns emerge<\/li>\n<\/ul>\n\n
Privacy<\/h3>\n\n
Designed to minimize data exposure and keep control local.<\/p>\n\n
\n- No plain IP storage<\/li>\n
- Short retention window<\/li>\n
- GPC \/ DNT support<\/li>\n
- No external tracking services<\/li>\n
- Data stored fully on-site<\/li>\n<\/ul>\n\n
Integrations<\/h3>\n\n
Captured data is structured so other tools can use it.<\/p>\n\n
\n- Activity data can feed downstream analytics tools<\/li>\n
- Events remain connected to their original page context<\/li>\n
- Compatible with analytics and processing workflows<\/li>\n<\/ul>\n\n
Quantely Activity exposes a small developer API for integrations and downstream processing.<\/p>\n\n
\nqmon_hit_before_insert<\/code> \u2014 Filter a normalized hit array before it is stored.<\/li>\nqmon_hit_recorded<\/code> \u2014 Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.<\/li>\nqmon_event_normalize<\/code> \u2014 Filter a normalized event payload before it is finalized.<\/li>\nqmon_event_db_dedupe_window_sec<\/code> \u2014 Filter the database deduplication window for events.<\/li>\nqmon_bot_verdict<\/code> \u2014 Filter the bot-classification verdict before it is finalized.<\/li>\n<\/ul>\n\n\n\n- Upload the plugin ZIP via WordPress Admin \u2192 Plugins \u2192 Add New \u2192 Upload Plugin<\/strong><\/li>\n
- Activate the plugin<\/li>\n
- Open Quantely \u2192 Activity<\/strong> to confirm that hits are being recorded<\/li>\n
- Adjust settings if needed<\/li>\n<\/ol>\n\n\n
\nWhat does Quantely Activity record?<\/h3><\/dt>\nIt records pageviews and interaction events as individual hits.<\/p><\/dd>\n
Does it replace analytics tools?<\/h3><\/dt>\nNo. 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.<\/p><\/dd>\n
Is JavaScript required?<\/h3><\/dt>\nNo. Server-side capture records pageviews without JavaScript. Browser-side JavaScript extends capture with interaction events and engagement pings.<\/p><\/dd>\n
How long is data stored?<\/h3><\/dt>\nRaw 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.<\/p><\/dd>\n
Does it store IP addresses?<\/h3><\/dt>\nNo. Plain IP addresses are not stored. The plugin uses derived or hashed values where needed for classification and exclusion logic.<\/p><\/dd>\n
Does it send data to external services?<\/h3><\/dt>\nNo. Captured activity is stored locally in the WordPress database.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.1.4<\/h4>\n\n\n- Shows whether the visitor cookie is active in the Activity table.<\/li>\n<\/ul>\n\n
1.1.3<\/h4>\n\n\n- Updated the plugin readme with clearer positioning, new tags, and revised feature descriptions.<\/li>\n<\/ul>\n\n
1.1.2<\/h4>\n\n\n- Replaced the visible IP (hashed) column in the Activity table with Actor key.<\/li>\n
- Added default excluded URL parts for common account and authentication paths.<\/li>\n<\/ul>\n\n
1.1.1<\/h4>\n\n\n- Added a separate Date column to the Activity table.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- quant_visit now uses a 35-day lifetime with sliding expiration.<\/li>\n
- visitor_key remains a coarse cookie-less fallback, without monthly rotation.<\/li>\n
- Fixed an admin warning in Diagnostics by replacing an undefined variable in the 24-hour pv_id check.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Review hardening for WordPress.org submission<\/li>\n
- Improved sanitization, validation, escaping, and internationalization coverage<\/li>\n
- Improved REST input sanitization and related code quality refinements<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Improved event correlation and deduplication behavior<\/li>\n
- Expanded diagnostics and integration-related improvements<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Refinements to monitoring, exclusions, and settings behavior<\/li>\n
- Stability and compatibility improvements<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Minor fixes and internal improvements<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial version prepared during pre-release review.<\/li>\n<\/ul>","raw_excerpt":"See what is really happening on your WordPress website.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/274019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=274019"}],"author":[{"embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/erravi"}],"wp:attachment":[{"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=274019"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=274019"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=274019"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=274019"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=274019"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/fuc.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=274019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}