Environment → mode mapping
A regex against page_location picks the environment for every incoming event. The matched environment's mode determines what Conform does when an event fails validation.
learning
Just watch. Validation is skipped entirely; every event is forwarded. Stats are still accumulated so Conform can infer a schema for events that don't have one yet. Best for new events you haven't decided rules for.
warning
Validate, but never block. Failures are logged to the bad-events archive, surfaced in DevTools and the floating panel, and reported via metrics — but the event is still forwarded to your downstream collector. Best for development, staging, and the first few weeks of a schema's life in production.
strict
Validate and drop on failure. Invalid events are rejected at the edge — never reach your warehouse, never train your models, never skew your dashboards. Best for established schemas where you've watched the <0.1% rejection rate hold for a week or two.
Environment
URL match (regex on page_location)
//
Mode
Environment
URL match (regex on page_location)
//
Mode
Environment
URL match (regex on page_location)
//
Mode
Fallback (no environment matched)
Reviewing
page_view
Fields (11)
For each field, review what was inferred from the live traffic and refine. Constraint = how strict you want validation: enum (only listed values), open (any value of the right type), pattern (regex), or exclude (drop from schema).
Field
Presence
Inferred
Type
Required
Constraint
Allowed values
Snapshot:
page_view data from radio-controlled.co.uk, captured 2026-05-05. Inference window: 24 hours, 24 hourly buckets merged.