Title: Quantely Activity
Author: erravi
Published: <strong>Seeɗto 5, 2026</strong>
Last modified: Seeɗto 12, 2026

---

Search plugins

![](https://ps.w.org/quantely-activity/assets/banner-772x250.jpg?rev=3504450)

![](https://ps.w.org/quantely-activity/assets/icon-256x256.gif?rev=3499301)

# Quantely Activity

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

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

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

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

## 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

 * [[
 * Live activity stream
 * [[
 * Live activity stream II
 * [[
 * Simple counters
 * [[
 * Settings and privacy controls
 * [[
 * Exclusions and bot handling

## Installation

 1. Upload the plugin ZIP via **WordPress Admin  Plugins  Add New  Upload Plugin**
 2. Activate the plugin
 3. Open **Quantely  Activity** to confirm that hits are being recorded
 4. 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

![](https://secure.gravatar.com/avatar/d9c50e3fb8518bca8f0a9abf0c40765086bd501ed55f3e27fbe5bc1d783d3deb?
s=60&d=retro&r=g)

### 󠀁[Simple yet valuable](https://wordpress.org/support/topic/simple-yet-valuable-2/)󠁿

 [ruuddekeijzer](https://profiles.wordpress.org/ruuddekeijzer/) Seeɗto 5, 2026

I’ve been using Quantely Activity and really like how straightforward it is. It 
shows what’s happening on my site without loads of clutter or vague marketing stats.
What I find especially useful is that it helps spot real visitor activity as well
as bot noise. It feels lightweight, clear, and focused on what matters. For me, 
it’s one of those plugins that is simply handy to have.

 [ Read all 1 review ](https://wordpress.org/support/plugin/quantely-activity/reviews/)

## Contributors & Developers

“Quantely Activity” is open source software. The following people have contributed
to this plugin.

Contributors

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

[Translate “Quantely Activity” into your language.](https://translate.wordpress.org/projects/wp-plugins/quantely-activity)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/quantely-activity/),
check out the [SVN repository](https://plugins.svn.wordpress.org/quantely-activity/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/quantely-activity/)
by [RSS](https://plugins.trac.wordpress.org/log/quantely-activity/?limit=100&mode=stop_on_copy&format=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.

## Meta

 *  Version **1.1.4**
 *  Last updated **16 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **6.9.4**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/quantely-activity/)
 * Tags
 * [event tracking](https://fuc.wordpress.org/plugins/tags/event-tracking/)[pageviews](https://fuc.wordpress.org/plugins/tags/pageviews/)
   [user activity](https://fuc.wordpress.org/plugins/tags/user-activity/)[visitor tracking](https://fuc.wordpress.org/plugins/tags/visitor-tracking/)
   [website traffic](https://fuc.wordpress.org/plugins/tags/website-traffic/)
 *  [Advanced View](https://fuc.wordpress.org/plugins/quantely-activity/advanced/)

## Ratings

 5 out of 5 stars.

 *  [  1 5-star review     ](https://wordpress.org/support/plugin/quantely-activity/reviews/?filter=5)
 *  [  0 4-star reviews     ](https://wordpress.org/support/plugin/quantely-activity/reviews/?filter=4)
 *  [  0 3-star reviews     ](https://wordpress.org/support/plugin/quantely-activity/reviews/?filter=3)
 *  [  0 2-star reviews     ](https://wordpress.org/support/plugin/quantely-activity/reviews/?filter=2)
 *  [  0 1-star reviews     ](https://wordpress.org/support/plugin/quantely-activity/reviews/?filter=1)

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

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

## Contributors

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

## Support

Got something to say? Need help?

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