Hi @Ajay_Rabari! App Proxy requests are only forwarded to your backend once the client has passed the storefront password gate. The password page is pre-authentication by definition, so a request fired from it hasn’t cleared the gate yet and gets redirected (302) to /password. That’s exactly why it works on every other page, where the visitor has already entered the password and their session is authenticated, but not on the password page itself. This came up here where a colleague confirmed the same thing, that the client making the proxy request needs storefront access first, otherwise it returns the password/login page.
So for analytics specifically on the password page, there’s no way around it with an App Proxy. Your direct-to-server approach is the right call there!