外掛標籤
開發者團隊
原文外掛簡介
Quantely Activity is a lightweight, privacy-conscious plugin that captures visitor activity as it happens. It records pageviews and events reliably, even under imperfect conditions.
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
Optional 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.
