Schema Explorer
Schema Explorer (DATA in the console’s menu) shows what your events actually carry: every event name your pipelines receive, the fields on each with their types, and which integrations handle each event. It also holds the fields you expect, imported from a schema you already have or added from what was seen. The Visual Builder offers all of these fields when you map rows and write rules.
Schema Explorer is a guide, not rules. It enforces nothing and never changes what is sent. To enforce a schema (required fields, types, rejecting events that do not match), use Data Governance.
What is recorded
Signal records the shape of the events each pipeline receives, after bot
filtering: each field’s path, as a blueprint reads it (for example
properties.items[].price or $traits.email), and its type (text, number,
true/false, object or list), with how often and when it was first and last
seen. No values are stored. A field that arrives as more than one type
keeps a record of each.
Recording reads a small sample of each pipeline’s events, so it adds no noticeable cost at any volume. New fields appear within about a minute; counts and last-seen times catch up within about ten minutes. Fields are never removed: one that stops arriving shows when it was last seen.
Events received
Pick a pipeline, or all pipelines. Each event shows when it was last seen and how the integrations live on the pipeline handle it:
| Shown as | Meaning |
|---|---|
| mapped | The integration’s blueprint has a section for this event. |
| sent as unmatched | No section for this event; the blueprint sends events it does not map. |
| dropped | No section for this event, and the blueprint drops events it does not map: this integration never receives it. |
Use it to check every event your site sends is handled where it should be.
Fields
For the selected event, each field shows its type, how often it was seen and when last. A ⚠ marks a field that arrives as more than one type (for example an order ID sent as text on some pages and a number on others): usually a mistake on the site, and a blueprint may need a transform for it.
Only your own fields (on by default) shows what your site or app sends in
properties and the identity profile, and hides the standard fields Datafly.js
adds. Hide removes a test or junk field from Schema Explorer and the
builder’s pickers; it is still recorded, and Show hidden brings it back.
Expected fields
Expected fields describe the events you expect your site to send, before or alongside what arrives:
- Import a JSON Schema file (one schema, or one per event under
$defs) or a spreadsheet saved as CSV with the columnsevent, field, type, description(a blank event means every event). Import only adds; fields you already expect are left as they are, and you see what will be added first. - Expect adds a seen field; Expect all fields shown adds every field on the event. With no written schema, send some test events and expect what arrived.
- Export downloads the expected fields as JSON Schema or CSV.
Schema Explorer then shows expected fields an event has not carried, and expected events no pipeline has sent. Expected fields are offered in the builder before any traffic arrives.