Clarification for correct configration of endpoints for a domain proxy

Hi @eddie.gaona thank you for helping out!

Yes, we have our own domain and are using the npm module @amplitude/analytics-browser in our React app to instrument it. We want to host the tracking endpoint at our domain under the path /amplitude. We are running a node express server on our domain and I’ve setup the express-http-proxy middleware for this purpose. Our node.js express server code for that looks like this:

import proxy from 'express-http-proxy';

app.use('/amplitude',
  proxy('https://api2.amplitude.com/', {
    proxyReqPathResolver: function (req) {
      // rewrite the request path to /2/httpapi
      return '/2/httpapi'
    },
  })
);

In the React App, we initialize the library with:

import * as amplitude from '@amplitude/analytics-browser';

amplitude.init(
  process.env.REACT_APP_AMPLITUDE_API_KEY,
  '',
  {serverUrl: 'https://ourdomain.com/amplitude'}
);

Then on app events, we instrument with this code:

import { track } from '@amplitude/analytics-browser';

// ... example button click handler ...
handleButtonClick = (name) => {
  track("Button Click", {name});
  // ... process the actual button action
}

In development, this appears to work well. However, I don’t know if it’s configured correctly because, as I noted in my first post, the guide document says the /2/httapi endpoint should be used only temporarily for testing so I would like to understand the meaning of that statement clearly.

Thank you