# The tracked data page

## Introduction

The `tracked data` page is used to view summary information for tracked data:&#x20;

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FQSLTAGA2Ek5yVtjsDZ15%2Ftracked%20data%20page%206a.png?alt=media&#x26;token=16fbc61a-c0d1-47cf-96a8-202ce965315d" alt=""><figcaption></figcaption></figure></div>

Here, you can [search for an entity value](#searching-for-tracked-data) to access available tracked data summaries, and then choose to view [summary details](#understanding-tracked-data-summaries).

## Need to know

* Tracked data includes data tracked by [track data]() and [de-dupe](../../advanced-shapes/de-dupe-shape) shapes.
* Data for the `tracked data` page is updated every `10 minutes` (i.e. every 10 minutes the database is checked for new tracked items and these are pushed to the dashboard UI).
* The `tracked data` page shows a maximum of `15` `entries` for any given tracked entity. So if you're tracking the same entity in more than 15 places, only the latest 15 entries are shown.
* Tracked data summaries remain available for `15 days`, starting from when an entity was last tracked. For example, if you're tracking customer IDs and ID `0100001` 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 on tracked data summaries are UTC.

{% hint style="info" %}
A tracked data extension can be purchased as a [subscription bolt-on](../../../../../../getting-started/core-subscription-tiers#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%2FHVUCgQbLRfJAMbvyNE70%2Faccess%20tracked%20data%201.png?alt=media&#x26;token=9685b9db-5be7-4827-be50-075c4487d2a6" alt="" width="563"><figcaption></figcaption></figure></div>

## Searching for tracked data

To find tracked data information for a particular field value, start by selecting the associated `entity type` - 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%2FZ2B8CwTTV9FCZO27DvsV%2Fentity%20types%20list.png?alt=media&#x26;token=ee66b328-bc36-4c16-9272-6b1978439b85" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
The entity type list includes all entity types that have been tracked.
{% endhint %}

Next, enter the `value` that you want to to review - for example, if you are tracking customer IDs, you'd enter the required customer ID here:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2F2w8p53tGbznBjXIdVq6I%2Ftracked%20data%20page%203.png?alt=media&#x26;token=94cd9a92-787e-4a75-b7d0-5211ff138b5c" alt="" width="375"><figcaption></figcaption></figure></div>

[Tracked data summaries](#understanding-tracked-data-summaries) are displayed for the most recent process flow runs where this entity was tracked - 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%2F40jKxPteZHTg7IZXqKtx%2Ftracked%20data%20page%204.png?alt=media&#x26;token=285666d3-b7b7-4738-a6a8-b17738d30d21" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
As you type a value, the search updates instantly so you may notice that the list of available summaries changes as you type.
{% endhint %}

From here, you can click any summary to view details:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FrXtsmrzu6H5Sn3Y5m8Gn%2Ftracked%20data%20page%207.png?alt=media&#x26;token=31721ae9-f709-4741-8c8d-c77964a8efe6" alt=""><figcaption></figcaption></figure></div>

## Understanding tracked data summaries

Each tracked data summary shows tracking information for the given entity in a flow run - 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%2FCdHjbwOmCup0yUvsX87U%2Ftracked%20data%20summary%201.png?alt=media&#x26;token=32fc52a2-877d-4379-b45c-3eb9f464e8f5" alt="" width="563"><figcaption></figcaption></figure></div>

You'll see one entry for each occasion that this entity was tracked in this run. In our example, we have two entries because the associated process flow includes two [track data shapes](), and this entity passed through both.&#x20;

### Summary information&#x20;

| Information    | Notes                                                                                                                                                                                                                                                                                                                                 |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Receive / send | The flow direction for the associated tracked data.                                                                                                                                                                                                                                                                                   |
| Date & time    | The date & time that this data was tracked.                                                                                                                                                                                                                                                                                           |
| Success / fail | <p>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>.</p> |
| Message        | If a [success criteria message](..#success-criteria-message) is  defined in the `track data` shape, it is shown here.                                                                                                                                                                                                                 |
