--- title: "SSR apps" description: "Server-rendered apps (Rails, Django, Express, Next.js Pages Router, Remix) work like static sites. The CanaryLytics snippet runs in the browser after the page loads." last_updated: "2026-07-30" --- # SSR apps Server-rendered pages work exactly like static sites from the tracker's point of view: the snippet is inert until the browser parses and executes it, so it doesn't matter whether the surrounding HTML came from a template on disk or was rendered per-request on the server. Include the snippet in whatever shared layout or partial renders your `` (or the end of ``): ```html ``` That is the whole integration for classic server-rendered apps. There is no client-side router to patch and no hydration timing to worry about. If your SSR framework layers a client-side router on top of the initial server render (Next.js, Remix, SvelteKit, Nuxt, and similar "SSR + SPA navigation" frameworks), the snippet's `history.pushState`/`replaceState` patching picks up client-side route changes automatically once the app hydrates. ## Related ## Sitemap - [Docs sitemap](https://analytics.canarycoders.es/docs/sitemap.md) - [Full documentation as a single file](https://analytics.canarycoders.es/llms-full.txt)