Full Answer
The distinction between GTM hosting and GTM replacement defines the two architectural categories in server-side tracking for WordPress. GTM hosting keeps GTM at the centre — you still build tags, configure triggers, manage variables, and debug using GTM's interface. The hosting provider manages the cloud infrastructure the container runs on.
GTM replacement removes GTM from the architecture entirely. Event capture happens through WordPress hooks — woocommerce_payment_complete, woocommerce_add_to_cart — with no Data Layer push, no JavaScript tag, and no GTM container involved. Event processing happens on a dedicated server that validates, enriches, and formats each event. Destination delivery happens through direct API calls — GA4 Measurement Protocol, Facebook CAPI, Google Ads Enhanced Conversions API, BigQuery Streaming Insert — each with its own connector module.
The operational difference is who maintains the system and where. GTM hosting requires GTM expertise — a specialised skill set that most WordPress developers and store owners do not have. GTM replacement requires WordPress expertise — a skill set that anyone operating a WooCommerce store already possesses or has access to through their existing developer.
The term matters because marketing language in the server-side tracking space often blurs the distinction. A provider describing their service as server-side tracking for WordPress could mean either category. Asking whether the solution requires a GTM container is the clarifying question that separates hosting from replacement.