Hotjar combines heatmaps, session replays and surveys to surface qualitative user behaviour. The tool helps teams identify UX issues and analyse conversion barriers. It integrates easily and is commonly used during product and design iteration cycles.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
Hotjar is a behavioral analytics and user-feedback platform combining heatmaps, session recordings, surveys, and interviews for digital products.
The company launched in 2014 to complement quantitative web analytics with observable behavior and direct feedback.
A tracking script captures permitted interactions and page states. Heatmaps aggregate clicks and scroll depth, recordings reconstruct individual sessions, and feedback tools collect statements. Filters segment patterns, while masking and consent constrain capture.
Aggregated and individual interactions show how interfaces are actually used.
Surveys and interviews add motives and evaluation to observation.
Consent, masking, and exclusions bound sensitive capture.
Hotjar supports UX diagnosis and hypothesis generation. Recordings are samples rather than complete explanations; privacy, consent, data minimization, performance, and safe handling of sensitive input are central.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.