Queries
Query and filter your event data with advanced search, without writing SQL.
The query builder answers one-off questions about your raw events. Dashboards and reports are for numbers you watch repeatedly; Queries is for the question you have once, right now, usually while debugging or investigating something specific.
Go to Analytics → Queries.
Build a Query
The Query Builder takes a few inputs, all optional. Leave one blank and it does not constrain the results.
Event narrows to a single event name. Start here when you know which event you are investigating.
User ID narrows to one person, which is the fastest way to answer "what did this user actually do".
Metadata Path targets a property inside the event payload. Use dotted notation to reach a nested
value, so a payload of {"plan": {"tier": "pro"}} is reached at plan.tier.
Fields chooses which columns appear in the results table. Add the properties you care about so the answer is readable rather than a wall of JSON.
Filtering
Conditions combine the same way they do in the API. Filters inside a group are joined with AND, and groups are joined with OR, which lets you express "this and that, or this other thing" without nesting anything by hand.
The available operators are equal, not equal, greater than, greater than or equal, less than, less than or equal, is null, and is not null. The two null operators take no value, so the value input disappears when you select one.
For the full reference including request shape, see Query Filters.
Results
Results come back as a table with the columns you chose under Fields. Because the query runs against raw events rather than a rollup, you are seeing exactly what was stored, which is what makes this the right tool for checking whether an event arrived and what it carried.
If a property you expect is missing from the Metadata Path suggestions, it is usually because no event has carried it yet. Send a test event from Project Settings → Playground and check again.
Doing This Programmatically
Everything here is available over the API. See Search Events for the endpoint and Query Filters for the filter shape.