[WordPress] 外掛分享: Tracking Hippo Server-Side Tracking

首頁外掛目錄 › Tracking Hippo Server-Side Tracking
WordPress 外掛 Tracking Hippo Server-Side Tracking 的封面圖片
全新外掛
安裝啟用
尚無評分
13 天前
最後更新
問題解決
WordPress 5.9+ PHP 7.2+ v1.0.0 上架:2026-08-17

內容簡介

Tracking Hippo Server-Side Tracking 將您的 WordPress 網站連接到 Tracking Hippo 上的伺服器端 Google Tag Manager (sGTM) 容器,透過伺服器端標記提升數據質量、頁面性能,並抵抗廣告攔截器和瀏覽器追蹤限制。

【主要功能】
• 伺服器端標記提升數據質量
• 自訂的第一方加載器,避免廣告攔截
• GA cookies 重新發行,解決 Safari 限制
• 健康面板檢查容器狀態
• 支援 WooCommerce 的 GA4 電子商務追蹤

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Tracking Hippo Server-Side Tracking」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

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 , after , in the footer — or not at all, if you only want the data layer.
First-party loader — serves gtm.js from 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

Consent Mode v2

Publishes the gtag('consent', 'default', …) command ahead of the container, covering all seven signals including ad_user_data and ad_personalization.
Apply the defaults globally, to the EEA and UK, or to a custom region list.
wait_for_update, ads_data_redaction and url_passthrough are 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/cart data store — so the block checkout is covered as fully as the classic one.
Rich items: item_brand, item_variant, item_category through item_category5 from the real category hierarchy, discount, index, and item_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_id is 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.
purchase is deduplicated per order, carries customer_type (new or returning), and can include hashed customer data for Enhanced Conversions.

Server-side webhooks

Sends purchase, refund and order_paid from 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.

延伸相關外掛

文章
Filter
Mastodon