Inconsistent GA4 Event Delivery via Server-Side GTM on Download Portal

Google Tag Manager Server Container
1

I recently set up a Stape server-side container to capture user engagement and conversion events on our utility portal. While page_view events appear reliably in the debugger, custom interaction events—specifically when users initiate a deltaeutor setup flow—frequently fail to reach GA4 or experience significant latency.

Upon checking the network tab, the incoming requests to our custom domain endpoint return 200 statuses, but the outgoing requests mapped to the analytics endpoint occasionally report payload validation errors. We are currently trying to isolate whether this stems from strict CORS policies, header stripping, or cookie storage conflicts with modern ad-blocking browsers.

Has anyone encountered similar event routing mismatches when handling dynamic client triggers through Stape, and what server container settings helped ensure consistent forwarding?

2

Hi,
Thanks for the detailed information. Since the incoming requests return 200, I’d first recommend checking the server container logs for the affected events and comparing them with successfully processed page_view requests.

Please also verify that the custom events are actually being sent to the server-side container and that the Google tag isn’t being overwritten or replaced before the request is sent. This will help determine whether the issue occurs on the client side or during server-side processing and forwarding to GA4.