Eye Tracking – Definition & Guide

Eye tracking is a UX research technique that records where users look on a screen, how long they look there, and in what order – giving you data on visual attention that self-reporting and click data cannot provide.

Why It Matters

Users lie – not intentionally, but they consistently misreport where they looked and what they noticed. Ask someone if they saw the error message and they’ll say yes; eye tracking will tell you they looked directly past it. This gap between self-reported attention and actual gaze behavior is exactly what eye tracking in UX research is designed to close.

The implications for design are significant. Content you assume users see – warning labels, navigation items, helper text, promotional banners – may be completely invisible in practice. Eye tracking surfaces this systematically rather than leaving it to chance. Nielsen Norman Group’s F-pattern research, which showed that users scan text-heavy pages in an F-shaped pattern rather than reading them, only became possible because of eye tracking data.

For information-heavy interfaces – news sites, dashboards, product pages, e-commerce listings – understanding visual attention patterns directly informs layout, hierarchy, and what gets placed where. It’s the kind of insight that changes how you think about information architecture at a fundamental level.

How It Works

Modern eye trackers work by projecting near-infrared light onto the user’s eyes and using cameras to track the reflection on the cornea and pupil. Software calculates the precise gaze point on the screen in real time, typically at 60–120Hz (60–120 gaze samples per second).

The output is analyzed through two primary concepts:

Fixations: Moments when the eye is relatively still, focused on a specific point – this is when the brain is actually processing visual information. A fixation typically lasts 100–500 milliseconds.

Saccades: The rapid movements between fixations. Saccades are nearly blind – the visual cortex suppresses input during the jump. What matters for UX is where fixations land, not what happens in between.

Common gaze patterns observed in research:

F-pattern: Dominant on text-heavy pages. Users read the first line fully, scan the left edge, and occasionally glance right. Content below the first two lines gets sharply diminishing attention.
Z-pattern: Common on visually lighter layouts. Eyes travel across the top, diagonally to the lower left, then across the bottom – roughly following a Z shape.
Layer cake: On pages with clear headings, users skip from heading to heading, only dipping into body text that matches their interest.
Spotted: Users jump directly to salient elements (images, buttons, prices) without following a predictable path.

Lab vs. remote eye tracking: Lab setups use high-precision trackers (Tobii, SR Research) with controlled conditions. Remote unmoderated eye tracking (available through tools like Realeye or UserZoom) sacrifices some precision for scale and naturalness.

When It’s Worth the Cost

Eye tracking equipment and lab time are expensive – a proper session can cost $5,000–$20,000 including recruitment, equipment, and analysis. This makes it appropriate for:

Evaluating competing layout designs where click data is ambiguous
Understanding attention on complex pages (dashboards, product pages with many elements)
Researching whether key information (CTAs, warnings, pricing) is actually seen
Academic or deep-research contexts where the rigor justifies the cost

For most teams, a heatmap tool provides 80% of the value at a fraction of the cost. Eye tracking adds the fixation/saccade distinction and captures attention even when users look and move on without clicking – which heatmaps cannot detect.

Real-World Example

Nielsen Norman Group’s eye tracking research on e-commerce product pages found that users’ attention consistently clustered around product images (especially the first image), the price, and the primary CTA – while detailed descriptions, secondary images, and review summaries received substantially fewer fixations. This wasn’t about users deliberately ignoring content; they simply never looked there.

The design implication was clear: if a product page needs to communicate a key benefit, it needs to be in the visual hotspot – near the image, price, or CTA – not buried in a paragraph below the fold. This finding reshaped how product teams think about information hierarchy on listing pages and what content deserves prominent placement versus what can safely live further down.

How to Apply

Define specific hypotheses before running sessions. “Do users see the error message?” is a testable hypothesis. “What do users do on this page?” is too broad and leads to unfocused analysis.
Combine eye tracking with think-aloud protocol. Gaze data tells you where users looked; verbal commentary tells you what they understood. Together, they explain the behavior.
Use attention heatmaps as a communication tool. Eye tracking outputs are visually compelling and persuasive for stakeholders who resist UX findings presented as text alone.
Test with representative users. Gaze patterns differ between first-time and experienced users, and between age groups. Be explicit about which population you’re studying.
Cross-reference with usability testing findings. Eye tracking catches attention problems; usability testing catches interaction problems. Together, they cover more ground.

Common Mistakes

Treating click heatmaps as eye tracking. Click heatmaps and scroll maps (from tools like Hotjar) record cursor movement and clicks, not gaze. Cursor position correlates with gaze, but not reliably enough to treat as equivalent. The distinction matters when you’re making design decisions.

Ignoring the difference between fixation and comprehension. A fixation confirms the user’s eyes landed on something. It doesn’t confirm they understood it, remembered it, or acted on it. Someone can fixate on an error message and still not process the content.

Over-generalizing small samples. Eye tracking sessions are expensive, so sample sizes tend to be small (5–12 participants). The patterns are directional, not statistically conclusive. Treat findings as strong hypotheses to validate further, not as settled fact.

Heatmap – the accessible alternative that captures click and scroll data without specialist equipment
Usability Testing – the qualitative layer that explains why attention patterns form
Fitts’s Law – the principle connecting visual attention and target acquisition
Information Architecture – what eye tracking informs at the structural level
Cognitive Load – the mental cost of processing what users actually look at