Data Studio Google Ads Reporting: 2026 Field Fixes

If your Google Ads reports started throwing field errors in May 2026 and the product itself suddenly had a different name, nothing broke on your side. Data Studio Google Ads reporting changed twice this spring: Google renamed Looker Studio back to Data Studio, and it switched off a group of fields in the Google Ads connector. Dashboards that had run untouched for years quietly stopped rendering parts of themselves — a tile shows a configuration error, and nobody notices until the monthly review.

This guide covers the cleanup: what actually changed, which fields to swap and for what, which new metrics the connector now exposes (including gross profit and margin), where the line sits between the native connector and a BigQuery export, and how to build a dashboard whose numbers survive a client question.

What happened: Looker Studio is Data Studio again

On April 16, 2026 Google announced the rebrand: the product renamed from Data Studio to Looker Studio back in 2022 has returned to its original name. The home page was reworked at the same time, giving unified access to reports, data sources, BigQuery conversational agents and Colab data apps.

What matters operationally is that the rebrand broke nothing by itself. Existing reports, templates, shared links and connectors keep working. What changes is:

the product name in the UI and documentation — searching help for “Looker Studio” will increasingly land you on Data Studio pages;
home screen navigation, where data sources and reports now sit alongside BigQuery agents;
your own internal wording — if your onboarding docs, SOWs and client decks say “Looker Studio dashboard,” update them once now instead of confusing a new hire in six months.

One distinction worth keeping straight: Looker is a separate Google Cloud enterprise product with a semantic layer and LookML, and it still exists. Data Studio is the free reporting builder discussed here. The rebrand exists precisely to end the naming confusion that started in 2022.

Location fields are gone: what actually broke

The rename is cosmetic. The second change is not. On April 30, 2026 Google announced the deprecation of location extension fields in the Google Ads and New Search Ads 360 connectors, and they stopped working on May 4, 2026. This covers affiliate location and store location fields.

The failure mode is sneaky. The report does not go down as a whole — only the specific tile using a removed field returns a configuration error while every other page keeps serving data. If your dashboard has five pages and locations lived on page four, this can sit unnoticed for weeks.

The 15-minute fix

Open the report → Edit → in the resource panel choose Manage added data sources.
Open the Google Ads source → Edit → sort the field list and locate the fields flagged as deprecated.
Swap them for the corresponding Asset location fields — same meaning, expressed in the newer model where extensions have long been called assets.
Return to the report and walk every tile that used the old field. Replacements do not propagate into breakdowns, filters or calculated fields automatically.
Check calculated fields separately. A formula referencing a removed field still exists and breaks the tile a second time, after you thought you were done.

Even if you never report on locations, spend the five minutes anyway. Deprecated fields tend to hide inside forgotten filters inherited from whatever template the dashboard was originally copied from.

A habit that saves afternoons: once a quarter, open every live dashboard in edit mode and review the source field list. Google announces deprecations in advance, but nobody sends the notice to your team specifically.

What the Google Ads connector can do in 2026

The metric set has expanded meaningfully, and part of it removes the reason people used to build exports. Available now, among others:

Conversions by conversion date and conversion value by conversion date, plus the equivalents for all conversions;
New vs. returning customers — the segmentation Google now labels on its own side;
Gross profit and gross profit margin, provided you pass cost of goods in your product data;
Platform-comparable conversions, conversion value, conversion value/cost and cost/conversion.

Click date vs. conversion date: why your numbers disagree

This breaks more reports than any technical bug. By default Google Ads attributes a conversion to the date of the click, not the date the order was placed. A click on September 1 and a purchase on September 9 both land on September 1 — which means yesterday’s report changes retroactively.

Two practical consequences:

a dashboard people check daily must run on click date, otherwise your bid and budget decisions are based on numbers the algorithm is not optimising against. How long conversions take to mature, and why yesterday’s ROAS is always understated, is covered in our piece on conversion windows and conversion lag in Google Ads;
a finance-facing report that gets reconciled against accounting must run on conversion date, or “September sales” will never match between the ad account and the books.

The clean solution is to show both, side by side, labelled explicitly: “by click date (for optimisation)” and “by conversion date (for reconciliation).” That single layout change removes most of the questions before the call starts.

Data Studio Google Ads reporting: three tiers and where to stop

Not every account needs a warehouse. Pick the tier by volume and by how many sources you need to join.

Tier	Tooling	Fits when	Breaks when
1	In-platform: custom columns and Report Editor	One account, daily operations, up to 20–30 campaigns	No history outside the report window, no CRM join
2	Data Studio + native Google Ads connector	A handful of accounts, client reporting, straightforward summaries	API quotas, heavy blends, slow pages on large date ranges
3	Data Studio on top of BigQuery	Many accounts, long history, CRM and COGS joins	Needs transfer setup and basic SQL literacy

Tier one is routinely underrated: half of what people build dashboards for can be done inside the interface, as covered in our guide to custom columns and the Report Editor in Google Ads. When pages start crawling and you keep running out of history, that is the signal to move up, and the walkthrough for exporting Google Ads to BigQuery is the next step.

A 40-minute dashboard build

The structure below serves both daily operations and the client conversation. Build once, clone per account.

Step 1. The data source

Create a new data source on the Google Ads connector. One decision matters here: connecting a manager account (MCC) aggregates metrics across every child account and converts them into the manager’s currency. For a single-client report, connect the specific account. For a portfolio view, connect the MCC — and label the currency directly on the page.

Step 2. The Overview page

Scorecard row: cost, conversions, conversion value, ROAS, CPA, impression share.
Period-over-period comparison on every scorecard. Without it, a number means nothing.
Trend chart: cost and conversions on dual axes, weekly granularity. Daily granularity across a long range is noise wearing a chart’s clothing.

Step 3. The Campaigns page

A table broken down by campaign type and campaign: cost, conversions, CPA, value/cost, impression share plus lost IS to budget and to rank. Add conditional heat formatting on CPA — your eye finds the problem campaign in two seconds instead of four sorts.

Step 4. The Assets and Queries page

Search terms, ad assets and product groups live here. The asset view overlaps conceptually with what Ad Strength shows in-platform, but Data Studio makes it far easier to compare several campaigns at once. What to actually change based on that report is covered in Ad Strength and RSA asset reporting.

Step 5. The Economics page

The most valuable page and the one almost nobody builds. Gross profit and margin (when COGS is passed), new vs. returning customers, conversions by conversion date. This is where you see that the campaign with the best ROAS can make less money than the campaign with mediocre ROAS and a high-margin mix. The logic for turning margin into an allowable cost per click sits in our piece on media buying unit economics.

Step 6. Controls and polish

Default date range: last 30 days with automatic previous-period comparison.
Filters: campaign type, campaign, device. Past three filters per page, people stop using them.
A footnote on every page: data source, time zone, currency, last refresh.

Data freshness, caching and quotas

The second-most common complaint after “the numbers disagree” is “the report didn’t refresh.” Usually three mechanisms are at play, none of them a bug.

Report caching. Data Studio stores query results and refreshes them on a schedule rather than on every page load. If you just changed bids and want to see the effect, trigger a manual data refresh — otherwise you are reading a cached answer. Refresh frequency is configurable per source; every 4–12 hours is a reasonable starting point for client dashboards, more often for operational ones.

Google Ads data lag. Cost and clicks land quickly; conversions arrive late, and some metrics — invalid click adjustments among them — get restated over several days. Any report comparing “today” against “the same day last week” will understate today. Rule of thumb: make decisions on the last completed day, not the current one.

API quotas. Every tile with its own query consumes quota. A 40-tile report with many different breakdowns can hit limits and fail selectively — loading fine today, erroring tomorrow. The fix is aggregation: fewer tiles, more dimensions inside a single table, and heavy computation pushed into the warehouse.

Five mistakes that destroy trust in a dashboard

Mismatched time zones. The ad account, GA4 and the CRM can all sit in different zones. A 3–7% daily discrepancy is almost always this, not “broken tracking.”
Currency mixing in an MCC. A manager-level roll-up converts into the manager’s currency at Google’s rate. It will never match the client’s invoices to the cent — that is fine, but it has to be labelled.
Double-counted conversions. If one action fires two conversion goals, the dashboard doubles your results faithfully and silently. How to find those pairs is in our breakdown of duplicate conversions in Google Ads.
Blending without a real key. Joining tables on “campaign name” collapses the moment a name differs by one space. Join on an ID, not on a human-readable label.
Comparing unequal periods. “Last 30 days” vs. “previous 30 days” compares four weekends against five whenever the window does not start on a Monday. Pin week boundaries for weekly reporting.

Handling multiple accounts

Past five accounts the native connector starts working against you: one data source per account, and every change repeated by hand. Two approaches scale.

Approach A — via the MCC. Connect the manager account as a single source and expose an account filter as a page control. Fast, but you are limited to aggregate metrics in the manager’s currency. The structural side of this — hierarchy, labels, cross-account conversions — is covered in our guide to media buyer dashboards and reporting.

Approach B — via BigQuery. The transfer service lands every account in one schema, you write a view with your own logic, and Data Studio connects to a single source. More setup up front, but adding an account becomes one config line instead of a new dashboard.

For teams running several ad accounts in parallel, approach B usually pays for itself by month three, purely in hours not spent assembling reports. If your accounts come through agency access, confirm in advance that the access level permits API and transfer connections — some agency account providers restrict exactly that. Agency Google Ads accounts from PPC Rebels come with full access, so reporting is built with native tooling rather than manual CSV exports.

Pre-delivery checklist

Every tile renders; none shows a configuration error.
Location fields replaced with Asset location; calculated fields rebuilt.
Currency, time zone and date model (click vs. conversion) labelled on every page.
Period-over-period comparison present, not bare absolute numbers.
Access shared as View, not Edit.
Email delivery scheduled for a day when data has settled, not Monday morning on Sunday’s numbers.
A contact in the footer for whoever will question a figure.

FAQ: Data Studio and Google Ads reporting

Are Data Studio and Looker Studio the same product?

Yes. On April 16, 2026 Google renamed Looker Studio back to Data Studio. Same tool, same reports, same connectors. Looker is a different Google Cloud product and is unaffected by the rename.

Will my existing report links stop working?

No. The rebrand does not touch existing reports, data sources or granted access. What changes is the product name and the home page layout.

Why does my location tile show a configuration error?

Location extension fields (affiliate location, store location) were deprecated in the Google Ads and New Search Ads 360 connectors effective May 4, 2026. Replace them with the Asset location fields and rebuild any calculated fields that referenced them.

Why don’t Data Studio numbers match the Google Ads interface?

Three usual suspects: a different time zone on the data source, a different date model (click date vs. conversion date), and a different data window — conversions keep backfilling for days after the click.

How do I report on profit instead of just ROAS?

The connector exposes gross profit and gross profit margin, which work when cost of goods is passed in your product data. Without COGS you can only approximate profit with a calculated field using an average margin — an estimate, not a fact, and it should be labelled as such.

Native connector or BigQuery?

Up to three to five accounts with no CRM join, the native connector is enough. Once you need long history, revenue joined from a CRM, or reporting across dozens of accounts, a BigQuery export with one source on top is faster and cheaper in team hours.

How much data can the native connector handle?

There is no hard row limit, but large ranges and complex blends slow reports down and push against API quotas. Practical benchmark: if a page takes more than 10–15 seconds to load, move aggregation into BigQuery.

Why is my report showing yesterday’s data after I refreshed the page?

Caching. Data Studio serves stored query results until the configured refresh interval elapses. Trigger a manual data refresh, and set the interval explicitly on the source for recurring reports.

How many tiles should one page have?

No technical limit, but each tile is a separate API query. Ten to twelve elements per page is a workable benchmark; beyond that, load times grow and quota errors start appearing intermittently.

How do I schedule automatic delivery to a client?

In the report: Share → Schedule delivery. Pick a day when the data has settled, and always state the reporting period in the email body — otherwise the recipient compares it against a different window and comes back with questions.

Should clients get edit access?

No. View access covers reading and exporting. Edit access reliably ends in an accidentally broken tile and an evening spent restoring it.

Should one dashboard cover every channel?

Yes, but not by blending on the fly. Join channels in the warehouse where you control a single campaign dictionary and a single key. In-report blends on campaign names break on the first renamed campaign.

The takeaway: a dashboard is trusted exactly as far as it is legible. A labelled currency, time zone and date model buy more credibility than ten additional charts.

Data Studio for Google Ads Reporting in 2026: The Rename, the Dead Fields and a Dashboard You Can Trust

What happened: Looker Studio is Data Studio again