PostHog Reverse Proxy

A reverse proxy allows you to send events to PostHog Cloud using your own domain.

This means that events are less likely to be intercepted by tracking blockers. You'll be able to capture more usage data without having to self-host PostHog.

Setting up a reverse proxy means setting up a service to redirect requests from a subdomain you choose (like e.yourdomain.com) to PostHog. It is best practice to use a subdomain that does not include posthog, analytics, tracking, or other similar words.

You then use this subdomain as your api_host in the initialization of PostHog instead of us.i.posthog.com or eu.i.posthog.com.

posthog.init('phc_YOUR_TOKEN', {
  api_host: 'https://e.yourdomain.com'
})

Custom domain

It's recommend that you associate this service to a custom domain. If your frontend service is yourdomain.com, make this service e.yourdomain.com.

Environment Variables

This template requires two environment variables, SERVER_NAME and PORT. Both are set by default by the template and don't need to be changed.

SERVER_NAME is set to ${{RAILWAY_PUBLIC_DOMAIN}}

PORT is the port through which Railway will contact this service, by default it's 80 but it pretty much doesn't matter.