Tracking Hippo Server-Side Tracking Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Tracking Hippo Server-Side Tracking links your WordPress site to a server-side Google Tag Manager (sGTM) container hosted on Tracking Hippo. Server-side tagging moves tracking out of the visitor’s browser and onto your own first-party server, which improves data quality, page performance and resilience against ad blockers and browser tracking restrictions.
Container
- Injects the Google Tag Manager web snippet in
<head>, after<body>, in the footer — or not at all, if you only want the data layer. - First-party loader — serves
gtm.jsfrom your own container domain, with an optional custom path, so ad blockers and tracking prevention no longer recognise it. - GTM environments (
gtm_auth/gtm_preview), a configurable data layer variable name, and an optional<noscript>fallback. - Cookie keeper — re-issues the GA cookies from the server so Safari’s seven-day cap on script-set cookies stops truncating returning-visitor attribution.
- Exclude specific user roles, and stop tracking entirely outside production.
- A built-in health panel warns about a missing container ID, a container on a third-party domain, a duplicate GTM plugin, or WP-Cron being disabled — and a Test connection button checks your container is live.
Consent Mode v2
- Publishes the
gtag('consent', 'default', …)command ahead of the container, covering all seven signals includingad_user_dataandad_personalization. - Apply the defaults globally, to the EEA and UK, or to a custom region list.
wait_for_update,ads_data_redactionandurl_passthroughare all configurable, and the plugin warns you when a consent plugin is already publishing its own defaults.
GA4 ecommerce for WooCommerce
The complete funnel: view_item_list, select_item, view_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info and purchase, plus login and sign_up.
- Works with the Cart and Checkout blocks. Page events use WooCommerce’s conditional tags rather than template hooks, and cart changes are detected from the
wc/store/cartdata store — so the block checkout is covered as fully as the classic one. - Rich items:
item_brand,item_variant,item_categorythroughitem_category5from the real category hierarchy,discount,index, anditem_list_id/item_list_name. - List attribution carries the listing a product was clicked from into the later
add_to_cart, so GA4 can credit the right list. - Choose whether
item_idis the SKU or the product ID, add a prefix to match your product feed, and report revenue with or without tax. { ecommerce: null }is pushed before every ecommerce event, as GA4 requires.purchaseis deduplicated per order, carriescustomer_type(new or returning), and can include hashed customer data for Enhanced Conversions.
Server-side webhooks
- Sends
purchase,refundandorder_paidfrom your server to your container, so conversions survive a browser that blocks every script. - Delivery runs on a background cron tick, so checkout is never slowed down, and failures retry with exponential backoff.
- The payload carries the GA cookies, client ID and session ID captured during checkout, so the server event joins the same GA4 session.
- Optional shared-secret header, configurable timeout, and a log of the last ten deliveries.
Works on a plain WordPress site and adds the WooCommerce events automatically when WooCommerce is active. Compatible with High-Performance Order Storage.
Links
- Tracking Hippo — WordPress setup guide — Modules — Pricing
- FAQ — Contact support — Service status — Give feedback
- Privacy policy — Terms of service — Data processing agreement — Cookie policy
External services
This plugin connects your site to a server-side Google Tag Manager container. Nothing is transmitted until you enter a container URL in the settings.
Your GTM server container (the domain you configure, hosted by Tracking Hippo or elsewhere)
- Browser requests: when the first-party loader is enabled, visitors’ browsers download the container script from your container domain instead of googletagmanager.com. The request carries the visitor’s IP address, user agent and any analytics cookies, exactly as the Google-hosted script would.
- Server requests: when webhooks are enabled, your server sends order events to the endpoint you configure. Each delivery can contain the order total and line items, the customer’s email, phone, name and billing address, plus the analytics identifier, IP address and user agent captured at checkout. Email, phone and name are SHA-256 hashed by default.
- Both are governed by Tracking Hippo’s terms of service, privacy policy and data processing agreement. If you point the plugin at a container hosted elsewhere, that provider’s terms apply instead.
Google Tag Manager (googletagmanager.com)
- Used only as a fallback: with no server container URL configured, the container script is loaded from Google, subject to Google’s terms and privacy policy.
The plugin also stores, on each order, the analytics identifier, IP address and user agent captured at checkout, so orders can still be attributed when they are delivered later. This data is removed with the order, and everything the plugin stores is deleted when it is uninstalled. Suggested privacy-policy wording is added to Tools Privacy for you to review.
Screenshots
The Container tab — server container URL, web container ID, first-party loader and custom loader path, with the health panel showing live status for the container, Consent Mode, ecommerce and webhooks.
Consent Mode v2 defaults for all seven signals, targeted at the EEA and UK, with
wait_for_update,ads_data_redactionandurl_passthrough.
The base data layer — page, post, author, search and language context, plus logged-in customer details, SHA-256 hashing and the WordPress user ID.
The complete GA4 ecommerce funnel for WooCommerce, with the
item_idsource, an item prefix and the brand taxonomy used foritem_brand.
Server-side webhooks — endpoint, the events to send, which order statuses count as a purchase, and exactly what the payload carries.
