> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/history.md).

# History

The **History** tab shows watched activity associated with your CrossWatch profile.

It provides two sources: **Synced history** and **Scrobbles**.

### Synced history

Synced history contains plays read from connected providers after synchronization.

Use this view to check the history currently stored by your providers.

The summary cards show:

* **Plays** — total synchronized history entries.
* **Everywhere** — entries present on every relevant provider.
* **Missing** — entries missing from one or more providers.
* **Providers** — providers contributing history data.

### Scrobbles

Scrobbles are plays captured live by CrossWatch through supported watchers and webhooks.

Use this view to inspect captured playback and its destinations.

The summary cards show:

* **Scrobbles**
* **Movies**
* **Episodes**
* **Hours Watched**

### Find and filter activity

Depending on the selected source, you can filter by:

* **Search**
* **Media type**
* **Provider**
* **Coverage** — **Any coverage**, **Missing somewhere**, or **On every provider**.

### Views

History supports:

* **Timeline** — grouped by date.
* **Grid**
* **List**

You can choose 24, 48, or 96 items per page.

### Remove history

With write permission, select individual items, visible items, or all matching results.

Remove matching history from selected providers.

Provider support can differ. CrossWatch reports each requested provider action.

{% tabs %}
{% tab title="End users" %}
Use **Synced history** to verify what your providers currently contain.

Use **Scrobbles** to inspect playback captured live by CrossWatch.
{% endtab %}

{% tab title="Power users" %}
History is available at `/profile#history`.

The page reads from `/api/profile/history`.

The available sources are `synced` and `scrobble`.

Local view preferences are stored under `cw.profile.history`.
{% endtab %}
{% endtabs %}

### Related pages

* Overview
* [Watchlist](/crosswatch/main-dashboard/navigation/profile/watchlist.md)
* Ratings
* [Playback](/crosswatch/main-dashboard/navigation/profile/playback.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.