# Segments

A segment is a named view of one site, defined by a path prefix. Give one site a blog, a docs tree, and a marketing homepage and the totals stop meaning much; a segment lets you look at `/docs` on its own, including everything beneath it, without splitting the site in two or touching your embed.

Prefix matching is what makes this useful: a segment on `/docs` covers `/docs/api` and `/docs/getting-started`, but not `/docs-old`, which is a different path rather than a deeper one.

![Segments in Settings](docs/segments.png)

Create them under **Settings → Segments**. Once a site has segments, a switcher appears under its name on Overview to move between **All** and each segment. Four segments or fewer show as pills on a wide screen; past that, and on a narrow one, you get a dropdown instead.

Segments work within one site. If what you want to compare is several different hosts, that is a [group](/docs/account/groups), not a segment.

## Adding a segment

Press **Add segment**, name it, and pick one of two kinds.

**Paths** takes one prefix per line. When prefixes overlap, the order of the list decides which segment claims a hit, and the earlier one wins — so drag them into the priority you want rather than trying to write mutually exclusive prefixes.

**Everything else** collects the traffic no other segment claimed. You get one remainder per site, and you can list extra paths to keep out of it if there is traffic you would rather leave uncategorised.

You can have up to ten segments per site. Removing one only removes the view; the hits stay exactly where they were.

## What a segment is not

It is not the dashboard path filter. That filter is an exact match, so clicking `/docs` there shows you that one page and nothing below it. Segments exist precisely because that is often not the question you were asking.

It is also not an ignore rule. Ignore rules hide traffic; segments name traffic you want to keep looking at.