Learning path · Level 5 · Tutorial 5

Build a Decision-Focused Looker Studio Dashboard

Build a focused Looker Studio dashboard using practice rows written on screen and manually entered into your own Google Sheet, or a suitable source you can access. Validate the results and use them to explain a business-relevant finding without a live website or paid connector.

  • Level: Intermediate
  • Duration: 25 min
  • 9 steps
Start tutorial Back to the path
Build a Decision-Focused Looker Studio Dashboard

What you will go through

  1. Start with the Decision Define a focused dashboard brief for Northstar Studio before building the report. 2 min
  2. Create a Chart-Ready Practice Sheet Create the complete Northstar Studio practice table in your own Google Sheet, using consistent records and field types that will be ready for later charting. 4 min
  3. Connect the Sheet and Check the Fields Connect the practice sheet through Looker Studio’s free Google Sheets connector and verify the field settings needed for reliable count-based charts. 3 min
  4. Calculate a Rate That Aggregates Correctly Create a calculated Session key-event rate that stays valid when the underlying rows are grouped or filtered. 3 min
  5. Build the Overview Scorecards Create a focused one-page overview with three readable, verifiable scorecards. 2 min
  6. Add the Trend and Channel Comparison Build complementary trend and channel-comparison views that keep inquiry-session rates connected to their supporting counts. 3 min
  7. Test Dates, Totals, and Freshness 4 min
  8. Share Without Exposing the Source Choose a restricted sharing setup and understand how report permission differs from access to the underlying source. 2 min
  9. Present One Finding and One Next Check Present a validated dashboard finding carefully, with an appropriate next check, limitations, and sharing boundary. 3 min

What you will learn

  • Define one business question and select a small set of measures that can answer it.
  • Create a consistently structured practice table and connect it to Looker Studio using a free connector.
  • Build scorecards, a trend chart, a channel comparison, and a usable date control.
  • Check field types, totals, date behavior, and a session key-event rate against the underlying practice rows.
  • Present one supported finding and one next check, while identifying data limitations and appropriate sharing restrictions.

Before you start

  • Set Marketing Objectives and Calculate Core KPIs
  • Read GA4 Acquisition, Engagement, and Key-Event Reports

Step 1 of 9

Start with the Decision

Define a focused dashboard brief for Northstar Studio before building the report.

The decision frame

Start with a focused brief

A dashboard begins with a decision

A useful dashboard brief names three things:

  1. Audience: who will use it.
  2. Business question: the one question it should help investigate.
  3. Next decision or check: what the audience should examine next.

For Northstar Studio, the audience is the marketing lead. The question is: Which acquisition channel deserves the next inquiry-performance check?

This is deliberately narrow. The dashboard should help prioritize an investigation, not attempt to explain why a result happened.

Diagram showing a marketing lead using one business question and three measures to prioritize a channel investigation.

A decision-focused dashboard connects its audience, question, measures, and next check.

Set useful boundaries

Measures for the inquiry question

Choose only measures that answer the question

Use these three measures, viewed by date and channel:

  • Sessions — the volume of recorded visits.
  • Sessions with key event — sessions containing the designated key event.
  • Session key-event rate — the share of sessions containing that event.

In this practice, the only designated key event is an inquiry submission. A session with one or more inquiry submissions contributes once to Sessions with key event.

Together, the measures show volume and inquiry-session performance. A rate without its supporting counts can be misleading, so the dashboard will keep them together.

Example

Example

Dashboard brief example

  • Audience: Northstar Studio marketing lead
  • Question: Which acquisition channel deserves the next inquiry-performance check?
  • Measures: Sessions, Sessions with key event, and Session key-event rate, by date and channel
  • Next check: Review the relevant channel detail and inquiry measurement before making a change

The dashboard can show a difference. It cannot, from these measures alone, prove a cause or prescribe a budget change.

Choose your practice route

You will build in your own browser with your own Google Sheet and Looker Studio account, using free features. No live website, paid connector, supplied project, or downloadable file is required.

If you cannot access an account, continue with the on-screen planning and validation work. You can still create a dashboard specification, but you will not create a live report.

Practice: select the right brief

Choose the focused brief

Which dashboard brief is the best fit for Northstar Studio's stated business question?

Step 2 of 9

Create a Chart-Ready Practice Sheet

Create the complete Northstar Studio practice table in your own Google Sheet, using consistent records and field types that will be ready for later charting.

Build a rectangular source

Set up one tidy source table

Create a Google Sheet named Northstar Studio - Dashboard Practice. Name its worksheet Daily channels.

This sheet is a small, rectangular practice source: one header row followed by 12 records. Each record represents exactly one Date + Channel combination. The three channels repeat once for each of four dates.

Use the headers exactly as shown in the next screen and keep their order. This source is synthetic practice data, so you can enter it manually in your own Sheet—no download, live website, or external dataset is needed.

Diagram of a clean rectangular spreadsheet with one header row and consistent date-and-channel records, contrasted with merged cells and embedded subtotals that should not be used.

A chart-ready source has one consistent row grain: one date and one channel in every data row.

Enter the 12 source records

Enter the complete practice rows

Enter the following four headers in row 1, from left to right: Date, Channel, Sessions, and Sessions with key event.

Then enter the 12 rows below. Enter dates as real date values, not as labels or plain text, and format the Date column to display YYYY-MM-DD. Keep both count columns as whole numbers. Do not add a total row.

Synthetic practice data for Northstar Studio. Each row is one date-and-channel combination.

Daily channels source rows — enter all 12 rows, with no additional totals or percentage column.
DateChannelSessionsSessions with key event
2025-06-01Organic Search10010
2025-06-01Email204
2025-06-01Organic Social804
2025-06-02Organic Search12012
2025-06-02Email306
2025-06-02Organic Social1005
2025-06-03Organic Search808
2025-06-03Email408
2025-06-03Organic Social1206
2025-06-04Organic Search20010
2025-06-04Email102
2025-06-04Organic Social1005

Tip

Keep labels consistent

Use the channel labels exactly: Organic Search, Email, and Organic Social. Small label differences, such as “Organic search” or extra spaces, can split one channel into separate groups later.

Make the data reliable

Assign the right field types

Before using the sheet, check its field roles. A date must remain a date so records can be organized by time. Channel is descriptive text. The two count fields must be numeric values, not numbers stored as text.

This source deliberately contains counts only. Do not add a precomputed percentage column: rates need to be calculated from the relevant grouped counts later.

Use this structure when reviewing the columns in your Sheet.

Required roles and stored values for the practice source.
FieldStored asRole
DateActual date valueTime dimension
ChannelTextChannel dimension
SessionsNumeric whole numberSession count
Sessions with key eventNumeric whole numberKey-event session count

Warning

Check structure and plausible counts

Keep the grid plain: no merged cells, embedded subtotals, blank separator rows, or duplicate Date + Channel records. A recorded 0 means the value was observed as zero. A blank means the value is missing or unknown; do not silently treat it as zero.

For every row, Sessions with key event must be zero or greater and must not exceed Sessions. The supplied rows meet that check.

Practice: identify roles and a structural risk

Check the chart-ready structure

Match each field or table condition to its required type, role, or consequence.

Tap an item and then its matching pair.

Step 3 of 9

Connect the Sheet and Check the Fields

Connect the practice sheet through Looker Studio’s free Google Sheets connector and verify the field settings needed for reliable count-based charts.

Know the three layers

Confirm access first

Before connecting, confirm that you can open the Google Sheet Northstar Studio - Dashboard Practice and its Daily channels worksheet. Also sign in to Looker Studio with a Google account that can create a report.

Builder route: If you have access, create a blank report named Northstar Studio - Acquisition Review.

Observation-only route: If you cannot open the Sheet, authorize the connector, or create a report because of account or organization restrictions, continue with this step’s diagram, field settings, and sequencing practice. You can record the expected setup without claiming that you created a live connection. Ask a Sheet owner or administrator for access only if you later want to build the report.

From worksheet to dashboard

A diagram showing a worksheet flowing into a connected data source with field settings, then into a dashboard.

The worksheet supplies rows; the connected data source interprets fields; the report displays charts.

Add the Google Sheets data source

Connect the practice sheet

Builder route: In Looker Studio, choose Add data and select the free Google Sheets connector. Authorize access if prompted. Select Northstar Studio - Dashboard Practice, then choose the Daily channels worksheet. Confirm that the first row is used as headers, then add the data to your report.

Interface wording can vary slightly, but the choices should correspond to the spreadsheet, worksheet, and header row.

Observation-only route: Record this intended connection sequence: Google Sheets connector → Northstar Studio - Dashboard Practice → Daily channels → first row as headers. Do not state that the source was connected unless you completed it in your own account.

Tip

Using another source?

An existing source is suitable only when it has compatible date-and-channel detail and a genuine numerator for sessions containing one or more inquiry submissions. If you use one, validate it against its own records—not against this tutorial’s synthetic practice totals.

Make the fields chart-ready

Inspect the detected fields

After connecting, open the data source field list before creating charts. Looker Studio detects field types, but detection is not proof.

Builder route: Inspect the detected fields in your connected data source and correct any mismatch.

Observation-only route: Use the required settings below as your field-settings specification. They describe what a correctly connected practice source must show before charts are built.

Required field settings

Use these settings for the practice source.

Dimensions describe each row; metrics are values that charts aggregate.
FieldRole and typeAggregation
DateDimension · DateNot applicable
ChannelDimension · TextNot applicable
SessionsMetric · NumberSum
Sessions with key eventMetric · NumberSum

Warning

Fix types before charts

Fix a field before relying on a chart. A Date detected as text cannot drive date behavior correctly. A count detected as text cannot be summed reliably. Set both count metrics to Sum; do not use an average for these row-level counts.

If you are observing only, identify these as required corrections in your setup notes rather than attempting a live edit.

Practice: connect, then verify

Sequence the setup and field check

Put the connection and inspection tasks in the only workable order before building charts. This sequence also identifies the source settings that must be corrected if detection is wrong.

  1. Confirm that the source sheet and worksheet are accessible, or switch to the observation-only setup notes.
  2. Select the spreadsheet and Daily channels worksheet, use the first row as headers, and connect the source.
  3. Inspect fields; correct Date and count-field types if needed, then set both count metrics to Sum.
  4. Create a Looker Studio report and choose the Google Sheets connector.

Step 4 of 9

Calculate a Rate That Aggregates Correctly

Create a calculated Session key-event rate that stays valid when the underlying rows are grouped or filtered.

Aggregate before you divide

A rate is a ratio of aligned totals

A rate must be calculated from counts that belong to the same slice of data. For this dashboard, divide the total Sessions with key event by the total Sessions.

Create this as a reusable data-source metric, not as a manually typed percentage. When a chart groups rows by Channel or shows a subset of dates, Looker Studio can recalculate both totals for that same set of rows before dividing.

How the full-period rate is formed

Diagram showing source rows being summed into 80 sessions with a key event and 1,000 sessions, then divided to produce 8.0 percent.

For all 12 practice rows, aggregate first: 80 ÷ 1,000 = 8.0%.

Create the calculated metric

Reusable calculated metric

In the connected data source, add a calculated metric. Set its field name to Session key-event rate, then paste only this expression into the formula editor.

Looker Studio formula
SUM(Sessions with key event) / SUM(Sessions)
Expected output
8.0%

Expected result when the full 12-row practice dataset is included and the field is formatted as Percent.

Metric settings

Use these settings after saving the metric.

The source count fields remain summed; do not multiply the formula by 100.
SettingValueWhy
Field nameSession key-event rateMatches the dashboard measure
Display typePercentShows a decimal ratio as a percentage
FormulaRatio of summed countsKeeps numerator and denominator aligned
AggregationAutoRetains the calculated metric behavior

Keep the numerator and denominator together

Why row averages mislead

Do not average the percentage for each source row. Rows have different session volumes, so an unweighted average gives every row the same influence.

With the full practice dataset, the ratio of totals is 80 ÷ 1,000 = 8.0%. The simple mean of the 12 row-level percentages is 11.25%, which is not the dashboard's Session key-event rate.

Compare the calculations

Two methods can produce different results from the same rows.

Use the ratio of totals for a grouped or filtered view.
MethodCalculation scopeFull-period resultUse for this rate?
Ratio of totalsAll matching key-event sessions ÷ all matching sessions8.0%Yes
Unweighted row averageMean of 12 row percentages11.25%No

Warning

Zero is not a performance rate

A rate has no meaningful value when its total Sessions denominator is zero. Treat that result as undefined, not as 0% performance. Every supplied practice row has a positive Sessions value.

Check the aggregation logic

Complete the rate formula

Complete the calculated-field expression for Session key-event rate.

Looker Studio formula
SUM() / SUM()

Choose the reason

Why is an unweighted average of the 12 row-level rates not the correct full-period rate?

Step 5 of 9

Build the Overview Scorecards

Create a focused one-page overview with three readable, verifiable scorecards.

Lay out one decision view

Plan the overview

Work in one single-page decision view in the report. Builder route: Open your existing Looker Studio report and rename it exactly Northstar Studio - Acquisition Review before adding scorecards. Observation-only route: Record Northstar Studio - Acquisition Review as the required report name in your dashboard specification; do not claim that you renamed or created a live report.

Place a clear report title at the top, then a compact context area, then a row for three scorecards. Leave uncluttered space below for supporting views you will add later.

Use these context labels exactly:

  • Synthetic practice data
  • Data covers: 2025-06-01 to 2025-06-04
  • Source last checked: YYYY-MM-DD

Replace the final placeholder with the date you actually checked the source. Coverage describes dates available in the source; it does not describe a viewer-selected reporting period.

A calm overview layout

Use a simple reading path: title and context first, then the three decision measures. Alignment makes the cards read as one set rather than unrelated widgets.

Schematic dashboard with a title and context at the top, three aligned scorecards in the middle, and open space below.

The scorecards should be the first numerical information a marketing lead can scan.

Build and format the cards

Configure only the core measures

Add three scorecards in one aligned row. Configure them with these exact metric labels:

  1. Sessions
  2. Sessions with key event
  3. Session key-event rate

Builder route: Configure the cards in your report to show the complete four-day practice coverage for this initial build. If an automatic recent-date setting excludes the practice rows, set the cards’ current range to include 2025-06-01 through 2025-06-04 for this initial check. A later step will add the interactive control and replace any conflicting fixed chart range.

Observation-only route: Record these three scorecards and the full four-day coverage as the required initial configuration. You are specifying expected behavior, not testing a live report.

Do not add a prior-period comparison, change arrow, or “up/down” color indicator. The practice source has no comparison period that supports one.

Tip

Make the values checkable

Format Sessions and Sessions with key event as whole numbers with English thousands separators. Format Session key-event rate as a percentage with one decimal place. Keep the calculated metric’s normal aggregate behavior.

Avoid compact displays such as “1K.” They save little space here and make source validation less transparent. Use adequate contrast between labels, values, and the page background; do not rely on color alone to distinguish cards.

Use hierarchy, not decoration

Use a strong title, readable metric labels, and restrained color. Color can organize the page, but it should not imply that a value is good or bad without a defined benchmark. Keep the cards equal in size and aligned so the marketing lead can scan the three related measures before looking at supporting charts.

Check the visual hierarchy

Choose the usable overview

Select the schematic overview that follows the build guidance.

Review the full-period benchmark

Example

Expected initial scorecards

For the complete four-day practice coverage, the expected initial scorecards are:

  • Sessions: 1,000
  • Sessions with key event: 80
  • Session key-event rate: 8.0%

Builder route: Inspect your three scorecards and compare their labels, units, and values with these benchmarks. A mismatch is a prompt to check the card metric, number format, or underlying source and calculation before treating the dashboard as decision-ready.

Observation-only route: Use these as expected benchmarks for your dashboard specification. Mark live display behavior as not tested; do not claim that scorecards displayed these values.

Record your comparison

Validate your overview

Compare your overview with the full-period benchmark from the previous screen.

Builder route: Record whether your live scorecards match, including each metric label and displayed value.

Observation-only route: Record the required scorecard configuration and state that live display behavior is not tested. Do not claim that you viewed live scorecards.

Write at least 20 characters (0/20).

Step 6 of 9

Add the Trend and Channel Comparison

Build complementary trend and channel-comparison views that keep inquiry-session rates connected to their supporting counts.

Choose the view for the question

Two complementary views

A trend chart and a channel table answer different questions.

Use a trend to ask: When did recorded inquiry-session volume change? It shows Sessions with key event across dates.

Use a channel table to ask: How do channels compare in volume and rate? It keeps Sessions, Sessions with key event, and Session key-event rate together so that a high percentage is not viewed without its supporting counts.

The four synthetic dates demonstrate chart behavior. They do not establish a durable trend, explain why channels differ, or justify a spending change.

See the two chart roles

A schematic dashboard with a daily line chart beside a three-row channel comparison table.

The line chart organizes inquiry-session volume by date; the table places each channel's volume and rate side by side.

Configure both supporting views

Build the time series

Builder route: Add a Time series chart to your report. In Setup, choose Date as the dimension and Sessions with key event as the metric. Sort by Date in ascending chronological order. Set the chart title exactly to Sessions with key event by date.

Observation-only route: Record that same configuration in your dashboard specification. Use the preview on this screen to interpret the expected chart; do not claim that you created or tested a live chart.

A line can help the marketing lead locate a change in recorded inquiry-session volume. It does not identify the cause of that change.

Build the channel comparison

Builder route: Add a Table chart. Choose Channel as its dimension and add all three metrics: Sessions, Sessions with key event, and Session key-event rate. Initially sort by Sessions in descending order. Set the chart title exactly to Channel comparison.

Observation-only route: Record this table configuration and title in your dashboard specification. The figures below are an expected full-period preview, not evidence from a live report.

Keep the supporting counts beside the rate. Do not rank channels by percentage alone.

Supporting-view configuration

Use these configurations for the initial full practice-data view. Date-control configuration and full dashboard validation come next.

Initial configuration for the two supporting views
ViewDimensionMetricsInitial sort
Time seriesDateSessions with key eventDate ascending
Channel comparisonChannelSessions; Sessions with key event; Session key-event rateSessions descending

Expected full-period preview

These values summarize all four synthetic dates. Builders can compare them with their charts as an informal setup check. Observation-only learners should treat them as the expected textual preview and mark live behavior as not tested.

Expected values when the complete synthetic practice dataset is displayed
ViewDate or channelSessions with key eventOther displayed measures
Time series2025-06-0118—
Time series2025-06-0223—
Time series2025-06-0322—
Time series2025-06-0417—
Channel comparisonOrganic Search40500 Sessions; 8.0%
Channel comparisonOrganic Social20400 Sessions; 5.0%
Channel comparisonEmail20100 Sessions; 20.0%

Practice: connect setup to purpose

Check the chart roles

Match each chart statement to its correct question or configuration.

Tap an item and then its matching pair.

Apply the chart evidence

Apply the chart evidence

Write three short lines using your completed report or the expected preview from the previous screen.

  1. Match the trend chart to its question, then name its dimension and metric.
  2. Match the channel comparison to its question, then name its dimension and three metrics.
  3. Report one visible difference between two channels, supporting it with Sessions, Sessions with key event, and Session key-event rate for both channels.

Builder route: Describe what your report displays.

Observation-only route: Describe the expected preview and state that live chart behavior was not tested. Do not claim why the difference exists.

Write at least 180 characters (0/180).

Step 7 of 9

Test Dates, Totals, and Freshness

Configure the date control

Make one date control govern the dashboard

Add a date-range control to the dashboard and set its initial selection to 2025-06-01 through 2025-06-04. This is the selected reporting period: it determines which source rows are currently included.

For each intended scorecard, the time series, and the channel table, use Date as the date-range dimension and let the chart inherit the control. Do not leave a chart on a conflicting custom or fixed range. The channel table should still use Channel as its displayed dimension; Date governs its filtering.

Builder route: configure and inspect these settings in your report. Observation-only route: record this as the required configuration; do not claim that a live chart was tested.

How the reporting-period control should work

A date-range selector directs one selected period to scorecards, a line chart, and a channel comparison table.

The date control filters every intended chart through the Date field.

Tip

Keep coverage and selection distinct

Keep stable source context separate from the control. Display these labels exactly:

  • Synthetic practice data
  • Data covers: 2025-06-01 to 2025-06-04
  • Source last checked: YYYY-MM-DD

Replace the final placeholder with the date you actually checked the source rows. Coverage describes the dates available in the Sheet. The visible date control describes the period currently selected in the report; it may be narrower than the four-day coverage.

Check full-period totals

Validate the full reporting period

With the full four-day range selected, validate the scorecards and channel table against these benchmarks. Counts should display as whole numbers with English thousands separators, and the rate should display to one decimal place. The rate remains the ratio of summed counts, not an average of row or channel percentages.

Builder route: compare the displayed values with the benchmarks. Observation-only route: record these as the expected values for a correctly configured report and mark live display behavior as not tested.

Full-period scorecard benchmark

Expected scorecard values for the complete practice-data coverage.

Use these values when the control covers 2025-06-01 through 2025-06-04.
MetricExpected valueCheck
Sessions1,000Sum of all session rows
Sessions with key event80Sum of all key-event session rows
Session key-event rate8.0%80 / 1,000

Channel comparison benchmark

Expected totals by channel for the same full reporting period.

Compare both supporting counts and the rate.
ChannelSessionsSessions with key eventSession key-event rate
Organic Search500408.0%
Email1002020.0%
Organic Social400205.0%

Test a filtered period and investigate safely

Run a shorter-range test

Now change the control to 2025-06-03 through 2025-06-04. The scorecards, time series, and channel table should all respond. The expected overall values are 550 Sessions, 39 Sessions with key event, and a 7.1% Session key-event rate.

Builder route: test the range in your report, then restore 2025-06-01 through 2025-06-04. Observation-only route: record the filtered values and the expected behavior that all intended charts respond; mark live behavior as not tested. Record the full four-day range as the intended restored selection.

Use mismatches as investigation signals

Start with the symptom you observe rather than changing several settings at once.

A mismatch calls for a source or configuration check; it does not prove a performance change.
Observed issueFirst check
Totals are too highLook for duplicate Date + Channel rows in the Sheet.
A count does not sumCheck source entry and that the count field uses Sum.
A chart ignores the controlCheck its Date range dimension and remove a conflicting fixed range.
Dates appear as categories or textCheck that Date is stored and detected as a date field.
No rows for a selectionConfirm whether rows exist in that range; do not treat an empty result as 0% performance.

Tip

Record freshness accurately

The source covers only 2025-06-01 through 2025-06-04 because those are the dates entered in the Sheet. A manual Sheet update can add or change rows. A connector refresh can retrieve changes already present in that connected Sheet, but it cannot create dates that are absent from it.

Record the actual date you last checked the source. That freshness note is different from both source coverage and a viewer's selected reporting period.

Document the validation

Report your validation result

Use the 2025-06-03 through 2025-06-04 test period. Write three short lines:

  1. Calculate the expected Sessions, Sessions with key event, and Session key-event rate.
  2. Builder route: state whether the scorecards, time series, and channel table matched or responded as expected. Observation-only route: state that live behavior was not tested and describe the expected behavior.
  3. Suppose the channel table ignores the date control. Name the most appropriate first troubleshooting check.

Write at least 80 characters (0/80).

Step 8 of 9

Share Without Exposing the Source

Choose a restricted sharing setup and understand how report permission differs from access to the underlying source.

Separate the report from its source

Two access layers

Sharing has two separate layers.

Report permission determines who can open or edit Northstar Studio - Acquisition Review.

Source permission determines who can directly open the Google Sheet Northstar Studio - Dashboard Practice and its Daily channels worksheet.

Giving someone report viewer access does not automatically give them access to the Sheet. Likewise, someone with Sheet access does not automatically get access to the report.

Report access is not source access

A schematic diagram shows a spreadsheet, data source, dashboard, viewer, and editor as separate access paths.

Treat access to the report and direct access to the Sheet as two settings to review separately.

Match credentials to the review need

Credential behavior

A data source can use different credential behavior, depending on the options available in your account or organization.

With owner's credentials, authorized report viewers can see source-backed report results without needing direct access to the Google Sheet. They still need permission to open the report.

With viewer's credentials, each viewer must have their own permission to access the underlying Sheet. A viewer who lacks that source permission may not see the report data.

Check the data source settings rather than assuming a mode is available: organization policy can limit credential and sharing choices.

Practical comparison

Choose a setting based on what the reviewer needs to do, not only on whether the Sheet is private.

Available labels and options can vary by account policy.
NeedReport permissionCredential behaviorDirect Sheet access
Review dashboard onlyNamed viewerOwner's credentials, if availableNot required for report results
Review dashboard and inspect rowsNamed viewerEither available modeRequired
Change charts or layoutNamed editorDepends on source setupOnly if needed for the task

Review the sharing boundary

Use a restricted review setup

For a focused review, share the report only with named recipients and assign Viewer access when they do not need to change charts, controls, or layout. Avoid broad link sharing merely because the practice Sheet is private.

Before sharing, inspect the report as well as the source: confirm that the data is synthetic, that no personal or confidential information appears in chart labels or notes, and that the intended credential behavior is understood.

Warning

Check before you share

A private Sheet does not by itself make a broadly shared report safe. Under owner's credentials, authorized report viewers may be able to see results derived from that Sheet even when they cannot open it directly. Review both sharing settings before inviting anyone.

Apply the access decision

Choose the sharing setup

A marketing lead is a named reviewer of Northstar Studio - Acquisition Review. They need to inspect the dashboard but must not edit it and do not need to open the underlying Google Sheet. Which setup is most appropriate, assuming the option is available?

Step 9 of 9

Present One Finding and One Next Check

Present a validated dashboard finding carefully, with an appropriate next check, limitations, and sharing boundary.

Check the dashboard before interpreting it

Final readiness pass

Before presenting a result, make one final readiness pass. Your dashboard should answer the marketing lead’s question: “Which acquisition channel deserves the next inquiry-performance check?”

Confirm that the one-page view includes Sessions, Sessions with key event, and Session key-event rate; a date trend; and a channel comparison. Check that the date control changes every intended chart, the visible period is clear, and the displayed values agree with the source rows.

Keep context visible: “Synthetic practice data,” “Data covers: 2025-06-01 to 2025-06-04,” and “Source last checked: [your actual checking date].” Coverage describes what exists in the source; it is not necessarily the selected reporting period.

Summary

Readiness checklist

  • Business question is visible and decision-focused.
  • All three metrics use validated totals and formats.
  • Trend and Channel comparison support the scorecards.
  • Date control changes each intended chart without a conflicting fixed range.
  • Selected reporting period is visible; source coverage and last-checked date are separate.
  • Report values agree with the sheet or other accessible source.
  • Sharing is restricted to the intended named viewers, or the report remains private.

Build a cautious decision note

Turn validated numbers into a careful note

Write a short decision note in four parts:

  1. State the selected period.
  2. State one observation with supporting counts and rate.
  3. Name a limitation that prevents a stronger claim.
  4. Propose one proportionate next check, then state the intended sharing boundary.

A chart can show a recorded difference. It cannot, by itself, explain why the difference occurred or prove that a channel is superior. With this four-day synthetic dataset, use the result to prioritize an inquiry-performance check—not to declare a cause, change spending, or predict durable performance.

The anatomy of a decision note

Four connected visual cards represent period, evidence, limitation, and next check, with a lock for restricted sharing.

Use evidence and caution together: period → validated observation → limitation → next check → sharing boundary.

Example

Model: evidence is not an explanation

Example using the full practice period:

“During 2025-06-01 to 2025-06-04, Email recorded 20 sessions with key event from 100 sessions, a 20.0% Session key-event rate. This is the highest recorded rate in this synthetic four-day dataset, so Email is a sensible channel for the next inquiry-performance check. The data do not establish a cause, real channel superiority, or the effect of a change. Next, check the Email source rows and available channel detail for measurement quality and context. Keep the report private or share it only with named viewers; review source access separately.”

The claim stays within the evidence: it identifies where to look next, rather than claiming why the result happened.

Apply the evidence and boundaries

Your final decision note

Write your own short decision note for Northstar Studio. Include: the selected reporting period; one validated finding with counts and a rate; one limitation; one next inquiry-performance check; and the intended restriction for sharing the report.

Use only what your dashboard and source support. Do not claim a cause or recommend a spending change.

Write at least 250 characters (0/250).

Completion

Tutorial complete

Congratulations! You completed: Build a Decision-Focused Looker Studio Dashboard

You completed a decision-focused Looker Studio dashboard workflow. With account access, you have a validated private dashboard ready for restricted sharing. Without access, you have a completed dashboard specification, validation record, and evidence-based decision note.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate