Skip to main content

Schemas, validation and delivery

Discovery: learn the structure​

Before the first published schema, representative events help discover event names and fields. Review the observations and decide which fields belong in your schema. Discovery is a setup step, not normal warehouse delivery.

Published schemas: define the contract​

A published schema version defines the accepted event structure. Your sender must use its published version. Changes are prepared in a draft and published as a new version, so updating a draft does not silently change an existing contract.

Check shared Base Schema fields, event-specific fields, their types and required values. Field mappings identify properties such as the event name and timestamp.

Validation mode: check without collecting​

A new environment with a published schema starts in validation mode while its destination has never been ready. Validation mode active means valid events are checked but not stored or queued. They will not be delivered later.

This lets you check your sender before starting collection. A validation result is not proof that the event exists in your warehouse.

Collection: accept and deliver new events​

Successfully testing and saving a destination activates collection. New valid events can be queued and delivered according to the destination settings. Collection active describes the environment's mode, not proof of delivery for every individual event. Consent and bot settings may filter events.

Read the results for individual events, even when the request succeeds. An event being queued means it has been accepted for processing. Verify delivery in the warehouse before relying on it in reports.

When a destination stops working​

An environment that has entered collection does not silently return to validation mode. Collection needs attention means you should restore and test the destination. Check the reported error before retrying your sender.

If data is missing, check the selected environment, published schema version, individual event results, destination status and processing rules in that order.

See tracking diagnostics for event statuses, debug headers and retries.