Text version of this lessonExpand
Many teams do not fail at GA4 because they cannot click the interface. They fail because they put the question in the wrong data layer. Standard reports inspect, Explorations investigate, fixed reports review, and BigQuery plus order systems reconcile raw events. The output of this lesson is a GA4 analysis layer selector: choose the layer before you go deep.
Lesson output: a GA4 analysis layer selector
Do not start by opening the most complex Exploration. First decide what type of question you are asking:
- Did something change: use standard reports for trends, channels, pages, devices, events, and revenue.
- Why did it change: use Explorations for Free Form, Funnel, Path, Segment Overlap, segments, and filters.
- Can the team review it repeatedly: use fixed reporting for weekly reports, monthly reports, and management readouts.
- Can it reconcile: use BigQuery, Shopify, ERP, or finance sheets for raw events, orders, refunds, cost, and profit.
If the layer is wrong, the analysis can become more complex while the team still does not know whether to change a page, adjust ads, fix tracking, or pause the conclusion.
Standard reports inspect; Explorations investigate
Standard reports are closer to a fixed dashboard. They help a team see the same trend quickly. Explorations are closer to an ad hoc analysis workbench. They are useful after you find an anomaly and need to ask why it happened.
The steadier order is: use standard reports to confirm whether the issue is real, then use Explorations to explain which people, step, or path caused it. Do not use Explorations as the daily reporting system, and do not rebuild from a blank tab every time.
Four Exploration types answer four follow-up questions
- Free Form: answers “which dimension mix explains the anomaly,” such as source / medium × landing page × device × purchase rate.
- Funnel exploration: answers “where do users drop off,” such as
view_item -> add_to_cart -> begin_checkout -> purchase. - Path exploration: answers “where do users go after a starting point,” such as the path after a high-spend landing page.
- Segment Overlap: answers “which audiences overlap,” such as new users, mobile users, high-value users, cart abandoners, and remarketing audiences.
Write the question first, then choose the template. Do not drag every dimension into one table just to make the view look advanced.
Identify data boundaries before going deeper
Different numbers across reports, Explorations, Data API, and BigQuery do not always mean tagging is broken. They are different reporting surfaces.
- Retention: an Exploration may not show the long history you expected. Check data retention settings first.
- Thresholding: small or sensitive slices may be hidden or compressed. Do not over-read protected small samples.
- Sampling: complex queries can use sampled data. Reduce dimensions or move to another layer when needed.
(other)row: high-cardinality dimensions may be grouped, hiding long-tail URLs, campaign names, or parameters.
If these boundaries affect the decision, stop forcing the GA4 interface to answer it. Move the question to fixed reporting or BigQuery when that is the right layer.
BigQuery and order systems reconcile; they do not define the business question for you
BigQuery Export can send GA4 raw events to a warehouse. It is useful for long windows, complex joins, purchase reconciliation, custom attribution, and long-term BI. But BigQuery is not an automatic answer. You still need to define session, user, purchase, time zone, excluded events, and filtering logic.
When purchase does not match Shopify orders, first check the GA4 and BigQuery link, time zone, excluded events, reporting identity, transaction_id, and order status. Do not expect every interface number to match perfectly.
Real scenario: standard reports and Exploration do not match
For example, the standard channel report says paid social purchase rate looks stable, but a Free Form split by landing page × device shows two weak mobile landing pages. Do not immediately blame GA4, and do not immediately rewrite the page.
A steadier read is: standard reports confirm the total trend; Free Form locates the landing page and device issue; if no clear sampling warning appears but some campaign names are grouped into the (other) row, limit the conclusion to visible pages instead of all campaigns. The page owner checks mobile hero and product entry, then reviews the result in the fixed weekly report after 7 days.
That is the core habit from this lesson: choose the right data layer first, then decide whether deeper analysis is worth doing.