Analytics and Tracking

Explorations

Also called GA4 Explore

The GA4 workspace for building custom analyses, including funnels, paths, cohorts and segment overlaps.

Quick facts: Explorations

Category
Analytics and Tracking
Also called
GA4 Explore
Level
Intermediate
Affects
Custom analysis, funnel insight, reporting depth
Where to see it
GA4 (Explore)
In this article4
  1. How explorations work
  2. Why explorations matter
  3. Common mistakes with explorations
  4. How to act on it

How explorations work

GA4’s standard reports answer a fixed set of questions in a fixed shape. Explorations are the area where you build the question yourself: you choose the dimensions and metrics you want, drag them into rows, columns and values, and apply segments and filters until the table answers what you actually asked.

Several ready-made techniques sit alongside the blank free-form table. A funnel exploration lays out defined steps and shows where people drop out. A path exploration follows the sequence of pages or events people move through without you specifying it in advance. A segment overlap shows how far different groups of users are the same people, and a cohort exploration follows a group forward through time.

Explorations are personal by default. One you build is visible only to you until you share it with other users of the property, and the underlying data is still governed by the property’s settings — its retention period, its identity rule and its privacy thresholds all apply here exactly as they do in standard reports.

Why explorations matter

Most real business questions do not fit a standard report. Which enquiry sources actually produce the enquiries that turn into work. Where the checkout loses people. Whether the visitors who read the pricing page behave differently from those who do not. Each of those needs a table nobody built for you.

They also make an analysis reproducible. Once an exploration is saved and shared, the same question can be re-asked next month without anyone rebuilding it from memory, which is the difference between reporting and remembering.

Common mistakes with explorations

The first is expecting the totals to match standard reports. Explorations can sample on large data sets, they apply their own scope rules to dimensions and metrics, and a mismatched combination can produce rows that look wrong because the question was malformed rather than the data. Watch for the sampling and cardinality notices at the top of the table.

The second is building an exploration and never labelling it, so a colleague inherits a table of numbers with no statement of what it counts. The third is reaching for an exploration when the standard report already answered the question, which is slower and less consistent.

How to act on it

Start with the sentence you want to end with, then build the smallest table that supports it. Add one dimension at a time and check the row count and the notices as you go, so you notice the moment a combination stops making sense.

Name every saved exploration after the question it answers rather than the technique it uses, and share it with everyone who reads the numbers. When an exploration proves genuinely useful month after month, that is the point to lift it into a proper reporting dashboard so it is delivered rather than rediscovered. And keep the raw exploring in explorations, where a wrong turn costs nothing.

Do and do not

Do

  • Write the question first, then build the smallest table
  • Name saved explorations after the question, not the technique
  • Share explorations the team depends on

Do not

  • Assume totals will match the standard reports
  • Ignore the sampling and cardinality notices
  • Rebuild an exploration that a standard report already answers

Questions people ask about this

Why do my exploration numbers differ from the standard reports?

Usually because of scope, sampling or a mismatched pairing. Explorations let you combine dimensions and metrics that belong to different scopes, such as a user dimension against a session metric, which produces a technically valid but confusing table. Large data sets may also be sampled. Check the notices at the top of the exploration before assuming the data is wrong.

Can other people in my account see the explorations I build?

Not unless you share them. An exploration you create is visible only to you within that property, which means a colleague opening the same account will not find your work. Use the share option for anything the team relies on, and give it a name that says what question it answers.

How far back can an exploration look?

Only as far as the property's data retention setting allows for the detailed data explorations are built from. If retention was left at the shorter option, older date ranges return nothing even though the standard reports still show aggregated history. Check and extend the retention setting early, because it does not apply retrospectively to data already discarded.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.