Each event has a table
Use consistent event names and fields. Query the table to debug a failure or measure usage. You can inspect the individual rows behind a result.
Read the SQL behind the chart
You can read and edit every query. Public recipes include the event schema, sample results, known edge cases, and advice on turning the query into a dashboard or alert.
Choose what you send
Our guides recommend categories and identifiers. They tell you to exclude prompts, credentials, request bodies, and private customer content unless your team explicitly approves sending them.
Editorial and technical review
What we check before publishing
We check the docs against our public API and application code. SQL recipes only read data. We also have an optional audit that checks whether DataFusion can plan each query.
We label sample rows and charts as synthetic. They show how a query works and do not measure customer results. Comparison pages link to the other product's documentation and show when we reviewed the claims.
We update a page's review date when we change its claims or guidance. Unchanged content keeps its date.
Read the complete editorial standards and technical review policy to see who reviews the content, which sources we use, and how to request corrections.
Try a query on your own events
Pick a SQL recipe, check which event fields it needs, and adapt the query to your application.