Treat hash routes as separate pages

By default, Feedbucket ignores the hash (#...) when deciding which feedback belongs to the current page.
That works for normal websites, but hash-based SPAs (for example React or Vue apps using /#/dashboard) can look like one single page.

To treat each hash as its own page, set this before loading the widget:

<script> window.feedbucketConfig = { treatHashAsPage: true } </script> 

With this option enabled:

• https://example.com/#/dashboard and https://example.com/#/settings are treated as different pages.
• Feedback and pins are shown per hash route.
• Existing behavior stays the same if this setting is not used.

Updated on: 12/08/2026