modovisa

<p>A tiny settings page where you paste your <strong>Tracking token</strong> and enable tracking. The plugin then loads the lightweight Modovisa tracker on the <strong>front-end only</strong>.</p>
<ul>
<li>Loads once per page in <code><head></code> (optional <code>defer</code>).</li>
<li>Does <strong>not</strong> load in <code>wp-admin</code>.</li>
<li>Uses WordPress script APIs (<code>wp_register_script</code>/<code>wp_enqueue_script</code>) and standard attributes.</li>
<li>Plays nicely with common performance plugins (Autoptimize, WP Rocket).</li>
</ul>
<h3>How-to video</h3>
<p>Watch a short walkthrough of the setup:</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/olSW5JawjzE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>External services</h3>
<p>This plugin connects your WordPress site to the <strong>Modovisa Analytics</strong> service to track visitor journeys in real time on your WordPress site including page views and related events.</p>
<p><strong>Domains and what they do</strong><br />
– <code>https://cdn.modovisa.com/modovisa.min.js</code> — JavaScript file served from the Modovisa CDN. The plugin loads this script on the front-end when tracking is enabled.<br />
– <code>https://modovisa.com</code> (and subdomains) — Modovisa’s application/API endpoints that receive analytics events generated by the script.</p>
<p><strong>What data is sent and when</strong><br />
– On front-end page loads, the Modovisa script sends an event payload to Modovisa that typically includes:<br />
  – Page URL/path, referrer (if available), user agent, and basic device/viewport info.<br />
  – A Tracking identifier (<strong>your Tracking token</strong>) so data is associated with the correct Modovisa Tracking token.<br />
  – Pseudonymous visit/session identifiers (e.g., first-party cookies or similar storage) to recognize returning visits.<br />
– The plugin does <strong>not</strong> track or load the script in <code>wp-admin</code>. It does not send WordPress user emails, passwords, or other WP user PII.</p>
<p><strong>Consent and performance notes</strong><br />
– If you use a consent tool, configure it so the Modovisa script loads <strong>only after consent</strong>.<br />
– The script tag includes compatibility attributes for common performance plugins (e.g., <code>data-noptimize</code>, <code>data-nowprocket</code>, <code>data-cfasync</code>) to prevent aggregation or deferral from breaking analytics. These attributes do <strong>not</strong> transmit any data by themselves.</p>
<p><strong>Provider and policies</strong><br />
– Service: <strong>Modovisa Analytics</strong><br />
– Terms of Service: https://modovisa.com/legal/terms-and-conditions<br />
– Privacy Policy: https://modovisa.com/legal/privacy</p>
<h3>Privacy</h3>
<p>This plugin connects your site to <strong>Modovisa Analytics</strong> to measure visits and conversions. On front-end page loads, the Modovisa script (from <code>https://cdn.modovisa.com/modovisa.min.js</code>) sends event data to Modovisa for processing and reporting. The payload typically includes page URL, referrer (if available), user agent, and pseudonymous visit/session identifiers. The plugin does not send WordPress admin data or WP user PII.</p>
<p>Use of this plugin requires an active Modovisa account and Tracking token, which you enter on the plugin settings page. By enabling tracking, you consent to the transmission of analytics data to Modovisa as described in their policies:<br />
– Terms: https://modovisa.com/legal/terms-and-conditions<br />
– Privacy: https://modovisa.com/legal/privacy</p>


Modovisa Analytics

Injects the Modovisa real-time tracking script into your site’s .

erravi

<p>Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).</p>
<p>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.</p>
<p>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.</p>
<h3>Key features</h3>
<h4>Robust traffic monitoring</h4>
<p>Quantely Activity captures activity reliably under imperfect conditions.</p>
<ul>
<li>Server-side pageview capture (always-on baseline)</li>
<li>Optional browser signals (clicks, forms, engagement)</li>
<li>Server-side event capture from plugins, including WooCommerce</li>
<li>Server and browser alignment via <code>pv_id</code></li>
<li>Receive-order recording with preserved origin metadata</li>
<li>Lightweight deduplication of duplicate signals</li>
</ul>
<h4>Traffic context</h4>
<p>Each hit is enriched with context for interpretation and downstream use.</p>
<ul>
<li>UTM parameters (<code>utm_source</code>, <code>utm_medium</code>, etc.)</li>
<li>Click IDs (e.g. <code>gclid</code>, <code>fbclid</code>)</li>
<li>Channel classification (email, paid, social, ai, search, referral, direct, internal)</li>
<li>Visitor continuity via cookies and derived identifiers</li>
</ul>
<h4>Engagement signals</h4>
<p>Engagement is captured efficiently using milestone-based signals.</p>
<ul>
<li>One maximum engagement value per pageview</li>
<li>Fibonacci-based milestones (<code>2–89 seconds</code>)</li>
<li>No continuous timers or heavy scripts</li>
</ul>
<h4>Internal traffic filtering</h4>
<p>Internal or irrelevant traffic can be excluded without losing visibility.</p>
<ul>
<li>Role-based exclusions (e.g. admins)</li>
<li>IP-based exclusions</li>
<li>Path-based exclusions</li>
<li>Hits remain visible but are marked (<code>is_excluded</code>)</li>
</ul>
<h4>Bot filtering</h4>
<p>Automated traffic is detected and classified at capture time.</p>
<ul>
<li><code>is_nonhuman</code>, <code>bot_label</code>, <code>bot_reason</code></li>
<li>Detection based on patterns, endpoints, and behavior</li>
<li>Reclassification possible as patterns emerge</li>
</ul>
<h3>Privacy</h3>
<p>Designed to minimize data exposure and keep control local.</p>
<ul>
<li>No plain IP storage</li>
<li>Short retention window</li>
<li>GPC / DNT support</li>
<li>No external tracking services</li>
<li>Data stored fully on-site</li>
</ul>
<h3>Integrations</h3>
<p>Captured data is structured so other tools can use it.</p>
<ul>
<li>Activity data can feed downstream analytics tools</li>
<li>Events remain connected to their original page context</li>
<li>Compatible with analytics and processing workflows</li>
</ul>
<p>Quantely Activity exposes a small developer API for integrations and downstream processing.</p>
<ul>
<li><code>qmon_hit_before_insert</code> — Filter a normalized hit array before it is stored.</li>
<li><code>qmon_hit_recorded</code> — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.</li>
<li><code>qmon_event_normalize</code> — Filter a normalized event payload before it is finalized.</li>
<li><code>qmon_event_db_dedupe_window_sec</code> — Filter the database deduplication window for events.</li>
<li><code>qmon_bot_verdict</code> — Filter the bot-classification verdict before it is finalized.</li>
</ul>


Quantely Activity

See what is really happening on your WordPress website.

Modovisa Analytics vs Quantely Activity