How to capture paths from hash-based routing

Hash-based routing is a common way to manage navigation in single-page applications (SPAs) using the URL hash. This tutorial shows you how to set up PostHog to work with hash-based routing, ensuring that pageviews and events are tracked correctly.

Capturing paths in hash-based routing

When using hash-based routing, the URL path is typically in the format http://example.com/#/path/to/page. The $pathname property in PostHog will not automatically include the hash part of the URL. In this example, it will just be /.

To add the hash to the $pathname property, you can use the before_send function in PostHog's initialization. This function allows you to modify events before they are sent to PostHog.

The below example is how you can change the $pathname property to include the hash, so in the example above it will be /#/path/to/page:

import posthog, { CaptureResult } from 'posthog-js'

posthog.init('<ph_project_token>', {
  api_host: 'https://us.i.posthog.com',
  defaults: '2026-05-30',
  before_send: (event: CaptureResult | null): CaptureResult | null => {
    if (event?.properties?.$current_url) {
      // parse the URL
      const parsed = new URL(event.properties.$current_url)

      // if there is a hash in the URL, we want to include it in the $pathname property
      if (parsed.hash) {
        event.properties.$pathname = parsed.pathname + parsed.hash
      }
    }
    return event
  },
})

Which libraries are affected?

The most common routing libraries that use hash-based routing are:

• React Router - with the HashRouter component.
• TanStack Router - with createHashHistory
• SvelteKit - with router.type === 'hash'
• Vue Router - with createWebHashHistory