Quantely Activity

Quantely Activity is a lightweight capture layer that records pageviews and events. It helps site owners understand how visitors use their website.

Quantely Activity is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity. Whether JavaScript is blocked, networks are unreliable, redirects interfere, or traffic includes bots, scanners, and logged-in admins, it is built to capture activity reliably under imperfect conditions.

Quantely Activity does not focus on marketing analytics, attribution modelling, or behavioral profiling. Instead, it focuses on capturing reliable activity data that can also feed downstream analytics tools.

Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after.

Raw activity data is stored only briefly, helping keep the plugin lightweight and privacy-conscious.

Key features

1. Reliable capture

Quantely Activity prioritizes a dependable capture baseline before adding richer signals.

Server-side pageview capture (always-on baseline) Pageviews are recorded server-side, helping ensure capture even when JavaScript is blocked, networks are unreliable, or browser scripts fail.

Optional browser beacon collector (enhanced signals) A lightweight browser collector can send additional signals such as clicks, form submissions, and engagement pings.

Server-browser alignment Server and browser signals are aligned using a per-page-load pv_id. This allows pings and browser events to be associated with the correct pageview, even when browser signals arrive later than the server-side pageview.

Receive-order recording Hits are stored in the order they are received. Browser events may therefore appear after their related pageview when beacons arrive later. Origin metadata is preserved so downstream analytics tools can reconstruct the correct behavioral sequence.

2. Event origin metadata

Quantely Activity preserves origin metadata so downstream analytics tools can reconstruct user behavior more accurately.

Events may arrive later than their related pageviews, for example when browser beacons arrive after server-side pageviews. Origin metadata allows analytics tools to assign events to the page where they occurred.

Origin fields include:

• origin_pv_id — identifier of the pageview where the event originated
• origin_path — path of the origin pageview
• origin_page_seq — page sequence number within the visit
• client_ts_ms — client-side event timestamp, when available

These fields support behavioral reconstruction independently of hit arrival order.

3. Signal deduplication

Browser signals may occasionally be sent more than once due to retries, network issues, or repeated interactions.

Quantely Activity applies lightweight deduplication to reduce duplicate signals.

Events may be merged within a short time window while preserving diagnostic metadata. Pageviews are handled more conservatively. Duplicate pageviews may be suppressed when clearly redundant, but they are not merged because pageviews form the structural backbone of the activity stream.

4. Engagement signals

Instead of running continuous timers or larger client scripts, Quantely Activity records engagement as compact milestone signals.

Engagement pings are recorded as a single maximum engagement value per pageview.

Milestones follow the Fibonacci sequence: 2s / 3s / 5s / 8s / 13s / 21s / 34s / 55s / 89s.

This provides finer resolution for short visits and progressively coarser resolution for longer engagement, while keeping storage lightweight.

5. Traffic context

Quantely Activity records the context needed to interpret traffic more reliably.

UTM capture: – utm_source – utm_medium – utm_campaign – utm_term – utm_content

Click ID capture: Common identifiers such as gclid, fbclid, and others can be stored, including multiple identifiers in a compact field.

Channel derivation: Traffic can be classified at capture time based on referrer, UTMs, and click IDs.

Channels include: – email – paid – social – ai – search – referral – direct – internal

Channels can optionally be overridden by custom campaign rules using referrer host and UTM parameters.

6. WooCommerce purchase capture

Quantely Activity can capture WooCommerce purchases as lightweight conversion events.

A purchase event is recorded around checkout/order creation, helping ensure reliable capture across different WooCommerce flows and payment timings.

Captured fields include: – event_name: purchase – integration: woocommerce – order_id – purchase_origin

Product details and order totals are intentionally not stored. The purchase event acts as a minimal conversion marker for downstream analytics tools.

7. Bot detection and reclassification

Quantely Activity detects suspicious or automated traffic and records structured classifications at capture time.

Stored indicators include: – is_nonhuman – bot_label – bot_reason

Classification uses lightweight heuristics such as user-agent patterns, technical endpoint access, and burst patterns typical for scanners or link prefetchers.

Internal actor state helps track repeated behavior over time. This allows pattern-based reclassification. For example, probing or scanning behavior observed later can update earlier hits from the same actor.

Non-human traffic remains visible in Activity for diagnostics, but can be excluded from analytics processing.

8. Exclusions that do not destroy evidence

Most analytics tools silently drop excluded traffic. Quantely Activity does not.

Excluded hits remain visible in Activity but are clearly marked. This preserves diagnostic and forensic visibility while allowing analytics tools to filter the traffic when needed.

Supported exclusions include: – role-based exclusions – IP-based exclusions – path-based exclusions

Stored fields include: – is_excluded – exclude_reason

This helps ensure excluded traffic does not distort analytics while still allowing site owners to inspect what happened.

9. Short-term capture layer

Quantely Activity is designed as a short-term capture layer rather than a long-term analytics store.

Raw activity data is retained only for a limited period to keep the system lightweight and privacy-conscious.

All captured activity is stored in your own WordPress database.

10. Privacy

Quantely Activity is designed for reliable measurement while minimizing long-term storage and personal data exposure.

• No plain IP addresses stored
• Short configurable retention window
• Optional honoring of GPC / DNT signals
• No external tracking services
• Data remains on your own site

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.