---
url: https://trail.karanjot.co.in/docs/dashboard/activity.md
description: Find a person, a visit or an event, and follow a visitor page by page.
---

# Activity

Four tabs, each a paged table:

| Tab | One row per |
|---|---|
| **Visitors** | person seen in the range: location, first source, visits, first and last seen |
| **Sessions** | visit in the range |
| **Events** | event name. A row opens a sheet for that event |
| **Paths** | way people reached a goal, ranked |

## Journeys

Click a visitor to open their journey.

![A visitor journey: visits grouped by day, each a row of steps from the referrer through each page to a Signup event and the identify moment.](../../src/assets/journey.png)

Each visit is one row, grouped by day, read left to right:

* **Source**: the referrer or campaign that started the visit.
* **Pages**, in order, each with time on page and how far down the visitor scrolled.
* **Events**: custom events, named clicks, outbound links and form submits.
* **identified**: the moment `trail.identify()` linked this anonymous visitor to your user id.
* **left**: the end of the visit.

Use `[` and `]` to move between visits.

## How visits join up

* In **full mode** the tracker keeps a random id in a first-party cookie and localStorage, so visits from the same browser join one journey across days.
* Call `trail.identify(userId)` when someone signs in. Their earlier anonymous visits on that device join the same person, and visits from any other device where they sign in join too.
* Calling `identify` with a different user on the same device starts a fresh anonymous id first, so two people sharing a laptop are never merged.
* In **private mode** nothing is stored in the browser. The server groups a visitor's pageviews within one day, so a journey covers a single day at most.

See [Privacy modes](/tracking/privacy) for how to choose.

## Next

* Join visits to your users with [identify](/tracking/identify).
* Count conversions with [goals](/dashboard/conversions).
