Google Data Studio reporting services: from scattered data to a single dashboard that carries the decision.

We wrote this guide for marketing and management teams who pull GA4, Google Ads and Search Console data from separate screens every week, and spend their meetings arguing about whether the data is right because the numbers don’t match. We describe Google Data Studio’s connectors, the logic of blending and calculated fields, credentials, GA4 quotas and scheduled delivery based on Google’s official documentation and two renaming announcements on the Google Cloud blog. We verified product names, limits and figures against the source as of September 2026; the sources are listed by number at the bottom of the page. Our field observations are marked separately under the heading “Expert note”.

Our Data Studio (Looker Studio) reporting services run in three layers: connecting sources with the right credentials, freshness and quota settings; designing the dashboard backwards from the KPI (key performance indicator) definition; and managing ownership in your company’s account. We keep markention.com’s own reporting dashboards in Data Studio under the same rules; the examples on this page are illustrative. We cover the event and key event setup that feeds the dashboard separately on our Google Analytics 4 page.

Looker Studio, now Data Studio again: is it the same product?

Google Data Studio is a free Google tool that pulls data from different sources through connectors and turns it into shareable, interactive dashboards and reports; Looker Studio is the name the same product carried between 2022 and 2026. On October 11, 2022, Google brought its business intelligence products together under the Looker umbrella and renamed Data Studio as Looker Studio; the product stayed free, and Looker Studio Pro was added alongside it, bringing enterprise management, team collaboration and a service level agreement (SLA).² Then on April 11, 2026, Google Cloud announced that it was renaming the product Data Studio again, and that existing reports, data sources and users would move to the new experience without any action needed.¹ The product’s address also became datastudio.google.com; old lookerstudio.google.com links redirect to the new address automatically.¹⁴

That’s why the same product goes by both Data Studio and Looker Studio today. In Google’s 2026 positioning, Data Studio is for personal data exploration and quickly built one-off (ad hoc) reports, while Looker is kept separate as an enterprise business intelligence platform that serves governed data through a central semantic model.¹ The free version is for individual analysis and visualization; the licensed Data Studio Pro adds AI features, enterprise security, management and compliance.¹

Which data sources can you connect, and what does a connector bring in?

The sources we connect to Data Studio most often are GA4, Google Ads, Search Console, BigQuery and Google Sheets; each becomes a data source through a connector, and every connector has its own limits. The GA4 connector requires at least “Read & Analyze” permission on the property it connects to, and can bring every field in the Google Analytics Data API into the dashboard, including fields defined specifically for the property;³ this permission’s current name in GA4 is the Viewer role.¹³ Google writes that data from this connector will match the reports in Analytics but not explorations, and that GA4 segments and comparisons can’t be used in the connector.³

In the Search Console connector, the display type is chosen up front: Search Console aggregates search performance in two different ways, by site and by URL, and a data source can use only one of them.⁶ To see both side by side, we create two data sources and add them to the same report. Queries made only a few times, or that contain personal or sensitive information, may not be shown for privacy reasons; Data Studio may group these into a single row with an empty value.⁶

We set up each source once, then name and describe its fields so they can be reused across reports. Creating a separate source per report for the same property scatters definitions and splits the cache.

Why can GA4 quotas stop a dashboard?

Every Data Studio report connected to GA4 uses up Google Analytics Data API quotas; when a quota is exceeded, charts may show an error message instead of data.³ Quota is measured in tokens and applied per property: a standard GA4 property has limits of 200,000 core tokens per day and 40,000 per hour, 14,000 tokens per hour for the same project and property pair, and at most 10 concurrent requests; these limits are higher on Analytics 360 properties.⁴ Daily quotas reset at midnight Pacific time.⁴

A request’s token cost becomes clear only when the request runs; the number of rows, dimensions and metrics, filter complexity, the date range, high-cardinality dimensions such as page path, and the property’s event volume all increase the cost.⁴ While editing a report in Data Studio, you can right-click the report or a chart and open the “Google Analytics token usage” panel to see how much each chart uses and whether the data came from cache.⁵ The main routes Google recommends when a quota is exceeded are:⁵

• Owner’s credentials: viewers share the same cached data; a view served from cache doesn’t use new tokens.
• A single data source: duplicate GA4 sources are combined into a single reusable source.
• Fewer charts and less traffic: charts on pages are reduced; reports embedded in high-traffic pages are removed.
• Data extraction: GA4 data is extracted into a static snapshot; if the quota has been exceeded, you wait up to 24 hours for it to reset before extracting.
• BigQuery: GA4 data is exported to BigQuery, and the report reads it through the BigQuery connector.

How do data freshness and the cache affect the numbers?

Data freshness determines how old a number on the dashboard can be at most: Data Studio keeps a query’s result in memory for that period, and if the same query comes in again, it can serve the data from memory without going to the source.⁷ The report gets faster, and cost and quota consumption go down; the price is that the number doesn’t reflect the latest state immediately. For Google marketing products such as Google Ads and Search Console, freshness is 12 hours and can’t be changed; the table in the same document lists options of 1, 4 and 12 hours for Google Analytics, a 15-minute default for Google Sheets, and options from minutes up to 12 hours for BigQuery.⁷

The type of credentials also changes freshness. In a source that uses the owner’s credentials, all viewers depend on a single freshness setting; with viewer’s credentials, each viewer’s freshness works separately, and one person’s query doesn’t refresh the data another sees.⁷ A blended source’s freshness is the shortest refresh period among the sources it contains.⁷

Dashboard design: which KPIs, in which layout?

A dashboard includes a small number of KPIs that serve a decision; the layout presents them with their definition, target and comparison period, reading from the general to the detailed, top to bottom. We start the design by writing down which question the dashboard will answer in which meeting; choosing charts comes after. We use the same skeleton on every page:

1. Top strip: a few KPI cards, each showing the value, the change from the previous period and the target.
2. Trend: a time series of the main indicator, with campaign and site changes as date annotations.
3. Breakdown: a table by channel, campaign, page or product, sorted according to the decision question.
4. Controls: date range, channel and device filters, with a fixed default view.

Indicator definitions are written outside the dashboard, in a KPI glossary: name, formula, source, date logic and owner. The dashboard is the visible face of that glossary. We don’t merge similarly named measures from different platforms into one card, for example the ad platform’s conversion and the analytics tool’s key event; we show them under separate names and note in the glossary which one is the decision metric.

How do you set up calculated fields and data blending?

A calculated field produces a new metric or dimension from fields in the data source using a formula; blending combines several data sources in a single chart through shared fields. A calculated field can be defined in the data source or in a single chart: a field in the data source works in every report that uses that source but can’t be used with blended data; a chart-specific field works in blended data but lives only in the chart where it’s defined, and can’t refer to another chart-specific field.⁹ Ratios are written in aggregated form, for example SUM(Profit) / SUM(Revenue); when the aggregation function is given explicitly in the formula, the field’s default aggregation becomes “Auto”, and the formula doesn’t break if someone changes the aggregation type.⁹

In Data Studio, a blend combines at most five data sources; the blend is embedded in the report where it was created, can’t be reused in another report, and has no freshness or credential settings of its own, inheriting them from the underlying sources.⁸ Inner, left outer, right outer, full outer and cross joins are supported as join types; the join condition can only be based on equality.⁸ Before the tables are joined, each table is grouped and aggregated by its own dimensions; if the selected dimensions don’t include an ID that distinguishes each record, identical rows collapse into one at this stage.⁸ When joining Google Ads cost to GA4 data by campaign name, we check that the names are written exactly the same on both sides and that the date is part of the join condition. In tables filtered with a calculated field in the GA4 connector, the summary row doesn’t show a total;³ an empty total doesn’t mean data loss.

Credentials: whose permission does the dashboard read data with?

A dashboard reads data with the permission of the credentials chosen for each data source; Data Studio has three types: owner’s credentials, viewer’s credentials and service account credentials.¹⁰ The choice determines who sees the data, how the quota is used, and whether the dashboard keeps working when someone leaves.

Owner’s credentials are practical for dashboards shared with managers, and also an advantage for GA4 quota, since viewers share the same cache.⁵ The price is that access depends on a single person’s permissions; that’s why we choose a permanent company user in your Workspace organization as the credential owner. For sources containing personal data or sensitive financial figures, we use viewer’s credentials and hide unnecessary fields.

Sharing and ownership: who keeps the reports?

In free Data Studio, reports and data sources stay in the account of the person who created them, while in Data Studio Pro they belong to the organization; ownership can be transferred to another Google account from the sharing dialog.¹² The transfer can’t be undone: once a new owner is assigned, the former owner can’t transfer ownership again, not even back to themselves.¹² When a data source is transferred, its credentials stay as they are; sources using the owner’s credentials keep supplying data to the report.¹² In Google Workspace and Cloud Identity organizations, ownership can be transferred only within the organization, and in individual accounts only to another individual account; data sources created by uploading a CSV can’t be transferred, and the new owner has to set them up again.¹²

In the free version, Data Studio assets belonging to a deleted user are permanently deleted after 20 days.¹² In Pro, Google recommends team workspaces so that content doesn’t become inaccessible when an employee leaves.¹²

That’s why we create reports and data sources in your company’s Google account or Workspace organization; the markention team works on them as editors. The GA4, Google Ads, Search Console and BigQuery accounts are also opened in your company’s name. When the work ends, the reports, the KPI glossary and the setup notes stay with you; we take irreversible steps such as transferring ownership only with your approval.

How does scheduled delivery work, and when do you need Pro?

Scheduled delivery emails selected pages of a report as a PDF attachment, with a link to the report, at a set interval; the free version allows one schedule per report, and Data Studio Pro is needed when you need several schedules or hourly delivery.¹¹ Filter and date control values can be changed for a specific schedule, but controls can’t be added to or removed from a schedule.¹¹ The difference between the two versions shows most in delivery:

What to look for in a reporting agency or dashboard specialist

Whether you call it Looker Studio or Data Studio, a dashboard is only worth the definitions behind it. Reporting needs are usually met in one of three ways:

When you talk to a reporting partner, ask these before you look at the dashboard itself:

1. Ownership: will the reports and data sources be created in your company’s account? In the free version, content belongs to whoever created it.
2. KPI glossary: will each metric’s formula, source and owner be handed over in writing?
3. Credentials: which sources use owner’s credentials, which use viewer’s credentials, and why?
4. Checking against the source: how are the dashboard’s numbers checked against the GA4, Google Ads and Search Console interfaces?
5. Maintenance: who updates the dashboard when sources or targets change?

What determines Data Studio reporting pricing?

The cost of reporting services depends less on the number of charts than on the state of the sources to connect and whether you want ongoing maintenance.

We work out the scope together in the first meeting, then send a written proposal. If Data Studio Pro is needed, the license is bought from your company’s account; BigQuery query costs also land in your Google Cloud account and are separate from our service fee.

Data Studio reporting pricing: estimated ranges

Estimated range, excluding VAT; rows marked “/ month” are monthly, the others are one-off. Scope is confirmed in a written proposal after the first meeting. As of October 2026.

How do our Data Studio reporting services work in the first 30 days?

In the first 30 days, we write down decisions and definitions, verify the data, and only at the end build the dashboard and read it together with you.

1. Week 1 · Decisions and access: the questions the dashboard will answer and the meeting rhythm are written down; access is checked in your company’s accounts.
2. Week 2 · Data audit and KPI glossary: event and conversion definitions are verified at the source; the formula, source and target for each indicator are written into the glossary.
3. Week 3 · Setup: data sources are connected with credential and freshness settings; calculated fields, blends and filters are set up, and numbers are compared with the source interfaces.
4. Week 4 · Handover: access and scheduled delivery are set up; the dashboard is read together in the first decision meeting, and gaps are noted.

A dashboard can’t be more accurate than the measurement on the site; we verify that events fire correctly on the site in the Google Tag Manager setup. If you’d like to read your current reports together, pick a meeting day that suits you below.