Quantely Activity vs TeleLog

Lightweight, privacy-conscious pageview and event logging plugin that runs inside your own website. 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 All captured activity is stored in your own WordPress database. Quantely Activity does not send captured activity data to external services. IP addresses are never stored in plain form, 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 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.

This plugin is still under development and more hooks will be added soon, but for now, the full list of its hooks are: Post publish Post update New comment Login fail New plugin activation New plugin deactivation Theme switch New user registation New WooCommerce order Set up Create a new Telegram bot. (Learn more) Go to TeleLog admin page from your wordpress dashboard. Copy your bot token from botfather and paste it in the “API Key” field. If you want TeleLog to send the logs to your personal account, you can use your userid and put it in the “Chat ID” field (Find your userid), the other option is to create a channel and make your bot an admin with “Post Messages” access and enter the channel username as “Chat ID”, with an atsign(@) before it, e.g: @username. For every event that TeleLog sends it also reports the: User who did the change The object on which the change happenned. TeleLog in your language! We need help translating TeleLog, feel free to contribute to our GitHub Repository. TeleLog currently supports: English Persian Install TeleLog from within WordPress Visit ‘Plugins > Add New’ Search for ‘TeleLog’ Install and activate the TeleLog plugin Install TeleLog manually Upload the telelog directory to the /wp-content/plugins/ directory Activate the TeleLog plugin from the ‘Plugins’ menu in WordPress