Welcome to Human Behavior
What Human Behavior records, how access works, and what to do after we unlock your workspace.
Human Behavior watches what real people do in your product and keeps the evidence: the session as a replayable recording, the events they fired, the errors they hit, and who they were. Access is sales-led — we get you live. These docs are the reference once your workspace is unlocked.
How you get access
- Book a call from the marketing site (or ask us in Slack if you already have a channel).
- We agree on a plan and send a Stripe invoice.
- After payment, we unlock your project.
- You (or we, together) finish Project Setup → Install → Verify.
There is no public self-serve checkout. Details: Billing and access.
The problem it solves
Most teams answer product questions with three disconnected tools. The analytics
tool says signups dropped 12%. The error tracker says there is a TypeError in
checkout.tsx. The replay tool has a video somewhere. Nothing connects them, so
someone spends an afternoon proving that the three facts are the same fact.
Human Behavior records them together. An error in Issues links to the replay of the session that produced it. A dip in the Dashboard links to the visitors behind it. And because the data lives in one place, you can ask a question in plain language instead of building a query.
What gets installed
One browser package: humanbehavior-js. It records the session with rrweb and
posts batches to our ingestion service. From that install you get, with no
extra instrumentation:
- Session replays — what the person actually saw and clicked
- Autocaptured events — page views, clicks, rage clicks, dead clicks, form submissions
- Errors — uncaught exceptions and unhandled rejections, grouped into issues
- Visitors — anonymous people, upgraded to named people once you identify them
Two things need a line of code each: identifying logged-in
users and tracking business
events like signed_up.
We often run install with you on the call or in Slack. When you (or your engineer) do it yourselves, use the wizard or the pages below.
Where the data shows up
- Home answers questions about the project in plain language
- Replays shows individual sessions you can watch
- Issues groups errors so you fix a problem, not a stack trace
- Dashboard charts traffic, pages, sources, and devices
- Agents run saved instructions against that data on a schedule
More detail: how the product fits together.
After access
Once your workspace is unlocked:
- Create a project and get an API key — often already started with us
- Install the SDK — wizard or manual
- Verify data is flowing
- Get your first answer
Invited teammates may hit Welcome and user profile once on first sign-in.