CHAPTER 01
Install the snippet
Drop this before the closing </body> tag. It loads async and weighs under 8 KB — your users won't notice it.
<!-- Nigrumhodo trail camera --> <script src="https://cdn.nigrumhodo.xyz/hodo.js" data-key="YOUR_KEY"></script>
Privacy note: the snippet never reads input values, keystrokes, or page content — only navigation events. See Security for the full allowlist.
CHAPTER 02
Define your designed flows
Tell us the paths you designed — onboarding, checkout, settings. Trails are interesting only against the map they deviate from.
- Name each flow in plain language ("signup → onboarding → first project").
- Mark the steps with data attributes or let us detect routes automatically.
- Start with one flow. The messiest one.
CHAPTER 03
Read the trail map
After a few days of traffic, open your map. Thick amber trails are desire paths — heavily walked routes you never designed. Thin gray ones are the designed flows nobody takes.
Reading tip: a desire path that bypasses two designed steps is a feature request written in footprints. Pave it.
CHAPTER 04
Act on the evidence
- Each trail ships with counts, trends, and the flows it bypasses — screenshot-ready for roadmap meetings.
- Set alerts: get pinged when a new desire path forms or a dead trail grows.
- Re-map after each release to see whether the paving worked.