Analytics
Analytics collects application events into Project-owned Datasets and turns them into reports. It provides separate interfaces for event ingestion, resource management, and querying.
Why use Analytics?
Applications need to record what happened and inspect activity over time. Analytics gives those events a dedicated storage and reporting boundary, so client code can send facts while authorized tools query the resulting data.
What you can do
- Create and manage Datasets for distinct reporting needs or environments.
- Ingest events in batches through a Dataset's write key.
- Inspect recorded events and query reports through the API or CLI.
- Rotate write keys and manage Dataset retention.
Core concepts
A Dataset groups events and defines their reporting and retention boundary. An Event is an immutable fact recorded in that Dataset.
A Dataset write key permits ingestion only. It cannot read events, run reports, or administer resources. Management and reporting require OAuth authorization. Use separate Datasets when collected data needs separate reporting or retention rules.
Use Analytics
Read the CLI reference for commands or the API reference for resources, request fields, and responses.