Data

The Data tab is the request-level view of the dashboard. Where the Overview tab aggregates traffic into cards, the Data tab is the raw history: a paginated, filterable, sortable, column-configurable, exportable table of individual request records. This is the surface for “show me every identification call, search for one identifier, and export the rows.” Every value in the table is computed server-side and read-only. The dashboard renders results; it never blocks, challenges, or decides anything. Your own code owns the allow / challenge / review / block decision using the Risk Score and signals you receive over webhooks and the Management API.

​

Toolbar

The toolbar above the table holds the controls that shape it.

​

Filters

The Filters popover scopes the table. Apply one or several together, then clear them all with Reset filters.

​

Search

Records are searchable by identifier or field. Search is parameterized server-side as a search_type plus a search_value, so you look up records by a specific identifier rather than full-text scanning the table. The identifier types you can search by line up with the History API: See identifiers for how each id is derived and how durable it is.

​

Columns

Columns are grouped into five categories in the Columns toggle. The default visible set is Request ID, UserHID, Visitor ID, Device ID, Score, Date, IP Address, Country, VPN, Proxy, and Tor. Turn the rest on as you need them.

​

Request Data

The identity, timing, score, and environment of the request. The Request ID, Session ID, UserHID, Cookie ID, Visitor ID, and Device ID cells are copyable so you can paste an identifier straight into search or the History API.

​

Request Signals

Each scoring signal as a boolean column. A red Yes badge means the signal fired on that request; a muted No means it did not. These are the same per-request signals that build the Risk Score and ship in the explainable Details array. For what each signal weighs, how anonymity signals (Tor, Privacy Relay, VPN) are mutually exclusive, and the VPN 2-of-3 corroboration rule, see signals.

​

Connection Type

​

Traffic Source

​

UTM

The campaign tags captured on the request. The Channel, Referrer Domain, and UTM columns are the same attribution fields the Traffic Sources card aggregates. Use the Data tab when you need the per-request rows behind a channel’s risk badge.

​

Score column

The Score cell is a colored badge, banded the same way as everywhere else in ShieldLabs: The score is always 0–100, capped at 100. There is no higher scale. A legitimate user can land in a higher band (corporate proxy, VPN, privacy browser), so read the Score together with the signal columns that fired, not the number alone. See acting on the Risk Score.

​

Sorting

The table is sortable by Date, Score, and every boolean signal column. Sorting by a signal groups the rows where that signal fired, which is a fast way to pull, say, every request that tripped Anti-detect Browser in the period.

​

Pattern-ID highlighting

Turning on Pattern IDs in the toolbar highlights identifier cells that belong to a flagged entity, so you can spot at a glance which records are part of an abuse pattern. Only the UserHID, Visitor ID, and Device ID cells highlight:

• a Dangerous match shows a red background
• a Suspicious match shows an orange background

This pairs with the Pattern filter: filter to one pattern, turn on highlighting, and the matched identifiers stand out across the result set. The patterns themselves, their grading, and per-identifier breakdowns live on the Patterns tab. Reaching the Data tab pre-filtered to a single pattern is exactly what the View in Data button on each pattern card does.

​

Export

The Export button exports the current result set in either format: Exports are free: they do not consume request balance the way the History API does (which bills per returned row). Filter and search to the rows you want, then export them.

​

How the Data tab fits the flow

The Data tab is the readable mirror of the data your own backend already receives: Use the Management API when your code needs the records programmatically, and the Data tab when a human needs to investigate.

​

Where to go next