HARVV ANALYTICS

Harvv Analytics | REEID Translate Compatibility

REEID processes supported labels, notices and consent-related text while Harvv Analytics remains responsible for tracking IDs, events, measurement and analytics data.

Visit Harvv Analytics ↗

AWAITING VERIFICATION

Translate visible text. Preserve measurement logic.

Multilingual visitor-facing wording stays separate from tracking configuration, event definitions and collected analytics data.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.

DATA-SAFE
Tracking IDs, events, measurement rules and collected analytics data remain functional configuration.

PRACTICAL WORKFLOW

Translation workflow

01 · Configure analytics normally
Maintain tracking, events and measurement settings through Harvv Analytics.

02 · Identify visible analytics text
Locate supported consent labels, notices, embedded labels or other visitor-facing wording.

03 · Translate supported wording
Process multilingual text without altering IDs, event names or measurement configuration.

04 · Validate tracking and frontend text
Review translated wording while confirming analytics collection still behaves as intended.

SUPPORTED CONTENT

Translation scope

Visitor-facing text
Replace this draft item with the exact evidence-backed content coverage.

Interface content
Document supported labels, titles or interface strings where applicable.

Product-specific content
Add confirmed product-specific support before publication.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • Frontend behavioral tracking via a bundled vanilla-JS tracker (no jQuery) that captures interaction signals such as scroll depth, click targets (CSS selectors), dead/rage clicks, hover intent, JavaScript errors, and engagement time.
  • No-cookie / no-device-storage behavioral design: the plugin states it does not set or read cookies and does not store personal data in the WordPress database; it also states it does not load JavaScript from external URLs (the tracker is bundled).
  • Event transmission to Harvv endpoints: behavioral events are sent continuously while a visitor is on the site (batched every ~5 seconds or on tab close using `navigator.sendBeacon` when available), and WooCommerce order events are sent once on `woocommerce_payment_complete` using non-blocking HTTP calls.
  • WooCommerce order synchronization with non-reversible customer hashing: the plugin states it syncs order ID/status/total, line-item product IDs and quantities, coupon codes, payment/shipping method names, and a non-reversible customer hash derived from WordPress salts (via `wp_hash()`), and it states it does not transmit raw email/PII fields.
  • WooCommerce HPOS (Custom Order Tables) compatibility: the plugin claims compatibility with `custom_order_tables` and states it uses the WooCommerce Order CRUD API rather than direct `$wpdb` access to order tables.
  • Multisite-aware operation: the plugin states it is multisite-aware with one network API key, per-subsite Site IDs, and per-subsite admin overrides; it also states it registers each subsite on next pageload.
  • Optional frontend load control via a filter: the plugin documents a `harvv_should_load_tracker` filter that can prevent the tracker from being enqueued (e.g., returning `false` before `wp_enqueue_script`).

Distinctive features
Frontend behavioral tracking via a bundled vanilla-JS tracker (no jQuery) that captures interaction signals such as scroll depth, click targets (CSS selectors), dead/rage clicks, hover intent, JavaScript errors, and engagement time. No-cookie / no-device-storage behavioral design: the plugin states it does not set or read cookies and does not store personal data in the WordPress database; it also states it does not load JavaScript from external URLs (the tracker is bundled). Event transmission to Harvv endpoints: behavioral events are sent continuously while a visitor is on the site (batched every ~5 seconds or on tab close using `navigator.sendBeacon` when available), and WooCommerce order events are sent once on `woocommerce_payment_complete` using non-blocking HTTP calls. WooCommerce order synchronization with non-reversible customer hashing: the plugin states it syncs order ID/status/total, line-item product IDs and quantities, coupon codes, payment/shipping method names, and a non-reversible customer hash derived from WordPress salts (via `wp_hash()`), and it states it does not transmit raw email/PII fields. WooCommerce HPOS (Custom Order Tables) compatibility: the plugin claims compatibility with `custom_order_tables` and states it uses the WooCommerce Order CRUD API rather than direct `$wpdb` access to order tables. Multisite-aware operation: the plugin states it is multisite-aware with one network API key, per-subsite Site IDs, and per-subsite admin overrides; it also states it registers each subsite on next pageload. Optional frontend load control via a filter: the plugin documents a `harvv_should_load_tracker` filter that can prevent the tracker from being enqueued (e.g., returning `false` before `wp_enqueue_script`).

Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.

SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.

URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.

Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.

CONTENT BOUNDARY

Separate multilingual wording from analytics data and tracking logic.

REEID handles supported visitor-facing text while Harvv Analytics controls tracking configuration, measurement logic and analytics data.

Tracking IDs, event configuration and collected data are not translation content.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

Harvv Analytics and REEID Translate FAQ.

Does REEID Translate work with Harvv Analytics?

REEID Translate Pro processes the supported visitor-facing fields documented for this integration while Harvv Analytics retains control of its own functionality.

Does REEID translate or alter tracking IDs and events?

No. Tracking identifiers, event definitions and measurement rules remain controlled by Harvv Analytics.

Can consent or visitor-facing analytics labels be translated?

Yes when those strings are available through supported visitor-facing content paths.

RELATED GUIDES

Continue through the compatibility library.

ANALYTICS INTEGRATION

Translate visitor-facing Harvv Analytics text without disturbing analytics.

Keep multilingual wording separate from tracking IDs, events and measurement logic.

Supported content and limitations are defined by the integration record.

Shopping Cart
Scroll to Top