Monday morning, a service-business owner can have Google Analytics, an ad account, a CRM and a spreadsheet open at the same time. Every screen has numbers. The real question is still sitting there: what needs attention this week?
Google added Dashboards to Google Analytics on September 9, 2026. The feature puts custom visualizations on one report, with drag-and-drop editing and several ways to display the data.
Google’s dashboard guide lists scorecards, tables, line charts, bar charts, donut charts and funnel charts. A standard property can hold up to 15 cards on one dashboard. Editors and Administrators can create and publish it, and people with access to the property can view the published version.
That gives you enough room to build a useful weekly view. The harder part is deciding what earns a place on it.
Give the dashboard one job
Call it “Weekly Owner Review.” Its job is to show what changed on the website and point you toward the next place to inspect.
Google Analytics covers the website side of that review: visits, traffic sources, landing pages and the actions your tracking records. The CRM covers the sales side: inquiries, qualified leads, appointments, won work and revenue. Bring both into the same meeting, with each source doing the job it was built to do.
This split matters. A click on a phone number shows website intent. The connected call and its outcome belong in call tracking or the CRM. A form confirmation shows that the website recorded a submission. The CRM shows whether that person fit the service, booked and became a customer.
Start with eight cards or fewer
The 15-card limit can help you stay focused. Begin with a smaller first version:
- One scorecard for your chosen website traffic measure, using the dashboard’s date comparison.
- A table showing traffic by channel or source.
- A table showing the landing pages where visits began.
- A scorecard for completed contact forms.
- A scorecard for tracked phone-link clicks.
- A scorecard for confirmed online bookings, when the site supports them.
- A line chart showing the main website action over several weeks.
- A funnel showing the path from landing page to service page, contact step and completed action, when those steps are tracked consistently.
Leave the remaining space for a question that comes up repeatedly in your business. A dental practice may need a page-level view for a high-value treatment. A contractor may need to separate emergency-service visits from planned-project visits. The card earns its place when somebody uses it to make a decision.
Google currently leaves segments and card-level comparisons outside the dashboard feature. Use the underlying Analytics reports when the weekly change needs a closer breakdown.
Write the definition under every KPI
Two people can look at “leads” and mean two different things. Fix that before the first review.
Keep a short definition sheet beside the dashboard. For every card, write the name, the exact event or field behind it, the data source and the person responsible for checking it.
For example, “form submitted” can mean the success event recorded after the site accepts the form. Opening the form stays a separate action. “Phone click” means a tap on the website’s phone link. “Booked appointment” counts after the booking tool confirms the slot. In the CRM, “qualified lead” and “won” each need a written entry rule.
Revenue needs its label too. Booked value, invoiced value and collected revenue answer different questions. Pick the one used in the weekly review and name it plainly.
These definitions turn a chart into a shared operating tool. They also make tracking problems easier to spot. If form confirmations fall while the CRM still receives the usual number of website inquiries, check the event setup. If website actions hold steady while qualified leads fall, read the lead records and source mix before changing the page.
Bring CRM outcomes into the same meeting
Put a small CRM outcome table beside the Analytics dashboard. Use a separate CRM view until the data connection has been checked and the definitions match.
For inquiries that have had enough time to move through the normal sales cycle, review:
- New inquiries by original source
- Qualified leads under the written rule
- Appointments held
- Won and lost opportunities
- Booked, invoiced or collected value, using the chosen label
- Open opportunities with a next action and date
Now the website numbers have business context. A source can send fewer form submissions and still appear in more of the records that became customers. Another source can create plenty of activity while producing a qualification problem. Small counts deserve a record-by-record check before a budget or page changes.
When we connect Paid Advertising and CRM & Revenue Infrastructure, we define the website actions in Analytics, preserve the original source in the CRM and give pipeline outcomes clear rules. The weekly review can then follow the same path the customer took.
Finish with one written action
Use the same routine each week:
- Set a fixed date range and comparison period.
- Scan the dashboard and choose the one change that matters most.
- Open the underlying report, page or lead records and check what moved.
- Read the CRM outcomes before making a campaign or website decision.
- Write one action, one owner and the date you will check it again.
The action might be repairing a form event, reviewing calls from one source, clarifying a service page or waiting another week for recent inquiries to mature. The dashboard has done its job when the next check is clear.
Start with the eight-card version and run it for four weekly reviews. Remove the cards that sit unused. Add a card when the same useful question keeps sending you into another report.
If your website activity and CRM outcomes still live in separate worlds, talk to us about your measurement setup. Glory Digital Solutions can map the tracking, source fields, pipeline stages and weekly reporting around the way your business works.
Source note: Google announced Dashboards in Google Analytics on September 9, 2026. Its official documentation describes the single-page layout, supported charts, role requirements, property-wide sharing and current feature limits. The dashboard structure, KPI definitions, GA and CRM review method, and weekly routine in this article are original Glory Digital Solutions guidance.