Configuring Data Flows

Editing data flows and regulating popular trackers

Editing Data Flows

In order to configure a data flow, click on the line in the table of the rule which refers to the domain, resource path, or regular expression (regex) you wish to classify. (e.g. cdn.example.com, for a domain path, //example.com/analytics for a resource path, or (^|.*\.)example-\d{1,4}\.com(\/|$) for a regex.)

This will bring up the “Edit Data Flow” dialog where you can adjust the domain, resource path, or regular expression which is being matched.

To classify the data flow according to the purpose for which you seek consent to collect it, select one or more of the available purposes under ‘Require consent for…’. Otherwise select ‘No Consent Needed’ if no user consent is needed for this data flow.

Available purposes are:

  • Advertising: online advertising trackers, e.g. Google Ads or Facebook Ads
  • Analytics: web site analytics providers, e.g. Google Analytics
  • Functional: all other data flows which are to be quarantined

‘No Consent Needed’ means that the Transcend Consent will always allow all requests to this domain, resource path, or which match this regex.

Rules can be grouped by which service they refer to, e.g. if [https://example.com](https://example.com) and ://tracker.example.com are both associated with the Example Analytics service, you can select Example Analytics under Service and they will be sorted together in the list view. This can be especially helpful for large sites with many data flows.

Sometimes you may want to classify a given data flow as “Junk”, e.g. requests made by third-party extensions or malware installed on the user's device. Mark them as “Junk” in the “Edit Data Flow” modal to tell Consent to safely ignore these.

Regulating popular trackers

Reference this library of data flow configurations that can help you deeply integrate with common trackers. These configurations allow tracker scripts to load while precisely regulating their subsequent data emissions.

Configuring your unknown request policy

Unknown requests are allowed through by default to ease the onboarding process. Once you feel that your data flows are fully configured, you can choose to block unknown requests by setting your unknown request policy under advanced settings to "block".