About this plugin
Lightweight, privacy-conscious activity logger. Relate pageviews and events to visitors, browsers, devices, sources and other context.
Quantely Activity is built to capture activity reliably under imperfect conditions through server-side recording and optional client-side signals, while supporting filtering for bots, unwanted pages, IP sources and selectable WordPress logged-in roles.
Quantely Activity can be used for:
- Monitoring site behavior
- Reviewing traffic patterns
- Security and bot analysis
- Feeding downstream analytics layers
Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after. Raw activity data is retained for a configurable short period, helping keep the plugin lightweight and privacy-conscious.
What Quantely Activity is
Quantely Activity is a capture and monitoring layer. It is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity.
Unlike many analytics tools, it does not focus on marketing analytics, attribution modelling, or behavioral profiling. It also does not rely solely on browser JavaScript. A server-side baseline helps ensure pageviews are still captured when scripts or beacons fail.
Hybrid capture engine
The plugin combines server-side pageview capture with optional browser-side signals.
Typical flow:
Browser request
↓
Server pageview baseline
↓
Browser attach (Beacon)
– engagement pings
– interaction events
↓
Correlation via pageview identifiers
↓
Bot classification and exclusions
↓
Deduplication and storage
This architecture helps keep capture reliable under real-world conditions where browser-only tracking can miss signals.
Event correlation and deduplication
Quantely Activity links browser-side signals back to the pageview where they occurred.
Engagement pings, clicks, form submissions, and similar events can be correlated to their originating pageview. Built-in deduplication helps avoid duplicate records when similar signals are captured from both browser and server-side sources.
This keeps the activity stream more accurate and easier to interpret.
Fully on-site
Captured activity is stored in your own WordPress database. By default, Quantely Activity does not send captured activity to external services. If the optional Geography integration is enabled, human visitor IP addresses are sent to MaxMind GeoLite solely to obtain a country code.
Plain IP addresses are never stored by Quantely Activity, and the plugin does not perform cross-site tracking.
Privacy-aware design
The plugin is designed with privacy-conscious principles in mind:
- No plain IP addresses stored
- Short configurable retention window
- Optional honoring of GPC / DNT signals
- No external tracking services by default
- Optional country enrichment through MaxMind GeoLite, explicitly enabled by the administrator
- Activity data remains in your own WordPress database
This gives site owners visibility into activity while keeping capture local and controlled.
Hooks
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.
External services
Quantely Activity works without external services by default.
If an administrator enables Geography, the plugin can connect to the MaxMind GeoLite Country web service. For hits classified as human, the visitor IP address is sent to MaxMind so MaxMind can return country-level information. Quantely Activity stores only the resulting two-letter country code and does not store the plain IP address.
Non-human hits are not enriched. Lookup results are cached using Quantely’s existing hashed IP value to reduce repeated requests.
The integration requires a MaxMind account ID and license key. These credentials are stored in the WordPress options table. The license key is not displayed again after it is saved.
Service provider: MaxMind, Inc.
com/en/geolite2/
com/en/privacy-policy
com/en/geolite/eula
com.