Google Analytics Has New Dashboards. Which Numbers Belong in Yours?

Google Analytics' September 9 release adds dashboards for bringing key performance indicators into a single report, with drag-and-drop functionality and new visualization options.

A more flexible screen gives you somewhere to organize the numbers. You still need to decide what belongs there, where it comes from and which action it should support.

Start with the path from an eligible visit to a useful business outcome. Then add the exceptions that would stop your team from trusting or acting on that path.

Give the dashboard a job

Choose the person using it and the decision they make.

A campaign owner may need to inspect whether the right audience reaches the intended page. A sales operations owner may need to find inquiries that arrived without an assignment. A business owner may need to understand which acquisition groups reached accepted opportunities.

Those questions can share a view without becoming the same metric.

Write the main decision at the top. If a number cannot change that decision or identify a problem worth investigating, reconsider whether it needs space on the first screen.

When reviewing website measurement features, apply the same test. The purpose is a decision the team can explain, not the largest possible collection of charts.

Show eligible traffic with its unit

Begin with the activity relevant to the business question.

Name whether the count describes requests, sessions, observed visitor records or something else. State the campaign or page group, dates and exclusions. Keep known automated and internal activity separate where the measure requires it.

Preserve unknown sources. A missing campaign value should not become a confident channel assignment simply to complete the chart.

Use a breakdown that helps explain change. A whole-site traffic increase can hide a fall in the campaign group the business wanted. Show the important group sizes rather than relying only on the combined total.

Do not label every extra request a potential buyer.

Add the page's completed task

Choose an action that reflects the page's job.

For a lead form, distinguish a button click, a successful submission and a record received by the team. For a purchase path, distinguish the observed checkout step from a qualifying order in the business system.

Define the numerator and denominator for any rate. Use the same group and observation window. If your completion count comes from a different population, show it separately instead of presenting a misleading ratio.

Include the relevant failure or gap beside the success count. A high submission number is less useful when no one can establish that the destination received the records.

Keep distinct contacts and acceptance visible

A form total should not silently become a new-lead total.

Show the count after the agreed repeat, test and existing-contact checks. Then show the sales acceptance result with its definition and cutoff.

Keep accepted, rejected and unreviewed records distinguishable. An unreviewed inquiry is not a confirmed rejection, and a suitable contact can still be waiting for a conversation.

These are proposed business measures. A new Analytics dashboard does not by itself establish that your CRM acceptance decisions or pipeline records are available there. Confirm the data and reporting connection appropriate to your implementation.

Review the integrations supporting those records before promising a combined view.

Use a small reconciliation example

Consider a hypothetical operating report with invented figures.

The form review contains 100 eligible observed attempts and 70 confirmed successful submissions. The completion rate for that defined group is 70%.

Of the 70 submissions, six are repeats and four relate to existing contacts. The agreed rule therefore leaves 60 new distinct contacts.

Sales has reviewed 50: 35 are accepted and 15 rejected. Ten remain unreviewed. Those statuses reconcile to the 60-contact group.

A dashboard that displays only “70 leads” loses the distinctions. A more useful view gives the owner a next question: are the ten unreviewed contacts assigned, and why did sales reject the 15?

The example is not a target or a measured result. It shows why the definitions should remain visible even when the screen looks cleaner without them.

Give pipeline its own outcome window

An accepted opportunity is a different event from a form submission or an accepted contact.

Define the opportunity stage and the group it belongs to. If you follow contacts from an acquisition period, give them an appropriate time to develop and state how recent groups differ in maturity.

Do not divide this month's spend by every opportunity created this month unless the numerator and denominator describe the same agreed scope. Older contacts may produce opportunities during the current period.

Keep pipeline value, signed business and collected cash separate. A forecast in the sales process is not the same as money received.

Following visitor context into a practical action helps keep those stages connected without collapsing them into one number.

Put operating exceptions on the first screen

Add a short view of problems that need an owner.

That could include failed handoffs, unassigned inquiries, unresolved identity associations or records waiting beyond the team's defined review commitment. Choose exceptions your team can investigate from the available evidence.

Show the owner and a route to the relevant controlled record. Avoid copying personal details into a widely shared dashboard just because they exist in the source system.

Do not make every movement an alert. Agree on the conditions that require a response and the conditions that need a later review.

The dashboard should help the team find the task, not create an endless new queue of notifications.

Record freshness and collection changes

A number without its last update time can be difficult to interpret.

Name the source, refresh timing, timezone and cutoff for important measures. If two systems update at different times, keep that limitation beside the comparison.

Record changes to event definitions, source rules, forms and collection settings. Review consent and visitor choices when explaining which activity the report can observe.

Keep estimated or modeled numbers labeled and separate from directly observed events where their meanings differ. Do not add overlapping totals as though they were additional business.

A chart can change because the observation process changed. Preserve that possibility before attributing the movement to buyer behavior.

Review the dashboard through real questions

Before expanding the view, use it in a short operating review.

Ask whether the user can identify the relevant audience, confirm the completed task, see the acceptance decision and find the unresolved handoff. Trace a few appropriate records where the connection matters.

Check whether the display encourages a conclusion its evidence cannot support. A funnel shape can imply one connected population even when the counts came from unrelated groups. A single quality score can hide the reason a record needs attention.

Remove or relabel anything that makes the underlying definitions harder to understand.

Leave with one action

Choose the first correction from the report. Assign the unreviewed records, fix a receiving path, clarify an eligibility condition or inspect a changed source mix.

Record the owner and the evidence the next review will check. If the dashboard cannot support a decision yet, name the missing connection rather than filling the gap with a more impressive visual.

The September release provides new ways to arrange the view. Your team supplies its meaning through clear units, traceable records and decisions grounded in what the numbers can establish.