
A useful dashboard starts with a decision
To customize a GA4 dashboard on desktop, build an overview report from summary cards, then add it to a published report collection. You need Editor or Administrator access. Use detail reports for the rows behind each card, and use Explore when you need a funnel or a deeper investigation.
A dashboard should help someone decide what to do next. For a lead-generation team, that may mean identifying which landing pages attract relevant visitors and which produce confirmed enquiries. For an online store, it may mean spotting where product interest stops becoming purchases. A screen full of traffic totals does neither on its own.
Choose the right reporting surface
| Use | Best fit | Boundary |
|---|---|---|
| GA4 overview report | A shared view of a few recurring business questions | Cards draw on GA4 reporting data; this is not an unrestricted design canvas. |
| GA4 detail report | Investigating channels, landing pages or events in a table | Match dimension and metric scope before comparing rows. |
| Explore | Investigating sequences, segments and funnels | Observed behavior suggests hypotheses; it does not prove why someone left. |
| Looker Studio | A presentation combining sources or a more custom layout | Connections, refresh behavior and calculations need their own checks. |
Write a measurement brief before adding cards
Pick an audience, a reporting period and a business decision. Give every metric an owner and a definition. “Leads” should mean something testable, such as accepted demo requests in the CRM. A click on Submit can happen even when a form fails validation.
| Business question | Useful starting data | Check before trusting it |
|---|---|---|
| Which channels bring relevant visits? | Sessions by session channel or source / medium | Campaign tagging and channel definitions are consistent. |
| Which pages start useful journeys? | Landing page, sessions, engagement and a validated key event | The event fires on successful completion, not every button click. |
| Where does shopping stall? | Product views, cart additions, checkout starts and purchases | Ecommerce events and transaction IDs are implemented correctly. |
| Which enquiries become opportunities? | CRM qualification and opportunity stages | Analytics activity can be connected to business outcomes without exposing personal information. |
Keep acquisition scopes separate. A first-user source describes how a user was originally acquired; a session source describes a particular visit. A change in scope can change the story even when the dates match.
Create your overview report
Open the correct GA4 property, enter Reports and find Library. In its report-creation menu, choose an overview. Add the cards needed for your brief, arrange them in decision order, then save the report with a specific name such as “Website demand review.” Google permits up to 16 cards, but a shorter selection is often easier to act on. See the official overview-report instructions.
- DefineDecide what the reader needs to learn.
- BuildSelect the summary cards that answer it.
- ArrangePut the most important decision first.
- CheckReconcile each card with its detail report.
Start with your outcome, then show the traffic and content that may explain it. If enquiry tracking is not ready, say so in the report description. Do not relabel page views as conversions to make the dashboard look complete.

Build a card when the standard selection is not enough
Open the relevant detail report and its customization panel. In the summary-card area, create a card with a supported dimension, metric and visualization. Add a filter only when it is part of the question, apply the configuration and save the report. Google explains the available controls in its summary-card guide.
Example recipe · a lead-generation website
Organic landing-page review
- Question: Which organic entry pages deserve a closer look?
- Dimension: landing page, where supported in the chosen report.
- Traffic metric: sessions, kept separate from active users.
- Outcome: a validated enquiry event, inspected in the underlying table if the card cannot show the required combination.
- Filter: session default channel group equals Organic Search.
- Follow-up: compare useful enquiries and their quality in the CRM before deciding what to rewrite.
Do not force an incompatible dimension and metric into a card. Keep the overview simple and let the detail table answer the more specific question. Google documents how to customize detail-report dimensions, metrics and filters.
Make the report easy to find
A saved report can exist in Library without appearing where colleagues expect it. Add it to a collection and publish that collection through the report-navigation controls. Alternatively, an appropriate overview can be set as the Reports snapshot. Check what a colleague with viewing access sees, rather than assuming that saving automatically changes their navigation. See Google’s overview customization guidance.
Use custom definitions only when you need new data
Check the built-in dimensions first. If you need a custom event parameter, collect and verify it before registering a definition under Admin → Data display → Custom definitions. A name entered here does not create a tracking implementation. Google’s custom-dimension documentation explains scope and the reporting delay.
For example, a form-type parameter could distinguish a demo enquiry from a newsletter signup. A calculated abandonment rate is different: it needs a defined sequence, denominator and analysis. Registering a custom metric called “abandonment” will not calculate it automatically.
Troubleshoot the result before using it
| Symptom | Check first | Next action |
|---|---|---|
| Library or editing control is missing | Your role on this property | Ask the property administrator for the appropriate access; Viewer access does not expose all editing controls. |
| A custom card is unavailable | The detail report was saved and belongs to a collection | Revisit the saved report and collection before recreating the card. |
| Key events show zero | The success event exists and is correctly designated | Test a real completion path and verify the recorded event. |
| GA4 sessions differ from Search Console clicks | Dates, geography, landing URL, source and measurement definitions | Investigate the difference; do not equate sessions with clicks. |
| Engagement looks low | Page intent and collection setup | Review the experience directly. GA4 alone does not establish a UX cause. |
Turn the dashboard into a weekly decision
Record one observation, one plausible explanation and one next action. An observation might be “organic sessions increased while accepted enquiries stayed flat.” Possible explanations include a different audience or a tracking change. The next action is to inspect page and enquiry data, not automatically increase the content budget.
Keep the same definitions across reviews, note releases and campaign changes, and compare equivalent periods. Preserve useful historical reports before editing shared ones. The best dashboard is the one the team can explain and use consistently.
Connect reporting to a useful growth decision
Elatre can help connect acquisition, website journeys and enquiry handling. Explore B2B marketing and lead generation or CRM automation and integration to address the gap your reporting reveals.
Sources and verification
Product and documentation checks: 30 October 2026. Vendor examples are labeled separately from live observations and illustrative calculations.