Full Answer
Server-side GTM works for TikTok the same way it does for other platforms. Your web container or a server-side data layer sends the event to the server container, and a TikTok Events API tag template builds the API call and posts it to TikTok. Because the outbound request originates from your server, ad blockers and ITP don't touch it, and you can enrich the payload with hashed customer data and the ttclid click identifier.
The caveat is operational cost and complexity. Server-side GTM is not free infrastructure: you provision a tagging server, keep it patched, and pay for the compute, which lands most small stores in the $50-120 per month range before anyone has configured a single tag. You also still own the mapping work, translating WooCommerce events into TikTok's expected schema and managing deduplication with the Pixel.
That's why the honest framing is architectural, not technical. If you already run server-side GTM for Google and Meta, adding TikTok is incremental and sensible. If you don't, standing up a GTM server purely for TikTok is a lot of moving parts when a WordPress-native pipeline that posts directly to the Events API can deliver the same server-side resilience without the container layer. Either path gets events off the browser; they differ mainly in how much infrastructure you maintain.