# Pageview History

Bullseye tracks the complete browsing journey for every identified visitor. This pageview history shows what pages they viewed, when, and how they arrived — giving you clear intent signals for sales and marketing.

## What Is Captured

For each session, Bullseye records:

| Data Point              | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| **Landing page**        | First page the visitor saw in the session              |
| **Entry page**          | Page where the session started                         |
| **Pages visited**       | Every page viewed during the session, in order         |
| **Exit page**           | Last page before leaving                               |
| **Session timestamps**  | Start and end time of the session                      |
| **Referrer**            | URL or source that brought the visitor to your site    |
| **UTM parameters**      | source, medium, campaign, term, content (when present) |
| **Device type**         | Desktop, mobile, or tablet                             |
| **Geographic location** | Country, region, city                                  |

## Where to View It

Pageview history appears on each [Visitor Profile](/platform/visitor-profiles.md) as a chronological timeline. You can see:

* Which pages the visitor viewed
* The order of page views
* When each view occurred
* Session boundaries (when one session ended and another began)

## How to Use It

* **Intent signals** — Visitors who hit pricing, features, or case studies often show stronger buying intent
* **Personalization** — Reference specific pages in outreach ("I noticed you were looking at our integration options")
* **Lead scoring** — Combine pageview depth and recency with [ICP fit](/platform/icp-filtering.md) for prioritization
* **Content insights** — Identify which pages attract and engage your best prospects

## Session Boundaries

A session typically represents a continuous period of activity. When a visitor is inactive for a defined period or closes the browser, a new session begins on their next visit. Session boundaries help you distinguish between single, deep dives and multiple return visits.


---

# 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/pageview-history.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.