> ## Documentation Index > Fetch the complete documentation index at: https://docs.veristar.app/llms.txt > Use this file to discover all available pages before exploring further. # React Router with server rendering > Add the tracker to a React Router app in framework mode with server rendering. For React Router in framework mode (the successor of Remix), rendered on the server. Tested by the example [`examples/react-router-ssr`](https://github.com/justmert/veristar/tree/main/examples/react-router-ssr) (React Router 8.4.0 with `ssr: true`, served by `@react-router/serve`), which runs in the browser test matrix. ## Where the tag goes Render the tag as a ` ``` Write `crossOrigin` in JSX; React renders it as `crossorigin`. ## Route changes The first load is server rendered and is one pageview. Later navigations happen on the client with `history.pushState`, which the tracker watches, so each is one pageview; back and forward too. ## Custom events Declare `window.umami` once and call it with optional chaining, as in the [Vite and React guide](https://docs.veristar.app/onboarding/web/vite-react.md#custom-events); the example's [`app/routes/home.tsx`](https://github.com/justmert/veristar/blob/main/examples/react-router-ssr/app/routes/home.tsx) does exactly that. ## What the browser tests check One pageview per server-rendered load and per client-side navigation, back and forward, the previous route as referrer, an external referrer on the first pageview, the tag rendered with the release's integrity value, both kinds of custom event, Global Privacy Control and a tampered tracker refused (`tests/e2e/specs`, `examples/react-router-ssr/test`). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.