[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4gBf3-aa-xFukPISWswAQABKv4vouw_ZwXesgkFiB9g":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"erravi","https:\u002F\u002Fprofiles.wordpress.org\u002Ferravi\u002F",1,0,100,30,94,"2026-05-20T09:40:06.041Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":8,"num_ratings":6,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"quantely-activity","Quantely Activity","1.1.4","\u003Cp>Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).\u003C\u002Fp>\n\u003Cp>It helps site owners understand what is happening on their website for monitoring, diagnostics, performance checks, and analytics validation. It also makes this data available to downstream analytics tools.\u003C\u002Fp>\n\u003Cp>Quantely Activity runs fully on-site, uses no external services, stores data only briefly, supports cookie-free operation, does not depend on JavaScript, and does not store plain IP addresses.\u003C\u002Fp>\n\u003Ch3>Key features\u003C\u002Fh3>\n\u003Ch4>Robust traffic monitoring\u003C\u002Fh4>\n\u003Cp>Quantely Activity captures activity reliably under imperfect conditions.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Server-side pageview capture (always-on baseline)\u003C\u002Fli>\n\u003Cli>Optional browser signals (clicks, forms, engagement)\u003C\u002Fli>\n\u003Cli>Server-side event capture from plugins, including WooCommerce\u003C\u002Fli>\n\u003Cli>Server and browser alignment via \u003Ccode>pv_id\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Receive-order recording with preserved origin metadata\u003C\u002Fli>\n\u003Cli>Lightweight deduplication of duplicate signals\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Traffic context\u003C\u002Fh4>\n\u003Cp>Each hit is enriched with context for interpretation and downstream use.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>UTM parameters (\u003Ccode>utm_source\u003C\u002Fcode>, \u003Ccode>utm_medium\u003C\u002Fcode>, etc.)\u003C\u002Fli>\n\u003Cli>Click IDs (e.g. \u003Ccode>gclid\u003C\u002Fcode>, \u003Ccode>fbclid\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Channel classification (email, paid, social, ai, search, referral, direct, internal)\u003C\u002Fli>\n\u003Cli>Visitor continuity via cookies and derived identifiers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Engagement signals\u003C\u002Fh4>\n\u003Cp>Engagement is captured efficiently using milestone-based signals.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>One maximum engagement value per pageview\u003C\u002Fli>\n\u003Cli>Fibonacci-based milestones (\u003Ccode>2–89 seconds\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>No continuous timers or heavy scripts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Internal traffic filtering\u003C\u002Fh4>\n\u003Cp>Internal or irrelevant traffic can be excluded without losing visibility.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Role-based exclusions (e.g. admins)\u003C\u002Fli>\n\u003Cli>IP-based exclusions\u003C\u002Fli>\n\u003Cli>Path-based exclusions\u003C\u002Fli>\n\u003Cli>Hits remain visible but are marked (\u003Ccode>is_excluded\u003C\u002Fcode>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Bot filtering\u003C\u002Fh4>\n\u003Cp>Automated traffic is detected and classified at capture time.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>is_nonhuman\u003C\u002Fcode>, \u003Ccode>bot_label\u003C\u002Fcode>, \u003Ccode>bot_reason\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Detection based on patterns, endpoints, and behavior\u003C\u002Fli>\n\u003Cli>Reclassification possible as patterns emerge\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>Designed to minimize data exposure and keep control local.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>No plain IP storage\u003C\u002Fli>\n\u003Cli>Short retention window\u003C\u002Fli>\n\u003Cli>GPC \u002F DNT support\u003C\u002Fli>\n\u003Cli>No external tracking services\u003C\u002Fli>\n\u003Cli>Data stored fully on-site\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Integrations\u003C\u002Fh3>\n\u003Cp>Captured data is structured so other tools can use it.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Activity data can feed downstream analytics tools\u003C\u002Fli>\n\u003Cli>Events remain connected to their original page context\u003C\u002Fli>\n\u003Cli>Compatible with analytics and processing workflows\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Quantely Activity exposes a small developer API for integrations and downstream processing.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>qmon_hit_before_insert\u003C\u002Fcode> — Filter a normalized hit array before it is stored.\u003C\u002Fli>\n\u003Cli>\u003Ccode>qmon_hit_recorded\u003C\u002Fcode> — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.\u003C\u002Fli>\n\u003Cli>\u003Ccode>qmon_event_normalize\u003C\u002Fcode> — Filter a normalized event payload before it is finalized.\u003C\u002Fli>\n\u003Cli>\u003Ccode>qmon_event_db_dedupe_window_sec\u003C\u002Fcode> — Filter the database deduplication window for events.\u003C\u002Fli>\n\u003Cli>\u003Ccode>qmon_bot_verdict\u003C\u002Fcode> — Filter the bot-classification verdict before it is finalized.\u003C\u002Fli>\n\u003C\u002Ful>\n","See what is really happening on your WordPress website.",230,"2026-04-12T14:23:00.000Z","6.9.4","6.2","7.4",[25,26,27,28,29],"event-tracking","pageviews","user-activity","visitor-tracking","website-traffic","https:\u002F\u002Fwww.erravi.com\u002Fplugins\u002Fquantely-activity\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquantely-activity.1.1.4.zip",null,"2026-04-16T10:56:18.058Z"]