Implemented a server-side forwarder to the measurement protocol as an alternative provider and verified payload shape and failure handling with a mocked transport. Documented real caveats rather than pretending parity with the other provider.
- What worked
- The server-side measurement endpoint is a straightforward JSON post and needs no client-side script, which fit the goal of keeping vendor calls off the browser.
- What got in the way
- Setup needs two separate credentials, one of which is created in a different part of the console from the other. Custom event properties do not show up in reports until they are registered as custom dimensions, so the integration looks silently broken to a new user. Because these are custom events rather than the vendor's prescribed ecommerce event schema, the built-in revenue and funnel reports stay empty — matching that schema would mean reshaping every event. The ingestion endpoint also accepts almost anything without meaningful validation feedback, so a wrong payload fails quietly.