Quantely Activity vs Web Plura Diagnostics – Site Health,

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.

Web Plura Diagnostics helps WordPress site owners, agencies, and support teams find problems that quietly hurt leads, sales, trust, and maintenance time. It runs inside wp-admin and turns local site signals into clear, prioritized action items. Use it when you need to answer practical questions before an update, launch, client handoff, or support call: Are forms, password resets, store emails, and lead notifications likely to work? Is the site showing health, hosting, cache, cron, or PHP warning signs? Which plugin, theme, or update risks should be checked before making changes? What should a business owner, developer, host, or support team fix first? What can be exported or shared without sending diagnostics to an external service? For every finding, the plugin focuses on: What is wrong Why it matters What business impact it may cause Who should fix it What to fix first No external account, no tracking, and no frontend scripts are required for the core diagnostics workflow. No external service requirement: core diagnostics, dashboard rendering, exports, and scheduled scans run locally in WordPress. No tracking: diagnostics scans do not send telemetry or site diagnostics to Web Plura by default. Free local checks remain available without an external account. Customer Problems It Helps Solve Missed leads from broken contact forms, weak email setup, or untested notification paths. Risky updates when a site has stale plugins, inactive code, commerce dependencies, or no clear pre-update checklist. Slow or unstable sites caused by cache gaps, low memory, cron pressure, upload limits, or hosting constraints. Confusing support handoffs where clients, developers, and hosts need the same problem summary. Reactive maintenance where issues are discovered only after checkout, login, email, or lead capture fails. Key Checks Fix First dashboard with score, priority groups, recommended actions, and recent-change history. Site Health-style checks for WordPress, database version, PHP limits, timezone, URL alignment, cache signals, and key file permissions. Email readiness checks for local mail transport, SPF, DKIM, DMARC, domain alignment, manual admin-triggered test email results, and optional bounded metadata-only test history. Diagnostics scans do not send email automatically. Lead Capture Health checks for form plugins, contact pages, SMTP readiness, privacy-page status, and form-plugin updates. Pre-update Safety checks for inactive plugins, theme update backlog, commerce plugins, builders, and cache plugins. Hosting Advisor checks for memory, cache, cron pressure, upload limits, execution limits, and host-support guidance. Cron & Background Jobs checks for WP-Cron configuration, overdue events, orphaned callbacks, repeated hooks, Action Scheduler presence, and WooCommerce queue backlog signals. Front-end Response checks for home URL HTTPS, response code, redirect signal, cache-control, compression header, and REST API response. Support-safe diagnostics snapshot with redacted environment, module scores, and top findings for support handoffs. Client-ready diagnostics with problem, impact, owner, urgency, next action, JSON/CSV exports, WP-CLI commands, and multisite network visibility. Good Fit For Site owners who want a clear first-pass health, email, performance, and update-readiness review. Agencies preparing client reports, maintenance checks, launch reviews, or pre-update safety notes. Support teams collecting safe local diagnostics before deeper troubleshooting. WordPress admins who want prioritized actions without telemetry or a required external account. Product page: https://wplura.com/products/web-plura-diagnostics Terms: https://wplura.com/terms Privacy: https://wplura.com/privacy External Services Web Plura Diagnostics is local-first. Diagnostics scans, dashboard rendering, exports, and scheduled scans run inside WordPress by default. The plugin links to Web Plura product, terms, and privacy pages for support and product information: Product page: https://wplura.com/products/web-plura-diagnostics Terms: https://wplura.com/terms Privacy: https://wplura.com/privacy The public WordPress.org package uses WordPress.org update checks. Direct/private Web Plura builds may request a signed Web Plura release manifest from https://api.wplura.com/v1/plugin/updates/web-plura-diagnostics/manifest and send only the plugin slug, current version, and release channel. Data, retention, and uninstall behavior: Diagnostics results, history snapshots, explain-mode preference, scheduled-scan settings, export metadata, and manual test-email metadata are stored locally in WordPress options/transients. Retention settings allow site admins to control how long local diagnostic history and email-test metadata are kept. Uninstall cleanup removes plugin-owned options, transients, scheduled scan hooks, and local diagnostic metadata.