Looker Studio (Data Studio) Dashboard for Small Business

Think about the car you drive every day. Under the bonnet there are hundreds of sensors, measuring everything from oil pressure to exhaust temperature. A mechanic can plug in a reader and see every one of them. The driver never needs to know those hundred readings. The dashboard in front of the steering wheel shows only a handful of things: speed, how much fuel is left, whether the engine is running hot, and which warning light is on. That is enough to get where you are going with peace of mind.

Your business website already has the mechanic's reader. It is called Google Analytics 4, together with Google Search Console. Many owners have both installed and have full access, yet open them only a few times a year, because each visit means clicking through a lot of menus without being sure which numbers matter for the shop. What is missing is the dashboard.

In this article I want to walk you through building that dashboard with a free Google tool that many people know as Looker Studio, and some still call Google Data Studio after its oldest name. Google has now changed the name back to Data Studio. The Google Cloud blog announcement of 11 April 2026 says every existing report and data source moves across to the new name with no action on your part. When I opened lookerstudio.google.com, it sent me straight to datastudio.google.com. So if you searched for a Looker Studio dashboard for your small business and the screen says Data Studio, it is the same tool.

A five-minute check before you build anything

Answer these three questions honestly. Question 1: right now, signed in with your own Google account, can you open both GA4 and Search Console, without phoning your web team or agency for a password? Question 2: if someone asked how many customers the website brought in to contact you last week, could you answer within a minute? Question 3: when was the last time you opened GA4 because you genuinely wanted to know something?

If the answer to question 1 is no, sort out access first. A dashboard can only pull what its creator's account is allowed to see. According to Google's documentation, connecting GA4 needs at least Read & Analyze permission on the property, and Search Console needs view permission on the property, using the same account you sign in to Data Studio with.

If questions 2 and 3 were hard, this article was written for you.

How Looker Studio (now Data Studio) works, in the parts an owner needs

There are three layers. At the bottom is the connector, the pipe to a data source. Google builds its own connectors for Google Analytics, Search Console, Google Ads and Google Sheets. Anything that is not a Google product, such as Facebook Ads, needs a connector built by a third party. The middle layer is the data source: a finished pipe that remembers which property it connects to and whose permission it uses to fetch data. The top layer is the report, the dashboard where you drag in number boxes and charts.

There is one small detail about data sources worth knowing. If you create one while editing a report, it is embedded in that report, and anyone who can edit the report can also change the connection. If you create it from the Data Studio home page, you get a reusable data source that can serve several reports and is shared separately from them. For a shop that will let staff or an agency help out, I prefer reusable data sources, because they keep permission to view the report clearly separate from permission to touch the data.

The numbers are not as fresh as you think

This one is worth knowing before it surprises you. Data Studio's data freshness documentation says data from Google's marketing products, including Google Analytics and Search Console, refreshes every 12 hours, and that rate cannot be changed. People who can edit the report can refresh it manually from the menu, and if the viewer refresh option is switched on, staff with view-only access can do it too.

In practice, I recommend setting the dashboard to look back at the week that has already ended rather than today. An owner's dashboard is for direction, not for counting visitors minute by minute.

Who sees the data, and on whose permission

This is the part people skip and regret later. The data credentials documentation explains that each data source uses either Owner's credentials or Viewer's credentials. With the first, everyone you share the dashboard with sees the numbers through the data source owner's permission, even if they have no GA4 access themselves. With the second, each viewer needs their own access to the underlying data, and anyone without it sees empty boxes.

For a small shop that wants front-of-house staff to see the numbers once a week, Owner's credentials is the most convenient. Just remember that you are lending your own access to whoever has the report, so I'd share it only with people you trust. Also worth knowing: anyone who can edit a data source can make themselves the credentials owner, so keep edit rights with as few people as possible.

The six numbers I would put on one page

A good dashboard is not measured by how many charts it has. It is measured by how many business questions it answers when you open it. If I were choosing for a shop that sells through Facebook and LINE and uses its website as a storefront, I would place just six things.

Start with the number of times customers contacted you from the website, whether that is tapping to call, adding you on LINE or sending a form, as long as it is a key event already set up in GA4. This number is the reason the website exists, so it belongs top left and biggest. If you want to go further into turning visits into contacts, our article on conversion rate for business websites covers it.

Next comes visitors by channel: Google, Facebook, LINE, or people typing your address directly. Set beside the first number, it starts to show which channels bring people ready to talk and which bring passers-by.

The third set is which pages people landed on before they went on to contact you. Some shops discover that the page doing the selling is not the home page at all, but a single, carefully written product page.

From Search Console I would take clicks from Google and the number of times the site appeared in search results, shown together as a weekly line. For reading those two numbers more deeply, I have already written a piece on reading Search Console in the AI Mode era, when rankings hold but clicks disappear.

Alongside that goes a table of the search terms people typed before finding you, sorted by clicks. It tells you the words customers actually use, which are often not the words you use for your own products. The basics of what Search Console is and how it differs from GA4 are in our beginner's guide to GSC.

The last one is a number no tool can see by itself: customers who messaged you on LINE or phoned and said they found you through the website. If you or your sales team already note these in Google Sheets, that sheet can join the same dashboard through Google's own connector.

Those six answer the one question an owner wants answered every Monday morning: how hard did the website work for the shop last week, and what should we do next?

"GA4 already has everything. Why build another page?"

That's true, and I won't argue with it. Every number above already lives in GA4 and Search Console, and if you already open both every week, you may not need a dashboard at all.

The difference is who opens it. GA4 is designed for people who already know what they are looking for. Most owners open it, meet a dozen menu sections, and close it before finding the number they wanted. A one-page dashboard removes that step, so the same data actually gets looked at. It can also be sent to people who have no GA4 access, which the GA4 screens themselves cannot do. For the wider picture of how website data helps a business, see our article on data analytics and business websites.

Why starting early pays off

One week of numbers tells you very little. Is 12 contacts good or bad? Nobody can say without knowing what is normal for your shop. A dashboard becomes truly useful once you have looked at it steadily for about two months, long enough to know what normal looks like and what does not.

After that, small decisions get faster on their own. Did the promotion posted on your page move contacts from the website? Did the new article bring new search terms into the table? The sooner the habit starts, the sooner the comparison line gets long enough to be useful.

The habit compounds, like interest.

The smallest version that genuinely works

No need for it to be pretty, carry a logo or run to several pages. One page is enough. At the top, a single date range control, defaulting to the last seven days compared with the seven days before. The first row holds four number boxes: contacts, visitors, clicks from Google, and customers from your own sheet. The second row is one weekly line chart. The bottom row has two tables: landing pages that led to contact, and search terms from Search Console.

Reading it should be as simple as the layout. Look at the contacts box first, to see whether it moved up or down from last week. If it moved, check whether visitors and Google clicks moved with it, then finish at the two tables to find which page or search term was behind it. The whole thing takes less time than a cup of coffee. If every box is about the same as last week, close it and get on with your day. A steady week is good news too.

Build the report with the company's Google account, not one employee's personal account. The reason is in our own case further down.

Traps that make the numbers look strange

The most common one is accidentally including today in the date range. Data Studio's GA4 sampling documentation says Google Analytics may apply sampling to large data sets, and that Data Studio does not indicate whether the data it shows was sampled. If your dashboard does not match GA4, first check that you are comparing exactly the same dates, and try removing today. Small shops may rarely hit this, but knowing it saves you a long hunt for the cause.

Next is quota. The GA4 connector documentation says reports pulling GA4 data are subject to Google Analytics Data API quotas, which Google's quota page sets for standard properties at 200,000 tokens per day and 40,000 tokens per hour. A single page with a few boxes hardly touches that ceiling. Build ten pages with twenty charts each, share them with lots of people who open them at once, and you may see boxes showing an error. That is one more reason I like a one-page dashboard.

Search Console has its own source of confusion. When you connect it in Data Studio, you choose between Site Impression, which counts across the whole site, and URL Impression, which counts per page. They count differently, so their totals will not always match. Some search terms will also appear blank, because Google withholds very rare queries or ones that could identify a person, to protect searchers' privacy.

The one I would most like you to watch is sharing the report with anyone who has the link. Data Studio's sharing documentation warns that with public link sharing, any data source embedded in the report also becomes accessible to anyone with the link. For your shop's sales numbers, I recommend sharing by named email address, giving the team Can view, and ticking the option that stops editors from sharing it further.

Real examples you can open today

If you still cannot picture a dashboard, open the Data Studio Report Gallery at datastudio.google.com/gallery. Under Marketing Templates there are reports built by Google's Data Studio Team as examples, such as Ecommerce Store, which shows data from the Google Merchandise Store, Google's own example shop, and Acme Marketing Website, built for a fictitious company called Acme Widgets. Open one, use it as a template, then switch the data source to your own.

One thing to know: many gallery templates are old, and some names still refer to the older generation of Google Analytics reports. Once you connect GA4, some boxes may need their metrics chosen again. So I treat the gallery as a source of layout ideas rather than a finished product.

It is also worth seeing the paid tier, Data Studio Pro. Google's documentation on Pro says reports and data sources in Pro belong to the organisation rather than to individual users, and that a report can have up to 200 delivery schedules. The free version allows one schedule per report. For a small shop that wants one page in the inbox every Monday morning, one schedule is plenty.

A case from our own team, when we rebuilt the TumWebSME website

When our team rebuilt the TumWebSME website in 2026, we found that our old GA4 property was one nobody on the current team could access. The old data was still stored somewhere, but we could not open it. The fix was to create a new property under the company's own Analytics account and start counting again from that day.

The lesson applies directly to dashboards. In the free version, a report belongs to the person who created it, and with Owner's credentials every number on the page is fetched through that person's access. The day they change jobs or lose access, the dashboard the whole team opens every week could come up empty the following Monday. Building everything under the company account from the start is far cheaper than fixing it afterwards.

Our second case is about warning lights. After the new site launched, we had already started running Google Ads, but the conversion tracking code, which had gone live with the site, wasn't actually running on the live site for about a week because it sat in the wrong place. Clicks arrived as normal, yet conversions read zero every day, because the measuring device was not switched on. What we took away was to verify on the live site every time, rather than trusting that code sitting in the system will work by itself.

I tell this story because it is exactly what a dashboard warning light is for. A contacts line that drops to zero while visitors look normal almost never means every customer vanished overnight. Usually it means the measurement broke. If you see that shape one Monday morning, tap the contact button on your own website with your own phone first, then call your web team.

One more thing from our team: the sales team asks every customer who calls or messages on LINE where they found us and what they searched for, because measurement tools cannot see LINE chats. So the sixth number on the dashboard comes from people writing things down, not from a machine, and I think that is the most honest part of the page.

A five-step plan you can finish in one afternoon

1. Check that the company's Google account has at least Read & Analyze access in GA4 and view access in Search Console. If it does not, ask your web team to add it first.

2. Sign in to Data Studio with that account and create three data sources: GA4, Search Console using Site Impression, and the Google Sheet where LINE and phone customers are logged.

3. Build a one-page report with a date range control, four number boxes, one line chart and the two tables described above.

4. Share it with the team by individual email address, with Can view, and tick the option that stops editors from sharing it further.

5. Set up Schedule delivery to send the report to your inbox every Monday morning. Google's documentation says you can add up to 50 recipient addresses. The email attaches the report as a PDF with a link to the full report (an inline preview is a Pro feature).

How to tell whether the dashboard is really working

A dashboard is not judged by how good it looks. I use just two questions. Start by asking: over the past four weeks, did you open it every Monday morning? If not, the dashboard is still too hard or does not yet answer what you care about, so remove the boxes you never look at.

Then ask: in the past month, did at least one decision come from a number on this page? Moving post budget to the channel that brings more contacts, for example, or adding detail to a product page that gets plenty of visits and no enquiries. If there was even one, the dashboard has already paid for that afternoon.

Back to the car dashboard

Nobody drives with the bonnet open, watching the engine. We glance at a few gauges and head to the garage when a warning light comes on. A website deserves one page like that, so the owner can see the direction every week in under a minute and know when it is time to call the mechanic to look inside.

If you are planning a new website and want the team building it to set up GA4, Search Console and measurement under the right accounts from day one, you can see the scope of our work on the TumWebSME package page, then drop us a message and tell us about your shop.

Follow TumWebSME

Follow us for insights on website development and online marketing:

• Facebook: TumWebSME Business Website Development

• Instagram: @tumwebsme

• TikTok: @tumwebsme

• YouTube: TumWebSME

Contact Us and Inquire About Services

• 088-983-9386 (Ploy)

• 099-856-3198 (Saennan)