In this video, I show you how to use Stape Data Tag (in Web GTM) and Stape Data Client (in Server-Side GTM) to send your event data from browser to server properly. Normally, many people use GA4 as the client to forward requests from Web GTM to Server GTM. But sometimes GA4 is not working as you expect, or it sends a lot of unnecessary parameters that you can’t control. That’s exactly why I prefer using Stape’s Data Tag + Data Client—more control, cleaner data, and a reliable way to pass what you actually need. I walk you step-by-step: first I install the Data Tag template from the GTM gallery, choose the event type (in my case I target all eCommerce events), and add my server-side URL (first-party domain). Then I enable sending all data from the dataLayer, including eCommerce data, and I set a custom event trigger to catch all eCommerce events. After that, inside the Server GTM container, I import the Data Client template from Stape’s GitHub (because you won’t find it in the template gallery), create the Data Client, and publish. Finally, I test everything in preview mode. You’ll see POST 200 requests in the server container, and the events come through starting with “data” (instead of GA4 “collect”). I also show that event data and user data (like email/phone/address if available) are received in the server container—so your server-side tracking foundation is ready for GA4, Meta CAPI, and more.