You can have a working Data Studio report in about ten minutes: connect a data source, add a few charts, add a date control, share the link. The tool is genuinely easy to start with — the hard part is deciding what belongs on the page, which is what most tutorials skip.
This walks through building a real report from an empty canvas, then covers the four decisions that separate a dashboard people use from one nobody opens.
Before you open the tool
One question first, and it’s worth ninety seconds: what will this report be used to decide?
Not “what data do we have” — what decision. “Should we keep spending on this channel.” “Is the blog working.” “Which pages should we fix next.” A report built to answer a question has an obvious shape. A report built to display available data becomes a wall of charts nobody reads.
This is the most common beginner pitfall, and it’s a habit worth forming now: rushing to build before analysing the data produces a pretty report that conveys nothing, which is a waste of everyone’s time.
Step 1 — Connect a data source
- Go to datastudio.google.com and sign in.
- Create → Report. A blank canvas opens with the Add data panel already showing.
- Pick a connector. If you’re learning, use GA4 or Search Console — both free and native.
- Choose the property and click Add.
Data Studio drops a default table onto the page. Delete it — it’s a starting point, not a design.
Step 2 — Add your headline numbers
Start with scorecards, not charts. Three or four numbers that answer the question at a glance, across the top of the page.
- Add a chart → Scorecard.
- Set the metric — sessions, clicks, conversions, whatever your question needs.
- In the Comparison date range setting, choose Previous period. This single setting turns a number into a trend, and it’s the highest-value two seconds in the whole build.
- Duplicate it (Ctrl/Cmd + D) and change the metric, rather than building each one from scratch.
Step 3 — Add one chart that shows the shape
Underneath, one time series. Sessions or clicks over time, with the same previous-period comparison.
The rule that will improve your charts faster than any tutorial: choose visualisations that are appropriate for the type of data you’re visualising — don’t just choose them because they look pretty. Time series for change over time, bar for comparing categories, table for detail people need to read or export. A pie chart with nine slices is a table wearing a costume.
There’s a fuller breakdown in chart types explained.
Step 4 — Add a breakdown people will actually use
One table. Channel, landing page or query — whichever your question needs — with two or three metrics.
Keep it to the columns someone would act on. A table with fourteen columns gets scrolled past; a table with four gets read.
Step 5 — Add controls so people stop asking you things
Two controls turn a static picture into something people can interrogate:
- A date range control — so nobody has to ask “can I see last quarter?”
- A filter control on your main dimension, so they can narrow to one channel or section themselves
Place them top-right, above your scorecards. Consistency matters more than position — put them in the same place on every report you ever build and people will stop hunting.
Step 6 — Add the part that makes it a report
Here’s what separates a dashboard from something a stakeholder actually values. A dashboard is for exploring; a report is for explaining. You can’t use one in place of the other, and a link to twelve charts answers “what happened” while leaving “so what” entirely unanswered.
The cheap fix is a text box. Add one at the top, and write two or three sentences saying what changed and what you’re doing about it. If you want it to keep working month after month, keep annotations in a Google Sheet — date, event, description — and blend it onto the report by Date, so context sits beside the numbers it explains.
It has a useful side effect too: when a chart breaks — and charts break — a page with commentary on it is still useful to whoever opened it.
Step 7 — Share it
- Share top-right. Add people by email, or Manage access → anyone with the link.
- Viewers don’t need a Data Studio licence, and depending on the setting, may not need a Google account.
- Use Schedule delivery if someone wants a PDF in their inbox rather than a link they’ll never click.
Then do the thing most people skip: send it to one person and see what they ask for. The follow-up questions tell you what the report is missing far better than another hour of building will.
Four decisions that make the difference
| Decision | The rule |
|---|---|
| Who’s reading it | An executive wants a stable overview. An analyst wants to dig. Trying to serve both on one page serves neither — use separate pages. |
| How much to show | Don’t cram every metric in. Too much data overwhelms the audience and buries the insight. |
| How to structure it | Keep a stable, holistic overview on page one, linking through to fancier, less-stable, granular views. A broken chart on page four then never takes down page one. |
| What to say about it | Don’t leave people to work out their own next steps. The recommendation is the deliverable. |
Frequently asked questions
How long does it take to build a first report?
About ten minutes for something genuinely useful — connect a source, three scorecards, one time series, one table, a date control. Deciding what belongs on the page takes longer than building it.
Do I need to build from scratch?
No, and it’s often a worse way to learn. Copying a template and taking it apart teaches you the decisions, not just the buttons. See how to copy and reuse a template.
What should go on the first page?
Whatever answers the question the report exists for — usually three or four headline numbers with a previous-period comparison, one time series, and one breakdown table.
Why does my report look empty or show “no data”?
Usually the date range covers a period before your tracking started, or a filter is excluding everything. Widen the date range first.
Can people view my report without a Google account?
Often yes, depending on how you share it. Viewers never need a paid licence.
How many pages should a report have?
As few as answer the question. One well-built page beats six half-built ones, and extra pages are best used to separate audiences rather than to hold more charts.