The tracked data page
Last updated
Last updated
The tracked data page is used to view summary information for tracked data:
Here, you can search for an entity value to access available tracked data summaries, and then choose to view summary details.
Tracked data includes data tracked by track data and de-dupe 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.
A tracked data extension can be purchased as a subscription bolt-on, to increase the number of days tracked data remains available.
To access the tracked dat page, select process flows | tracked data from the left-hand navigation menu:
To find tracked data information for a particular field value, start by selecting the associated entity type - for example:
The entity type list includes all entity types that have been tracked.
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:
Tracked data summaries are displayed for the most recent process flow runs where this entity was tracked - for example:
As you type a value, the search updates instantly so you may notice that the list of available summaries changes as you type.
From here, you can click any summary to view details:
Each tracked data summary shows tracking information for the given entity in a flow run - for example:
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.
Receive / send
The flow direction for the associated tracked data.
Date & time
The date & time that this data was tracked.
Success / fail
If success criteria filters are defined in the track data shape, the success/failure marker is determined by the outcome of these.
If success criteria filters are NOT defined in the track data shape, the default marker is success.
Message
If a success criteria message is defined in the track data shape, it is shown here.
