Analytics
Analytics collects application events into Account-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 grant principals access to a Dataset.
Core concepts
A Dataset groups events and defines their reporting and access boundary. An Event is an immutable fact recorded in that Dataset. Events remain stored until you delete the Dataset. Legacy retention fields do not expire events.
A Dataset write key permits ingestion only. It cannot read events, run reports, or administer resources. Management and reporting require OAuth authorization and Dataset access. Account owners administer their Account's Datasets. Use separate Datasets when collected data needs separate reporting or access rules.
Use Analytics
Read the CLI reference for commands or the API reference for resources, request fields, and responses.