# The tracked data page

The `tracked data` page is used to view summary information for tracked data items. For example: 

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2Fd6nLvFebdt2N7c6duypA%2Ftracked%20data%20page%20b.png?alt=media&#x26;token=6460c955-1569-4b6e-93e6-16a7147132b9" alt=""><figcaption></figcaption></figure></div>

Here, you can [search for a tracked value](#searching-for-tracked-data) to view [details](#working-with-tracked-data)

## Need to know

* Tracked data includes data tracked by the [track data](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/track-data-shape) shape.
* Data for the `tracked data` page is updated as soon as data passes through the track data shape.
* There is no limit to the number of times that the same entity can be tracked. For example, if you are tracking an `order_id` field and the same `order_id` is processed 50 times within your retention period, there will be 50 entries in the tracked data table.&#x20;
* Tracked data items are retained for `15 days`, starting from when an entity was last tracked. For example, if you're tracking an `order_id` field and ID `10134` was tracked 14 days ago, but then again today, it will be visible for another 15 days (and so on until it's not seen for 15 days).
* Times shown are UTC.

{% hint style="info" %}
A tracked data extension can be purchased as a [subscription bolt-on](https://doc.wearepatchworks.com/product-documentation/getting-started/subscription-tier-limits#core-subscription-tier-bolt-ons) to increase the number of days tracked data remains available.&#x20;
{% endhint %}

## Accessing the tracked data page

To access the `tracked dat` page, select `process flows` ➤ `tracked data` from the left-hand navigation menu:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2Fkyn6UvlLBPfImiK69pUU%2Faccessing%20tracked%20data.png?alt=media&#x26;token=1e9c788d-9956-491b-8d2c-0a9dfbf140cd" alt=""><figcaption></figcaption></figure></div>

## Working with tracked data

Tracked data information is displayed in a searchable table, with information and options summarised below:

<table><thead><tr><th width="247.62109375">Field</th><th>Summary</th></tr></thead><tbody><tr><td>Flow</td><td>The name of the process flow from which the item was tracked. </td></tr><tr><td>Flow run id</td><td>The unique identifier associated with the flow run during which the item was tracked (displayed as a hyperlink for direct access to <a href="../../../../error-reporting-and-exception-handling/run-logs-and-queue">run logs</a>).</td></tr><tr><td>Entity type</td><td>The entity type associated with the tracked item (order, customer, invoice, etc.). This is set in the <a href="">track data shape</a>. Use the associated filter option to filter the list by a given entity type.</td></tr><tr><td>Value</td><td>The tracked value. Use the associated sort option to sort tracked items in this sequence (toggle for ascending or descending). To find a specific value, use the <a href="#searching-for-tracked-data">search</a> option.</td></tr><tr><td>Direction</td><td><p>The flow direction (<code>send</code> or <code>receive</code>) associated with the tracked field:<br></p><ul><li>If the tracked data is being pulled from a source, set this option to <code>receive</code></li><li>If the tracked data is being pushed to a destination, set this option to <code>send</code></li></ul><p>Use the associated filter option to filter the list by either direction. Use the associated sort option to sort tracked items in this sequence (toggle for ascending or descending).</p></td></tr><tr><td>Success / fail</td><td>If <a href="..#success-criteria-filters">success criteria filters</a> are defined in the <code>track data</code> shape, the success/failure marker is determined by the outcome of these.<br><br>If success criteria filters are NOT defined in the <code>track data</code> shape, the default marker is <code>success</code>.<br><br>Use the associated filter option to filter the list by success or failure outcomes. Use the associated sort option to sort tracked items in this sequence (toggle for ascending or descending).</td></tr><tr><td>Message</td><td>If a <a href="..#success-criteria-message">success criteria message</a> is displayed, an 'eye' icon is shown; click this to view the message.is defined in the <code>track data</code> shape, it's shown here. For example:<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FnhF788V8lKdCyqGMtSuI%2Ftracked%20data%20page%20show%20message.png?alt=media&#x26;token=7dceb0dd-2457-4f5e-a435-9c524f56ad6b" alt=""><br></td></tr><tr><td>Tracked at</td><td>The date &#x26; time that this data was tracked. Use the associated sort option to sort tracked items in this sequence (toggle for ascending or descending).</td></tr></tbody></table>

## Searching for tracked data

To find a specific tracked value, type the required value (or any part of it) into the search field. For example:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FyRjp56ewaOwlImAoyuDx%2Ftracked%20data%20page%20search.png?alt=media&#x26;token=a1e4175e-f303-4f46-af6c-1ae9371d407e" alt=""><figcaption></figcaption></figure></div>


---

# 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://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/track-data-shape/the-tracked-data-page.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.