How Platform works

From your application to your warehouse

Platform receives events from your website or application, checks them against your published event schema and delivers eligible events to your configured warehouse. Explorer can then read those stored events to build reports.

Website or application → Platform → your warehouse → Explorer

The warehouse is your permanent event store. Platform uses temporary processing and delivery storage rather than keeping a separate permanent copy of your event payloads. You control the warehouse and how stored data is retained and used.

Projects and environments

A project groups the tracking for one website or application. Its event schema describes a shared contract for incoming events. An environment separates a particular setup, such as testing or production, with its own keys and destination. Select the right environment before sending events or changing a connection.

Ingestion keys and tracking

An ingestion key authorizes a sender for an environment. Use Tracking setup for the integration instructions that match your selected environment. Use the appropriate key type for your sender and keep server credentials out of browser code.

Event schemas

An Event Schema describes event names, fields, types and required values. Shared fields belong to the Base Schema. Event-specific fields belong to the corresponding event schema. Publishing creates a version for your sender to use. A draft has no effect on regular event processing until published.

Destinations and Explorer

A destination is the warehouse connection used to store accepted events. ClickHouse is supported. BigQuery is available where enabled for your installation. Choose from the destinations offered in your account. Delivery and Explorer reading use separate permissions.

You can use Platform to collect data in your warehouse, Explorer to analyze existing sources, or both together. Set up your first project.