modovisa

A tiny settings page where you paste your Tracking token and enable tracking. The plugin then loads the lightweight Modovisa tracker on the front-end only.
<ul>
<li>Loads once per page in <code><head></code> (optional <code>defer</code>).</li>
<li>Does not 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>
Watch a short walkthrough of the setup:
<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>
<h3>External services</h3>
This plugin connects your WordPress site to the Modovisa Analytics service to track visitor journeys in real time on your WordPress site including page views and related events.
Domains and what they do 
– <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. 
– <code>https://modovisa.com</code> (and subdomains) — Modovisa’s application/API endpoints that receive analytics events generated by the script.
What data is sent and when 
– On front-end page loads, the Modovisa script sends an event payload to Modovisa that typically includes: 
 – Page URL/path, referrer (if available), user agent, and basic device/viewport info. 
 – A Tracking identifier (your Tracking token) so data is associated with the correct Modovisa Tracking token. 
 – Pseudonymous visit/session identifiers (e.g., first-party cookies or similar storage) to recognize returning visits. 
– The plugin does not track or load the script in <code>wp-admin</code>. It does not send WordPress user emails, passwords, or other WP user PII.
Consent and performance notes 
– If you use a consent tool, configure it so the Modovisa script loads only after consent. 
– 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 not transmit any data by themselves.
Provider and policies 
– Service: Modovisa Analytics 
– Terms of Service: https://modovisa.com/legal/terms-and-conditions 
– Privacy Policy: https://modovisa.com/legal/privacy
<h3>Privacy</h3>
This plugin connects your site to Modovisa Analytics 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.
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: 
– Terms: https://modovisa.com/legal/terms-and-conditions 
– Privacy: https://modovisa.com/legal/privacy

Modovisa Analytics

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

Octanist

Octanist is a conversion tracking platform that bridges online marketing with offline sales. This plugin is the official connector for WordPress.
<h3>How it works</h3>
The plugin acts as a first-party proxy for the Octanist pixel:
<ul>
<li>Pixel proxy. The tracking script is served from your own WordPress site (<code>/wp-json/oct/p</code>) and transparently fetched from Octanist in the background. No third-party domain, no DNS setup, no ad-blocker signal to match on.</li>
<li>Event proxy. Events from the pixel POST to <code>/wp-json/oct/e</code>; the plugin forwards them to Octanist server-side, carrying along the real visitor IP, country, and user-agent.</li>
<li>Server-side form capture. Form submissions from Gravity Forms, Contact Form 7, WPForms, Ninja Forms, Elementor Pro, Fluent Forms, Formidable Forms, Forminator, SureForms, and Divi Contact Form are captured server-side via action hooks, more reliable than client-side interception, and works with AJAX submissions.</li>
</ul>
<h3>Setup</h3>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to Settings → Octanist.</li>
<li>Paste your measurement ID.</li>
<li>Done.</li>
</ol>
That’s it. No field mapping. No DNS configuration. Listener mode and consent mode are optional toggles.
<h3>Data privacy</h3>
<ul>
<li>Octanist account required. You need an active account at octanist.com.</li>
<li>You are the data controller. Consent capture and privacy-policy disclosure are your responsibility. A consent management platform (CMP) is recommended.</li>
</ul>

First-party proxy for the Octanist pixel. Serves the tracking script from your own domain and captures form submissions server-side.

Modovisa Analytics vs Octanist