Quantely Activity vs Scoby Analytics

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.

Scoby Analytics is a privacy-focused analytics plugin for WordPress. It is designed to provide website operators with actionable usage statistics without using cookies, device fingerprinting, or cross-site identifiers. The WordPress integration is a lightweight, client-side integration that prioritizes visitor privacy. Scoby’s goal is to enable analytics in a way that can typically be operated under legitimate interest (Art. 6(1)(f) GDPR) and without consent banners, provided it is used as intended and configured appropriately. Scoby does not provide legal advice; always assess your specific setup with your DPO/legal counsel. We’re happy to answer their questions at [email protected] Privacy approach (GDPR / ePrivacy) Scoby is designed around the following principles: No cookies / no storage on the user device (relevant for ePrivacy / TDDDG) No device fingerprinting No user profiles or cross-site tracking Anonymization before transmission and aggregated storage (no individual-level analytics) This means Scoby is not trying to “optimize consent rates”. Instead, it aims to reduce or avoid regulated processing operations in the first place by keeping analytics non-identifying and aggregate. What Scoby measures Scoby provides aggregated statistics such as: Page views and visits Entry/exit pages and content performance Engagement metrics (e.g., time-spent distributions/percentiles) Conversion events (depending on your setup) Referrers and traffic sources (without persistent identifiers) What Scoby does not do No cookies No device fingerprinting No cross-site tracking No user/device profiles Reporting & exports WordPress dashboard reporting Export to .xlsx Integrations with BI tools (e.g., Looker Studio, PowerBI, Tableau) Third Party Services Scoby Analytics uses Scoby-operated servers for analytics processing. Service Used Service: Scoby Analytics Servers Purpose: Capture, process, and store website usage statistics in an anonymized and aggregated form to provide analytics reporting. Data Handling and Privacy – Anonymization prior to transmission: Page views and associated metrics are anonymized before being transmitted to Scoby Analytics servers. – Aggregation: Stored data is aggregated and not intended to relate to identifiable individuals. – No personal identifiers: Scoby is designed to avoid collecting or storing identifiers such as cookies, fingerprinting signals, or IP addresses. Transparency and further information – Service information: https://www.scoby.io/ – Terms of Use: https://www.scoby.io/terms – Privacy Policy: https://www.scoby.io/privacy