Title: Harvv Analytics
Author: Harvv
Published: <strong>Èbìbí  7, 2026</strong>
Last modified: Èbìbí  13, 2026

---

Ṣàwárí àwọn plugin

![](https://ps.w.org/harvv-analytics/assets/icon-256x256.png?rev=3525855)

# Harvv Analytics

 Láti ọwọ́ [Harvv](https://profiles.wordpress.org/ecommercepros505/)

[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/harvv-analytics.1.0.8.zip)

 * [Àwọn àlàyé](https://yor.wordpress.org/plugins/harvv-analytics/#description)
 * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/harvv-analytics/#reviews)
 *  [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/harvv-analytics/#installation)
 * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/harvv-analytics/#developers)

 [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/harvv-analytics/)

## Àpèjúwe

**Zero PII. No cookies. No consent banner required.**

Harvv Analytics ships a lightweight (under 10 KB gzipped) behavioral tracker that
captures how visitors interact with your pages — dead clicks, rage clicks, scroll
depth, hover intent, JavaScript errors, engagement time — and syncs WooCommerce 
orders to your Harvv dashboard. It never reads cookies, never transmits names, emails,
phone numbers, or addresses, and never stores personal data in your WordPress database.

Because the plugin transmits no personal data, it does not require a cookie-consent
banner under GDPR, CCPA, or PECR. Your visitors see no pop-ups; your checkout flows
are not slowed; your compliance posture is simpler.

**What this plugin does**

 * Enqueues a vanilla-JS tracker (no jQuery, no external scripts) on your frontend.
 * Captures behavioral signals: scroll depth, click targets, dead/rage clicks, hover
   intent, page errors, engagement time.
 * Syncs WooCommerce orders on `woocommerce_payment_complete` (never blocks checkout).
 * Passes customer identity as a non-reversible hash derived from the siteÌtumọ̀
   Yorùbá: ’s own salts — the raw email never leaves WordPress.
 * Works with WooCommerce HPOS (Custom Order Tables) out of the box.
 * Multisite-aware: one network API key, per-subsite Site IDs, per-subsite admin
   overrides.

**What this plugin does NOT do**

 * Does not set or read cookies.
 * Does not transmit email addresses, names, phone numbers, postal addresses, or
   IP addresses.
 * Does not load any JavaScript from external URLs — the tracker ships bundled with
   the plugin.
 * Does not create custom database tables on your WordPress site.
 * Does not record session replays or keystrokes.

**Why you might want this**

If you run a WooCommerce store and want to see the dead clicks, rage clicks, and
broken checkout paths your visitors hit — without making them click through a GDPR
banner — Harvv is designed for you. The behavioral signals are sent to your Harvv
dashboard where they become a prioritized list of UX fixes with plain-English explanations.

### External Services

This plugin relies on the Harvv analytics service (operated by Olivas Venture Capital
LLC d/b/a Harvv) to store and analyze behavioral events. Data is transmitted to 
the following endpoint:

 * **Endpoint:** `https://harvv.com/v1/track` (overridable via the `HARVV_API_BASE`
   constant in `wp-config.php` for staging or self-hosted receivers)
 * **When:** Events are sent continuously while a visitor is on your site (batched
   every 5 seconds or on tab close, via `navigator.sendBeacon` when available). 
   WooCommerce order events are sent once, on `woocommerce_payment_complete`.
 * **What is sent (behavioral events):** Session ID (random, in-memory, regenerated
   per browser tab — never a stable cookie), visitor ID (sessionStorage-scoped, 
   cleared when the tab closes), event type, page path (no query string with sensitive
   params), referrer, viewport dimensions, CSS selectors of clicked/hovered elements(
   tag + id + first class name only, no text content), JavaScript error messages,
   engagement timestamps.
 * **What is sent (WooCommerce events):** Order ID, order status, order total, line-
   item product IDs and quantities, coupon codes, payment method name, shipping 
   method name, non-reversible customer hash (derived via `wp_hash()` using your
   WordPress salts).
 * **What is NOT sent:** Names, email addresses, phone numbers, postal addresses,
   IP addresses, raw user IDs, cookies, session replays, keystroke data, form values.
 * **Registration endpoint:** `https://harvv.com/v1/sites/register` — called once
   per site (or subsite on Multisite) to obtain a Site ID. Transmits only the site
   URL, site name, WordPress version, PHP version, and plugin version.
 * **Pixel script (canonical, 1.0.3+):** `https://harvv.com/px/<your_site_key>/pixel.
   js` — enqueued on the frontend via `wp_enqueue_script`. This is the same canonical
   pixel served to every Harvv-installed site regardless of install channel (WP 
   plugin, Laravel package, direct script-tag, Shopify integration). Loaded once
   per page, ~15.6 KB gzipped. The pixel itself transmits only the behavioral signals
   described above. Sites that need an offline-capable / self-hosted pixel can override
   the URL via `define( 'HARVV_PIXEL_URL', '...' );` in `wp-config.php`, or via 
   the `harvv_pixel_url` filter.
 * **Connect flow:** `https://harvv.com/connect/wordpress` — opened in a new browser
   tab when an admin clicks “Connect to Harvv” in the plugin settings. HarvvÌtumọ̀
   Yorùbá: ’s hosted signup page handles authentication; it then POSTs the API key
   back to your siteÌtumọ̀ Yorùbá: ’s own REST endpoint (`/wp-json/harvv/v1/connect`)
   with a nonce you generated locally.
 * **Stack-inventory endpoint:** `https://harvv.com/v1/inventory` — called once 
   at site registration and refreshed weekly by WP-Cron. Sends a **site-context 
   snapshot**: installed plugin slugs + versions, the active theme slug + version,
   WordPress version, PHP version, MySQL/MariaDB version, server software string(
   e.g. “nginx/1.24.0”), site language code, timezone, permalink-structure boolean,
   WP_DEBUG boolean, memory limit, max execution time, object cache backend, WP-
   Cron disabled boolean, multisite blog count, total user count (number only — 
   no usernames, no emails, no per-role breakdown), aggregate post and page counts,
   custom post type slugs + publish counts, and (when WooCommerce is active) WooCommerce
   version, store currency, base country, and product count. **No visitor data, 
   no usernames, no email addresses, no post content, no comments, no IP addresses,
   no PII of any kind.** Powers plugin-attribution and platform-specific UX diagnosis
   on the Harvv dashboard. Admins can preview the exact payload at **Settings  Harvv
   Analytics  Preview the exact diagnostic snapshot we would send**. Disabled by
   clearing the **Settings  Harvv Analytics  Preferences  Share stack info** checkbox,
   by adding `define( 'HARVV_SHARE_INVENTORY', false );` to `wp-config.php`, or 
   by returning `false` from the `harvv_share_inventory` filter.
 * **Harvv terms of service:** [https://harvv.com/terms](https://harvv.com/terms)
 * **Harvv privacy policy:** [https://harvv.com/privacy](https://harvv.com/privacy)

By activating this plugin and supplying an API key, you consent to the transmission
of the data described above to Harvv. You can disconnect at any time from the pluginÌtumọ̀
Yorùbá: ’s settings page; uninstalling removes all plugin options from your database.

## Ìgbéwọlẹ̀

 1. Install and activate the plugin through the WordPress Plugins screen, or upload
    the plugin folder to `/wp-content/plugins/harvv-analytics/`.
 2. Navigate to **Settings  Harvv Analytics**.
 3. Click **Connect to Harvv** — this opens harvv.com in a new tab for signup. Once
    you complete signup, the tab will notify this plugin and your API key will be saved
    automatically.
 4. Alternatively, expand **I already have an API key** and paste your key manually.
 5. On WooCommerce sites, no further action is needed — order events start flowing 
    on the next completed payment.

For multisite networks: go to **Network Admin  Settings  Harvv Analytics** and set
one network-wide API key. Each subsite will auto-register with Harvv on its next
pageload and receive its own Site ID.

## FAQ

### Does this require a cookie consent banner?

No. The plugin sets no cookies and transmits no personal data. Under GDPR, CCPA,
and PECR, cookie-consent banners are required only when a site sets non-essential
cookies or transmits personal data to third parties. Harvv transmits only behavioral
signals (dead clicks, scroll depth, etc.) and a non-reversible customer hash — these
are not personal data under any major privacy regime.

If your legal counsel interprets the regulations more conservatively than we do,
you can still add Harvv to your privacy policyÌtumọ̀ Yorùbá: ’s third-party services
section. The plugin provides suggested language at **Settings  Privacy  Policy Guide**.

### Does this plugin work without WooCommerce?

Yes. The WooCommerce integration loads conditionally — on a non-Woo WordPress site,
the plugin runs as a pure behavioral pixel.

### Does this plugin slow down my checkout?

No. All outbound HTTP calls use `wp_remote_post()` with `'blocking' => false`, and
the browser tracker uses `navigator.sendBeacon()` or `fetch` with `keepalive: true`.
Nothing in the plugin waits on a response from Harvv.

### Is this plugin HPOS (Custom Order Tables) compatible?

Yes. The plugin declares compatibility with `custom_order_tables` and uses only 
the WC_Order CRUD API — never direct `$wpdb` access against order tables.

### What happens if my site loses internet connectivity?

The browser tracker queues events locally and attempts to flush on each interval;
unsent events are discarded silently when the browser tab closes. WooCommerce order
events are fire-and-forget — if your site cannot reach `harvv.com` at the moment
of `payment_complete`, the event is lost. We do not queue order events for retry
on-site because doing so would require creating a custom database table, which this
plugin intentionally does not do.

As of 1.0.1 the plugin records the timestamp of the most recent successful Woo sync
and surfaces it on the settings page so an admin can spot a silently broken integration
before reconciling Stripe and Woo manually.

### How do I uninstall?

Delete the plugin from the Plugins screen. All plugin options (`harvv_api_key`, `
harvv_site_id`, and related) are removed via `uninstall.php`. The plugin never creates
custom database tables on your site, so nothing is left behind.

### I use caching plugins — does this conflict?

No. The tracker is enqueued in the footer and is cache-friendly (same output for
every visitor). The Connect-flow REST endpoint is under `/wp-json/harvv/v1/*` and
is gated by a one-shot nonce, so caching that endpoint is harmless.

### Is the Site key in my page source a secret?

No — the Site key is a public, per-site identifier. Think of it like a Stripe **
publishable** key: it ships embedded in your page source so the browser tracker 
can authenticate its POSTs to Harvv. It can be used only to send events for the 
site it was issued for; it cannot be used to read your account data or events from
any other site. If you ever need to rotate it, do so from the Harvv dashboard.

### How do I keep Harvv exempt from my optimization plugin?

As of 1.0.4 the plugin auto-injects the exclusion attribute for every major optimization
tool, so most setups are immune out of the box. The exceptions are three tools that
match by URL pattern rather than HTML attribute:

 * **Perfmatters** — Settings  Perfmatters  Assets  Script Manager  “Delay JavaScript”
   Exclusions: add `harvv.com/px/`.
 * **W3 Total Cache** — Performance  Minify  JS  Never minify the following JS files:
   add `https://harvv.com/px/*`.
 * **Hummingbird** — Hummingbird  Asset Optimization  Files to exclude: add `harvv.
   com/px/`.

If youÌtumọ̀ Yorùbá: ’re not running any of those three, you do not need to do anything—
the pluginÌtumọ̀ Yorùbá: ’s auto-injected attributes handle WP Rocket, LiteSpeed
Cache, Autoptimize, WP Fastest Cache, NitroPack, and Cloudflare Rocket Loader automatically.

### How can I prevent the tracker from loading on specific pages?

Add a filter on `harvv_should_load_tracker` in your themeÌtumọ̀ Yorùbá: ’s `functions.
php` or a small site-specific plugin:

    ```
    add_filter( 'harvv_should_load_tracker', function( $load ) {
        if ( is_admin() || is_cart() || is_checkout() ) {
            return false;
        }
        return $load;
    } );
    ```

The filter fires before `wp_enqueue_script` runs, so a `false` return prevents the
script tag from ever appearing in HTML.

### How do I point the plugin at a staging or self-hosted receiver?

Define `HARVV_API_BASE` in `wp-config.php` before WordPress loads plugins:

    ```
    define( 'HARVV_API_BASE', 'https://staging.example.com' );
    ```

The plugin sends every outbound API call (registration, Woo order sync) to that 
base URL. The Connect flow always uses `https://harvv.com` because HarvvÌtumọ̀ Yorùbá:’
s hosted signup page is the only place that can mint a fresh API key.

### How do I tell if WooCommerce order sync is working?

Settings  Harvv Analytics shows the time since the most recent successful sync underneath
the “Connected ✓” badge on WooCommerce sites. If a sync fails (DNS error, sslverify
mismatch, etc.) the error message is shown in red and the timestamp is preserved
from the last successful send. The plugin never blocks checkout — these signals 
are surfaced asynchronously so you can spot a failing integration before it becomes
a reconciliation problem.

### Does the plugin send a list of my other plugins? Why?

Yes — by default, the plugin sends Harvv a snapshot of which other plugins, theme,
WordPress version, and PHP version are installed on the site. **This is site metadata,
not visitor data.** No personal information, no user content, no option values.

**Why we do this:** HarvvÌtumọ̀ Yorùbá: ’s value comes from telling you _exactly_
whatÌtumọ̀ Yorùbá: ’s wrong with your siteÌtumọ̀ Yorùbá: ’s UX. The browser tracker
can see “users are bouncing on /pricing because of a 600ms layout shift” — but without
knowing which plugins are running, the diagnosis stops at “something is shifting
layout.” With the stack snapshot, we can attribute the shift to the specific plugin
causing it (e.g. “Yoast 22.8 injects a meta tag late”) and tell you exactly what
to fix. Faster diagnosis = faster fix = better speed and UX for your visitors. ThatÌtumọ̀
Yorùbá: ’s what this plugin is for.

**WhatÌtumọ̀ Yorùbá: ’s sent (1.0.2 — site context):**

 * Installed plugins: slug only (e.g. `yoast-seo`, not the human display name), 
   version, active boolean.
 * Active theme: slug, display name, version, parent theme slug.
 * Environment: WordPress version, PHP version, MySQL/MariaDB version, server software
   string, site language code (`en_US`, `fr_FR`, …), timezone (`America/Chicago`),
   permalink-structure boolean (“pretty” vs “plain”), WP_DEBUG boolean, memory limit,
   max execution time, object cache backend (external / none), WP-Cron disabled 
   boolean, multisite boolean + blog count.
 * Aggregate counts (no individual content): total registered users (number only),
   published + draft post and page counts, every custom post typeÌtumọ̀ Yorùbá: ’
   s slug + publish count.
 * WooCommerce (only when active): version, store currency code, store base country,
   total published product count.

**What is NOT sent** (and we want to be explicit): no usernames, no email addresses,
no IP addresses, no visitor data, no post titles or content, no comment data, no
plugin option values, no user passwords, no per-user breakdowns (we only send the
total count), no “last login” timestamps. Click **Settings  Harvv Analytics  Preview
the exact diagnostic snapshot we would send** to see the literal JSON payload before
your next sync fires.

**Three independent opt-outs**, any of which disables the feature fully — no opt-
out beacon is sent, the feature simply does nothing:

 1. **UI toggle (recommended for most admins):** uncheck **Settings  Harvv Analytics
    Preferences  Share stack info**.
 2. **Site-config constant (recommended for staging-first / WP-CLI workflows):** add`
    define( 'HARVV_SHARE_INVENTORY', false );` to `wp-config.php`. This wins over the
    UI toggle.
 3. **Programmatic filter (for advanced cases):** `add_filter( 'harvv_share_inventory','
    __return_false' );` in a small mu-plugin.

The plugin will continue to work normally with the feature disabled; you just give
up the plugin-attribution column in the Harvv dashboard.

### Does this plugin auto-update?

Yes — Harvv Analytics defaults to auto-update from WordPress 5.5+ so new behavioral
signals and bug fixes reach your site without you having to remember to click Update.
Behavioral pixels are most valuable when theyÌtumọ̀ Yorùbá: ’re current; an out-
of-date pixel silently misses entire classes of issues, so the default leans toward“
stay current.”

If youÌtumọ̀ Yorùbá: ’d prefer to manage updates manually (e.g. on a staging-first
workflow), add this line to your `wp-config.php`:

    ```
    define( 'HARVV_AUTO_UPDATE', false );
    ```

The plugin will then defer to WordPressÌtumọ̀ Yorùbá: ’s normal per-plugin auto-
update toggle (which defaults to OFF until you click “Enable auto-updates” on the
Plugins screen).

## Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

## Àwọn Olùkópa & Olùgbéejáde

“Harvv Analytics” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa
sí plugin yìí.

Àwọn Olùkópa

 *   [ Harvv ](https://profiles.wordpress.org/ecommercepros505/)

[Túmọ̀ “Harvv Analytics” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/harvv-analytics)

### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/harvv-analytics/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/harvv-analytics/), tàbí ṣe àgbékalẹ̀
sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/harvv-analytics/)
nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/harvv-analytics/?limit=100&mode=stop_on_copy&format=rss).

## Àkọsílẹ̀ àwọn àyípadà

#### 1.0.8

 * **New:** dataLayer source. The pixel now subscribes to `window.dataLayer` and
   ingests GA4 recommended events (`add_to_cart`, `begin_checkout`, `view_cart`,`
   purchase`, `view_item`, `generate_lead`, `sign_up`, `search`) as Harvv `cm` events
   with `src:'dl'`. When a customerÌtumọ̀ Yorùbá: ’s GTM container fires a GA4 conversion
   event, Harvv captures the same logical event via the dataLayer instead of re-
   detecting from the DOM. More precise, less noise.
 * **New:** dataLayer sink. HarvvÌtumọ̀ Yorùbá: ’s detected commerce signals are
   also pushed to `window.dataLayer` under `event: 'harvv_signal'` (namespaced —
   never reuses GA4 event names, so no double-counting in customerÌtumọ̀ Yorùbá:’
   s GA4 reports). Customers can set up GTM triggers on `harvv_signal` to route 
   Harvv signals to Meta Pixel, Klaviyo, or any other tool managed through GTM.
 * **New:** in-pixel dedupe. DOM-detected events are held for 100ms; if a matching
   dataLayer event arrives in that window (GTM fired on the same click), the DOM
   emission is suppressed and the dataLayer version wins. Result: one event per 
   real conversion, regardless of how many signal paths the customerÌtumọ̀ Yorùbá:’
   s site has.
 * **New:** broader optimization-tool attribution. The `pf.deferred` eventÌtumọ̀
   Yorùbá: ’s `via` field now also detects LiteSpeed Cache and Cloudflare Rocket
   Loader in addition to WP Rocket, Perfmatters, and NitroPack. Dashboard banner
   and email alert can name the specific tool deferring the pixel.
 * **Internal:** GA4 event-name mapping centralized in `GA4_NAMES` (HarvvGA4) and`
   GA4_TO_KIND` (GA4Harvv). Adding a new mapping is a one-line change in either 
   object.

#### 1.0.7

 * **New:** GA4 coexistence layer. The canonical pixel now detects whether Google
   Analytics 4 is installed on the page (via `gtag`, `google_tag_manager`, or `dataLayer`)
   and stamps every session with a `ga4` flag. Commerce events (`cm/ca`, `cm/co`)
   carry a `ga4` alias mapping to the GA4 recommended event names (`add_to_cart`,`
   begin_checkout`) so the Harvv dashboard can label both. Harvv and GA4 stay separate-
   namespaced — no dataLayer writes by default — which means **zero double-counting**
   in the customerÌtumọ̀ Yorùbá: ’s GA4 reports.
 * **New:** GA4 Consent Mode v2 awareness. When `analytics_storage` is denied in
   the siteÌtumọ̀ Yorùbá: ’s consent config, the pixel downgrades to anonymous mode
   automatically (in-memory visitor ID, no cookie or localStorage writes) — mirroring
   GA4Ìtumọ̀ Yorùbá: ’s own “cookieless ping” behavior so the privacy posture stays
   consistent across both tools.
 * **Docs:** new runbook at `docs/runbooks/ga4-coexistence.md` documents the cross-
   system contract, expected number-deltas vs GA4, and the canonical answer for “
   why donÌtumọ̀ Yorùbá: ’t my Harvv numbers match GA4?” support questions.

#### 1.0.6

 * **New conversion signals (canonical pixel):** the pixel now fires on three high-
   value commerce moments, automatically detected from any page (no configuration
   needed):
    - **Cart-add clicks** (`cm`, kind `ca`) — every time a visitor clicks an “Add
      to cart” / `add_to_cart_button` / `single_add_to_cart_button` / `[data-add-
      to-cart]` element. Element id + scroll depth at click attached.
    - **Coupon attempts** (`cm`, kind `co`) — when a visitor focuses any input named
      coupon / discount / promo. Strong leading indicator for conversion intent.
    - **Exit intent on commerce URLs** (`cm`, kind `ei`) — mouse leaves the viewport
      from the top edge on `/cart`, `/checkout`, `/basket`, or `/payment`. One emit
      per pageload. Predicts cart abandonment.
 * **Scroll-depth at click** — every interaction (`ix`) event now carries `sp` =
   scroll % of the page when the click happened. Lets the dashboard answer “are 
   customers clicking my CTA from above the fold or after scrolling past it?”.
 * **Lazy-load attribution (Layer 5):** when the pixel detects it was deferred, 
   the `pf.deferred` event now includes the detected optimization tool (`wp_rocket`,`
   perfmatters`, `nitropack`). The dashboard banner and the email alert can now 
   name the specific plugin causing the delay.
 * **Plugin-side:** no PHP code change in this version; new signals are in the canonical
   pixel that the plugin enqueues. Sites running plugin 1.0.3+ already get the new
   signals automatically — the 1.0.6 bump captures the changelog so admins know 
   whatÌtumọ̀ Yorùbá: ’s new on their dashboard.

#### 1.0.5

 * **New:** when the plugin detects Perfmatters, W3 Total Cache, or Hummingbird 
   active on the site (the three optimization plugins that have no HTML-attribute
   opt-out), an admin notice now appears with the exact URL pattern to paste into
   that pluginÌtumọ̀ Yorùbá: ’s exclusion list. Dismissible per-user. We deliberately
   do NOT show the notice for WP Rocket, LiteSpeed, Autoptimize, WP Fastest Cache,
   NitroPack, or Cloudflare Rocket Loader because the 1.0.4 attribute carpet already
   handles those.
 * **New:** dismiss endpoint `/wp-json/harvv/v1/dismiss-lazyload-notice` (admin-
   gated; per-user user_meta).

#### 1.0.4

 * **Performance:** the pluginÌtumọ̀ Yorùbá: ’s pixel `<script>` tag now ships with
   the full carpet of vendor-specific exclusion attributes so it is exempt from 
   delay-JS / lazy-load passes in WP Rocket, LiteSpeed Cache, Autoptimize, WP Fastest
   Cache, NitroPack, and Cloudflare Rocket Loader. Before 1.0.4 these tools could
   catch our pixel and delay it until first user interaction, which meant we missed
   the initial-paint Core Web Vitals (LCP / INP / CLS) on every session. After 1.0.4
   the pixel boots immediately regardless of which optimization tool is installed.
 * **Documentation:** three tools (Perfmatters, W3 Total Cache, Hummingbird) have
   no HTML-attribute opt-out — exclusion is URL-pattern only via their respective
   settings pages. The new FAQ entry “How do I keep Harvv exempt from my optimization
   plugin?” lists the exact URL pattern to paste into each.
 * **Internal:** new `Harvv_Enqueue::inject_exclusion_attrs()` method, hooked on`
   script_loader_tag`. Attribute set researched 2026-05-13 against each vendorÌtumọ̀
   Yorùbá: ’s primary documentation. Conflict-free (each tool only inspects its 
   own attribute).

#### 1.0.3

 * **Architecture:** the plugin now loads the canonical Harvv pixel directly from`
   https://harvv.com/px/<site_key>/pixel.js` instead of a bundled copy of `tracker.
   min.js`. New behavioral signals shipped to the canonical pixel propagate to your
   site within minutes — no plugin update required. Same source of truth our Laravel
   package and direct-install path already use.
 * **Privacy + security:** the per-site key is no longer rendered into page source
   via `wp_localize_script`. The canonical pixel identifies the site via its URL
   path and the server-injected preamble. Tighter exposure surface for the (public-
   but-still-best-not-broadcasted) key.
 * **Compat:** offline-capable installs can pin to a self-hosted mirror via `define('
   HARVV_PIXEL_URL', '...' );` in `wp-config.php`. The `harvv_pixel_url` filter 
   is also available for runtime overrides.
 * **Internal:** new double-install guard (`window.__harvvLoaded__`) so a site running
   both the WP plugin AND the canonical script tag wonÌtumọ̀ Yorùbá: ’t double-fire
   events. First one to boot wins; second one bails cleanly. The reconciliation 
   event is also recorded server-side via `sites.install_sources` so the dashboard
   can show “both paths installed since X”.
 * **Compat:** the bundled `tracker.min.js` stays in the plugin directory for backward
   compat (CDN cache TTLs), but the enqueue no longer references it. Slated for 
   removal in a future release.

#### 1.0.2

 * **New:** site-context snapshot — sends a list of installed plugin slugs + versions,
   active theme, WordPress/PHP/MySQL versions, server software, locale, timezone,
   memory limit, post and page counts, custom post type slugs + counts, total user
   count, object cache backend, WooCommerce details when active, and other site-
   level configuration to Harvv. The dashboard uses this to attribute UX issues 
   to the plugin or platform configuration causing them. Site metadata only — no
   personal data, no user content, no usernames, no emails, no per-user data.
 * **New:** “Preview the exact diagnostic snapshot we would send” reveal on the 
   settings page. Renders the literal JSON payload before itÌtumọ̀ Yorùbá: ’s sent,
   so admins can audit before opting in. (Reviewer-friendly transparency pattern.)
 * **New:** weekly WP-Cron event refreshes the snapshot so the dashboard stays current
   as the site changes.
 * **New:** opt-out UI on the settings page under **Preferences  Share stack info**.
   Defaults to on; uncheck to disable. Code-level opt-outs also available: `define('
   HARVV_SHARE_INVENTORY', false );` in `wp-config.php` or `add_filter( 'harvv_share_inventory','
   __return_false' );`.
 * **Privacy:** suggested-policy text in Settings  Privacy now mentions the snapshot
   and how to disable it. Readme `External Services` section enumerates every field
   that ships.
 * **Internal:** new option keys `harvv_share_inventory`, `harvv_last_inventory_sync_ts`,`
   harvv_last_inventory_error` (cleaned up on uninstall). New WP-Cron hook `harvv_inventory_refresh`(
   cleared on uninstall). New REST endpoint `/wp-json/harvv/v1/diagnostic-preview`(
   admin-gated; returns the next payload that would be sent).

#### 1.0.1

 * **New:** plugin now defaults to auto-update so new behavioral signals + bug fixes
   ship without manual intervention. Opt out by defining `HARVV_AUTO_UPDATE` as `
   false` in `wp-config.php`.
 * **Fix:** auto-register now runs on single-site installs (was multisite-only —
   single-site admins who only pasted a Site Key would never get a Site ID assigned,
   and the tracker would silently never load).
 * **Fix:** API base URL switched from `api.harvv.com` (DNS NXDOMAIN) to `harvv.
   com`. The Connect flow, registration endpoint, and Woo `/v1/track` ingest now
   resolve to the production receiver. Existing installs with `HARVV_API_BASE` overridden
   in `wp-config.php` keep their override.
 * **UX:** “API key” renamed to “Site key” throughout the UI to reflect public-key
   semantics (like a Stripe publishable key). Help text explains why itÌtumọ̀ Yorùbá:’
   s safe to expose in page source.
 * **Observability:** Settings page now shows the time since the most recent successful
   WooCommerce sync, and the most-recent sync error (if any), on Woo-enabled sites.
   Helps spot a silently broken integration without cracking open the WP debug log.
 * **Observability:** Settings page now surfaces a red error message under the Site
   ID field when auto-register fails, with a hint that re-saving retries immediately.
 * **Docs:** Readme now documents the `harvv_should_load_tracker` filter and the`
   HARVV_API_BASE` override constant, both of which existed in code but werenÌtumọ̀
   Yorùbá: ’t surfaced anywhere user-facing.
 * **Internal:** `Harvv_Multisite::maybe_auto_register_subsite()` removed — the 
   logic moved to `Harvv_Core::maybe_auto_register()`. Network-admin UI and per-
   subsite override behavior unchanged.

#### 1.0.0

 * Initial release.
 * Behavioral tracker (dead clicks, rage clicks, scroll depth, hover intent, JS 
   errors, engagement).
 * WooCommerce `payment_complete` order sync.
 * HPOS (Custom Order Tables) compatibility declared.
 * Connect-to-Harvv flow with one-shot nonce + HMAC-signed callback.
 * Manual API-key entry as alternative path.
 * Multisite support with per-subsite override.
 * WordPress Privacy API integration (suggested policy text + empty exporter).

## Àkójọpọ̀ Meta

 *  Ẹ̀yà **1.0.8**
 *  Ìgbàgbọ́hùn tó kẹ́yìn **wákàtí 19 sẹ́yìn**
 *  Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10**
 *  Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ **
 *  Dánwò dé **6.9.4**
 *  Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ **
 *  Èdè
 * [English (US)](https://wordpress.org/plugins/harvv-analytics/)
 * Àwọn àmì
 * [analytics](https://yor.wordpress.org/plugins/tags/analytics/)[behavioral analytics](https://yor.wordpress.org/plugins/tags/behavioral-analytics/)
   [conversion tracking](https://yor.wordpress.org/plugins/tags/conversion-tracking/)
   [privacy](https://yor.wordpress.org/plugins/tags/privacy/)[woocommerce](https://yor.wordpress.org/plugins/tags/woocommerce/)
 *  [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/harvv-analytics/advanced/)

## Àwọn ìbò

Kò sí ìwádìí tí a tíì fi ránṣẹ́.

[Your review](https://wordpress.org/support/plugin/harvv-analytics/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/harvv-analytics/reviews/)

## Àwọn Olùkópa

 *   [ Harvv ](https://profiles.wordpress.org/ecommercepros505/)

## Ìrànlọ́wọ́

Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?

 [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/harvv-analytics/)