TRACKING HIPPO SERVER-SIDE TRACKING
Tracking Hippo Server-Side Tracking compatibility with REEID Translate
Tracking Hippo Server-Side Tracking compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side Google Tag Manager container integration with optional first-party loader that can inject the GTM web snippet into the site’s “, after “, in the footer, or not at all (data layer only). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Tracking Hippo Server-Side Tracking.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Tracking Hippo Server-Side Tracking is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Tracking Hippo Server-Side Tracking compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Server-side Google Tag Manager container integration with optional first-party loader that can inject the GTM web snippet into the site’s “, after “, in the footer, or not at all (data layer only).
- First-party loader serves `gtm.js` from a configured container domain (with optional custom path) instead of loading from `googletagmanager.com`, intended to improve resilience against ad blockers/tracking prevention.
- Consent Mode v2 support that publishes a `gtag('consent', 'default', …)` command ahead of the container, covering seven consent signals (including `ad_user_data` and `ad_personalization`), with configurable targeting (global EEA/UK or custom region list) and options such as `wait_for_update`, `ads_data_redaction`, and `url_passthrough`.
- GA4 ecommerce event mapping for WooCommerce, including a full funnel of ecommerce events (e.g., view_item_list through purchase) and additional login/sign_up events, with support for both classic and Cart/Checkout blocks via WooCommerce data stores/conditional tags.
- Ecommerce event payload enrichment for GA4, including rich item fields such as `item_brand`, `item_variant`, `item_category` through `item_category5`, `discount`, and list attribution (carrying the clicked listing into later add_to_cart).
- Server-side webhooks for conversion events (purchase, refund, order_paid) delivered from the server to the configured container endpoint, executed on a WP-Cron tick with retry behavior (exponential backoff) and configurable timeout/headers (including optional shared-secret).
- Webhook payloads include analytics identifiers and checkout-captured context (e.g., client/session identifiers and GA cookies), and customer PII fields (email/phone/name/address fields) are SHA-256 hashed by default; delivery logs include the last ten deliveries.
CONTENT BOUNDARY
Tracking Hippo Server-Side Tracking capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Tracking Hippo Server-Side Tracking and REEID Translate FAQ.
What does Tracking Hippo Server-Side Tracking do according to the available plugin evidence?
Tracking Hippo Server-Side Tracking has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Tracking Hippo Server-Side Tracking?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Tracking Hippo Server-Side Tracking?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Tracking Hippo Server-Side Tracking in a multilingual WordPress workflow.
REEID documents Tracking Hippo Server-Side Tracking functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.