Explore
Explore in the Analyze area (Behavior) — route /analyze/explore.
Explore lives in the Analyze area of the dashboard, under Behavior.
At a glance#
| Dashboard route | /analyze/explore |
| Area | Analyze (analyze) |
| Group | Behavior |
| Platforms | Available for every app platform. |
What it does#
Explore is the self-serve breakdown: pick one event, pick one of its properties, and get the count split by that property's values over a time range. Results open into a drill panel so you can go from a bar to the underlying data.
One event, one property. That constraint is deliberate — it is the question you ask ninety percent of the time, and it needs no query language.
When to use it#
For the question that arrives mid-conversation. "How many purchases, by plan?" "How many signups, by referral source?" Explore answers those in about fifteen seconds, which is the difference between checking and guessing.
When you need more than one split, or want to keep the result, build it as a dashboard tile instead.
Workflow#
Confirm the property exists before you look for it
The property list comes from what has actually arrived. If the one you want is missing, that is an instrumentation finding, not a query problem.
Watch for an unexpectedly large "other" or blank bucket
Events missing the property land there. A large blank bucket usually means the property is only set on some code paths.
Drill into a surprising value
The drill panel is what turns "that number is odd" into "here is why".
Permissions and prerequisites#
Requires event ingestion with properties attached — see Events.
Limits and edge cases#
One property at a time. No multi-dimensional breakdown here.
High-cardinality properties produce unreadable results. Splitting by something near-unique gives you one row per event. Session ids and timestamps are not breakdowns.
Property values are compared as they arrived.
"Pro"and"pro"are two values, and no normalisation happens on read.
Troubleshooting#
Counts lower than expected. Check the time range first, then whether the property is present on every instance of the event — an event missing the property is excluded from the split.
A property I send is not offered. It has not been seen on that event. Confirm which event carries it.
Where the data comes from#
From the SDK
Served by
Analytics