# Visitor Profiles

Each identified visitor has a dedicated profile page that brings together contact details, company information, browsing history, and engagement metrics in one place.

## What You'll See

### Contact Details

* Full name
* Work email address
* Job title
* LinkedIn profile URL
* Location (city, state, country)
* Profile image when available

### Company Information

* Company name
* Industry
* Employee count
* Company location
* Other firmographic data

### Pageview History Timeline

A chronological timeline of every page the visitor viewed across their sessions:

* Landing page and entry page
* Each page visited during the session
* Exit page
* Session timestamps
* Referrer information
* UTM parameters (source, medium, campaign, term, content)
* Device type
* Geographic location

This timeline helps you understand what content resonated and where the visitor is in their buying journey.

### Session Data

* Number of sessions
* Total page views
* First seen and last seen dates
* Visit recency

### ICP Match Status

Whether the visitor matches your configured Ideal Customer Profile, along with their fit score and which ICP rules they satisfied.

### Engagement Metrics

* Visit count
* Page view count
* Recency of last visit

## Using Visitor Profiles

Visitor profiles are designed for:

* **Sales outreach** — Use contact details and pageview history to craft personalized messages
* **Lead qualification** — Check ICP fit and engagement metrics before prioritizing
* **Intent signals** — See which pages they visited (e.g., pricing, features, case studies) to gauge interest
* **Account research** — Combine visitor and company data for account-based strategies

## Accessing Profiles

* From the Visitors list (sidebar), click any visitor row to open their profile
* Use [Search and Filtering](/platform/search-and-filtering.md) to find specific visitors, then open their profiles
* From a [Company Profile](/platform/companies.md), click any visitor to view their individual profile


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bullseye.so/platform/visitor-profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.