Introduction

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.

Need to know

• 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.

Accessing the tracked data page

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

Searching for tracked data

To find tracked data information for a particular field value, start by selecting the associated entity type - for example:

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:

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

Understanding tracked data summaries

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.

Summary information

Introduction

The track data shape is used to track processed data, based on field paths that you define. When data passes through a track data shape, the values associated with your defined field paths are tracked - which means they can be reviewed from the tracked data page.

For example, you might want to track all customer_id values that pass through a flow, so at any time you can quickly check if/when/how a given customer record has been processed.

Need to know

• By default, tracked data is available for viewing for 15 days after it was last tracked.

• Depending on data volumes, allow 10 minutes for tracked data to be visible in data pools.

• The track data shape works with incoming payloads from a connection shape, a manual payload, an API request, or a webhook.

• Payload, flow, and metadata variables are supported when defining success messages.

• JSON payloads are supported.

Adding & configuring a track data shape

You can add as many track data shapes to a process flow as required. For example, you might place one immediately after a receiving connector to track everything received before anything else happens to the data, and another after the final sending connector to track everything sent into your destination system.

To add and configure a new track data shape, follow the steps below.

Step 1 In your process flow, add the track data shape in the usual way:

Step 2 Configure settings as required - the table below summarises available fields:

Step 3 Save your settings., then access them again:

...you'll now see success criteria options at the bottom of the shape settings drawer:

Step 4 The success criteria options are optional. If you don't need to apply these then your setup is complete - close the settings drawer and continue with your process flow as required. If you do want to use these options, see below for guidance.

Success criteria options

When data passes through a track data shape, specified data fields are tracked and by default, tracked data is marked as a success.

However, there may be times where you want to control the conditions under which the status of tracked data is deemed a success or a failure, and to record this outcome for future reference. The success criteria section allows you to:

• Define filter conditions that must be met for an entity's progress to be reported as a success or failure in summary information for this tracked item.

• Add a message to be displayed in summary information for this tracked item.

Success criteria filters

Any conditions that you want to apply can be added via filters. To define a new filter, click the add filter button:

These filters work in the same way as other filters in the dashboard - select/define a field, then set conditions and values.

You can add as many filters as you need - multiple filters work together with an 'AND' operator. Remember that you're defining conditions that must be met for a success outcome - if multiple filters are present they must ALL be matched. If one or more filters are not matched, the associated tracked data is marked as a failure.

The success or failure outcome from these filters is reported in the logs, and also in tracked data summaries - for example:

Success criteria message

You can define a message to be displayed in the tracked data summary for associated tracked data:

This message can be text-only, or any combination of text, payload variables, flow variables, and metadata variables. For example:

In tracked data summaries, this example is shown as:

Messages are added to tracked data summaries when:

• No success criteria filters are defined

• Success criteria filters are defined and the outcome is success

• Success criteria filters are defined and the outcome is failure

Related pages

• The tracked data page

• Field tagging & tracked fields