> 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/cw-tracker.md).

# CW Tracker

Browse your local tracker, log watches, keep notes, fix records, and import from connected services.

**Tracker** is your local media journal in CrossWatch. Use it to browse watches, ratings, watchlists, playback progress and collections, or keep personal notes about movies and shows.

It stores data for the selected CW Tracker instance. [Profile](/crosswatch/main-dashboard/navigation/profile.md) brings together activity from your connected accounts; Tracker focuses on your local records.

{% hint style="info" %}
Tracker changes are saved locally. Configured sync pairs can send additions, edits or removals to other providers on the next run. Read the affected-provider message before confirming a change. Personal notes and custom fields stay in CrossWatch.
{% endhint %}

{% tabs %}
{% tab title="End users" %}

### Get started

1. Open **Settings → Connections → Trackers → CrossWatch** and select **Connect local tracker**.
2. Open **Tracker** in the main navigation, between **Playlists** and **Editor**.
3. If you have several instances, choose one under **Title and tracker → Tracker**.
4. Use **Log a watch**, **Import**, or a synchronization pair to add data.

Configure [TMDb Metadata](/crosswatch/settings/connections/metadata/tmdb-metadata.md) for title search, artwork, episode information and cleanup checks. Connecting **TMDb (Sync)** alone does not configure metadata.

### Find your data

On smaller screens, use the **View** selector to switch between Tracker tabs.

| Tab            | What it shows                                                                                                                                  |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **History**    | Recorded watches. Use **By day** to group plays and browse the month timeline.                                                                 |
| **Shows**      | Shows represented in your history, with episode progress where TMDb information is available. **Hide dropped** hides shows you marked Dropped. |
| **My titles**  | Movies and shows with personal status, dates, tags, notes or custom fields. Filter by status, tag or title.                                    |
| **Watchlist**  | Movies and shows saved for later.                                                                                                              |
| **Ratings**    | Your local ratings.                                                                                                                            |
| **Progress**   | Saved playback positions.                                                                                                                      |
| **Collection** | Your local collection entries.                                                                                                                 |
| **Clean up**   | Records that need matching or metadata review.                                                                                                 |

Switch between **List** and **Grid** using the layout buttons. The layout is remembered separately for each tab. Search by title and use the available filters, sorting and page-size controls. Select a row to open its title panel. On smaller screens, expand **Title and tracker** to see the panel and instance selector.

The top statistics show recent plays, estimated hours and your day streak. Hours use known runtimes, so they can be incomplete until metadata has been checked. Show progress uses TMDb episode numbering; specials are excluded from the overall progress total. A next-episode suggestion follows your latest watched episode and may leave earlier gaps for you to review. The title panel can show upcoming or next-episode previews with artwork, air dates and summaries when TMDb information is available.

### Log watches and manage titles

1. Select **Log a watch**.
2. Search TMDb and choose the correct movie or show.
3. Choose the watched date. For a show, select a season and an episode, or all episodes in that season.
4. Confirm the watch.

You can also log an unwatched episode from the title panel, rate a title, or add it to your watchlist. Ratings support **0.5 to 10** in half-point steps. Hover over or focus a star to preview its numeric value; selecting it saves the rating. Recording a new watch does not automatically enable synchronization with another account.

Use **More add options** beside **Log a watch** to open [Quick Add](/crosswatch/main-dashboard/navigation/quick-add.md) for one-off actions to selected connected accounts. Log a watch saves to your selected local Tracker; Quick Add uses the destinations you choose.

### Keep personal notes

Open a title and use **My notes**. Choose **Watching**, **Plan to watch**, **Completed**, **On hold**, **Dropped**, or **No status**. Add **Started** and **Finished** dates, tags and notes, then select **Save**.

* Notes belong to the movie or show, rather than one individual watch.
* **My titles** collects titles with saved personal information. Setting Completed does not create watched episodes.
* Use **Add your own fields** or **Manage your fields** for Text, Number, Date, Yes / no, or Pick from a list fields. Fields are shared across titles within that Tracker instance.
* Changing a field type or removing a field clears its saved values. Review this before selecting **Save fields**.
* Use **Clear** to remove the personal information for a title. This does not delete its watched history.

Notes belong to the selected Tracker instance. Anyone with access to that instance can see them; use separate instances for separate journals.

You can save notes while a sync runs. Notes, tags and custom fields are not sent to other providers through normal synchronization. Personal status labels can be shared through optional [Status mapping](/crosswatch/settings/configure-pairs/provider-settings/status-mapping.md); notes, tags, dates and custom fields remain local. The dropped-show import described below can also set a local Dropped status.

### Edit, match or delete records

Use the record actions to edit dates, ratings, playback percentage, title information or IDs. For a wrong match, use **Fix match** to select the correct title. Where offered, choose **Only this record** / **Only this episode** or **Every record of this title**.

Editing a whole title updates its related local records together. Dates, ratings and episode numbers remain unchanged when changing the title match; check episode numbering separately.

Select records and choose **Delete** for a bulk removal. The confirmation explains whether a later sync can remove them elsewhere or add them back from another provider. No remote deletion occurs simply from pressing Delete in Tracker.

Open **Changes** to review what you logged, edited or deleted, filter the list, and use **Undo**. Undo is refused if the affected data has since changed or would overwrite another record. Refresh and review the current data instead. Undo changes local data; it does not immediately reverse a change already sent to another provider.

### Check and clean up matches

1. Configure your TMDb metadata key.
2. Open **Clean up** and select **Check all**.
3. Follow the background job in Tracker or the notification bell.
4. Review **Need attention**, **Not checked**, or **Match TMDB** results.
5. Correct a wrong match, use the offered TMDb title/year correction, or edit the record as needed.

Checks can use supported IMDb or TVDB IDs to look for a unique TMDb match when a TMDb ID is missing. They can flag missing IDs, unknown titles, title/year differences and episodes absent from TMDb. They do not automatically rewrite your records. A matching result is a comparison with TMDb, not a guarantee that an alternative episode order is correct.

**Stop** keeps results already collected. A restart can interrupt the check; run it again when ready. Authentication or connection problems can stop checks without proving that your records are wrong.

### Import from a connected service

1. Select **Import** in Tracker.
2. Choose the source account under **From**.
3. Select the supported features under **What to bring in**.
4. Choose the destination under **Into**. Administrators can choose **New instance** and enter a **Name**.
5. Select **Start import**.

This is a one-time, one-way import. It adds supported data without deleting destination records, writing back to the source, or saving an ongoing sync pair. Existing records may be updated according to the selected feature. Large histories can take time while IDs are matched.

When the source supports it, History imports offer **Also bring in shows you dropped**. This is off initially. Imported dropped shows appear under **My titles** with Dropped status; review any existing personal status afterwards.

You can leave the page and follow progress in the bell. **Stop** requests cancellation after the current batch; data already imported remains. Review the result for skipped, unresolved or failed items. Only one service import runs at a time, and it cannot start during another sync. You cannot import an instance into itself.

For an export file, use **Import a file** to open [Import / Export](/crosswatch/main-dashboard/tools/import-export.md). File imports offer a preview before writing media records.
{% endtab %}

{% tab title="Power users" %}

### Access and limits

Managed users see Tracker only when they have write access and an assigned CrossWatch instance. They can access their assigned instances and source accounts; only administrators can create new instances. Read-only and monitor-only accounts do not have Tracker access.

Record changes cannot be saved while a sync runs; retry after it finishes. Use separate Tracker instances for independent local libraries. If editing is unavailable, ask your administrator to check the instance configuration.

Personal notes allow up to 10,000 characters and 30 tags per title. Custom fields are limited to 20 per instance. The local change log is retained for up to 90 days, subject to a 50,000-entry limit; it is not a permanent backup.

### Back up and restore

Use **Settings → Maintenance → CW Tracker → CW tracker archive → Download archive** for the selected instance. The portable archive includes tracker records, restore points, personal notes and custom-field definitions. It does not include the local Changes log.

**Import archive** accepts the supported tracker ZIP/JSON formats and can replace matching saved data. Select the correct instance and keep a backup first. This archive operation is different from importing a connected service.

See [Maintenance](/crosswatch/settings/maintenance.md#cw-tracker-archive), [Backup & Restore](/crosswatch/settings/maintenance/backup-and-restore.md), and [CrossWatch synchronization](/crosswatch/settings/synchronization/trackers/crosswatch.md) for restore and sync behavior.
{% endtab %}
{% endtabs %}


---

# 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/cw-tracker.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.
