Looker Studio: Marketing Dashboards Without the Spreadsheet Grind

Free native connectors, paid partner connectors, one self-refreshing report link.

Most monthly marketing reports in India are still built the same way: export GA4 to a sheet, export Google Ads to another, paste both into a slide, repeat next month.

Looker Studio exists to end that. Connect the sources once, design the page once, and the numbers refresh themselves.

It sits in the "Report" layer of our marketing analytics guide — the layer that turns five tool logins into one page someone will actually read. This post goes deeper than the guide: connectors, report anatomy, the quota problem, the Pro tier, a build procedure and the mistakes that make a report confidently wrong.

What is Looker Studio, and why is it called Data Studio again?

Looker Studio is a free, browser-based tool for turning data from Google products (and others) into charts, tables and scorecards on a shareable page. The standard version costs nothing; a paid tier exists for larger teams.

The name has moved twice. Google renamed Data Studio to Looker Studio on 11 October 2022 to fold it into the Looker family (2022 release notes). Then in April 2026 it went back: "We've rebranded Looker Studio as Data Studio," says the 16 April 2026 release note, and the Google Cloud announcement confirms that "Data Studio continues to offer powerful, no-cost individual analysis and visualization" and that existing reports and data sources carry over with no action needed.

So in 2026: Google Data Studio, Looker Studio and Data Studio are the same product. We use "Looker Studio" through this post because that is what most people still search and say; the interface now says Data Studio.

Which connectors are free, and which are paid?

A connector is the bridge between a platform's data and your report. Google builds the ones for its own products and they are free; everything else comes through partner connectors, which Google's documentation says "may cost money to use" (About data sources).

This matters for an Indian SMB because the two platforms most of them advertise on split exactly along that line: Google Ads is native and free; Meta Ads is not.

The workaround most small teams use for Meta: a monthly CSV export into a Google Sheet, connected for free. Less elegant, entirely workable for one account.

The Search Console connector has a quirk worth knowing: each data source is either Site Impression (site-wide totals) or URL Impression (page-level, and the only one that includes Discover); Google's connector documentation notes a single data source can only use one, so an SEO page usually needs both. Setup and verification for the property itself is in our Google Search Console guide.

How is a Looker Studio report put together?

Every report is five things stacked on top of each other. Understand the stack and the tool stops feeling like magic.

• Data sources. One connection to one platform account, with its fields and their types. A GA4 property, a Search Console site, a Sheet tab. Reusable across reports.
• Blends. Two or more data sources joined on a shared dimension, such as date or campaign name. Google's docs state "a blend can have up to five tables" and support inner, left, right, full-outer and cross joins (How blends work). This is how "Google Ads cost ÷ GA4 leads" becomes one number.
• Calculated fields. Formulas on top of fields — cost per lead, a CASE statement that groups 40 campaign names into four service lines, a REGEXP that cleans landing-page URLs.
• Date-range control. One picker at the top that every chart obeys. Set the default to "last month" and a comparison to "previous period" and the report reads itself.
• Filter controls. Drop-downs for campaign, city or device so the client can slice without asking you.

A worked example. A Pune coaching institute runs Google Ads for its CAT batches and counts a lead as a form submit, a WhatsApp click or a phone-call click. Their GA4 data source supplies key events by landing page; the Google Ads source supplies cost by campaign. Blend the two on campaign name, add a calculated field cost ÷ key events, and you have cost per lead by batch without opening either platform. GA4 setup and how to mark those key events is covered in our GA4 guide.

Why does the GA4 connector break, and how do you fix it?

Because every chart is a live API request. Google's connector documentation is explicit: reports connected to GA4 "are subject to Google Analytics Data API (GA4) quotas" and "may display an error message" when they exceed them (Connect to Google Analytics).

The numbers behind that: a standard GA4 property gets 200,000 core tokens per day, 40,000 per hour and 10 concurrent requests, per the Data API quota page. A 30-chart report opened by six people, each dragging the date picker around, burns through the hourly pot fast. The error reads "This property has issued too many requests in the last hour" and the charts go blank until it resets.

Google's own troubleshooting guide lists the fixes. In the order we would try them:

• Fewer charts. The simplest fix and the one nobody wants to hear. Ten scorecards cost less than forty.
• Owner's credentials. Set the data source to use your credentials rather than each viewer's, so viewers hit cached data instead of fresh queries.
• One GA4 data source, reused. Five copies of the same connection defeat caching; one shared source improves it.
• Extract Data. Google's free Extract Data connector takes a snapshot of the fields you need and serves the report from that. The limits are "up to 100 MB of data" and "up to 750,000 rows," with an auto-update schedule to refresh it (Extract data for faster performance). One scheduled pull a day replaces hundreds of live ones.
• Sheets as a middle layer. Google's GA4 Reports Builder add-on writes GA4 data into a Sheet on a schedule; the report then reads the Sheet, which has no GA4 quota at all. Good for one property and a fixed set of metrics.
• BigQuery as the middle layer. GA4's built-in BigQuery export lands raw events in a warehouse; the report queries that instead of the GA4 API. The right answer for agencies and any brand whose report has outgrown Sheets — our BigQuery for marketers post walks through the export.

Google also lists Analytics 360 and partner connectors as options. Both are paid; for an SMB report, the four free fixes above are almost always enough.

What does Looker Studio Pro add?

Not better charts. According to Google's Data Studio Pro documentation, the paid tier makes reports belong to your organisation rather than an individual, adds team workspaces with role-based permissions, raises scheduled deliveries to up to 200 per report with Google Chat delivery and alerts, adds personal report links, the Looker mobile app, Google Cloud support, and Gemini features such as asking questions of your data and writing calculated fields in plain language. Paid plans exist; if your problem is "the report lives in an ex-employee's Gmail," Pro solves it. If your problem is "the report is wrong," it does not.

How do you build a one-page marketing report for an Indian SMB?

Page one holds ten numbers and nothing else. Everything a curious reader might want lives on page two and beyond.

Two boundaries first, so this post stays in its lane. Which KPIs deserve those ten slots — and why leads beat sessions — is the job of our marketing dashboard post and the definitions in our marketing KPIs guide. What belongs in an SEO-specific report is owned by our SEO reporting post. This is the build.

1. Write the ten numbers on paper before opening the tool. For the coaching institute: total ad spend, leads (GA4 key events), cost per lead, Google Ads conversions as Google reports them, Meta leads as Meta reports them, organic clicks from Search Console, sessions by channel, top five landing pages by leads, a weekly lead trend, and month-on-month change on spend and leads.
2. Create the data sources once, at the account level. GA4 property, Search Console (URL Impression), Google Ads account, and one Google Sheet tab with the Meta export and the monthly targets. Set each to owner's credentials.
3. Add the date-range control and a comparison. Default "last month," compare to "previous period." Every scorecard now shows the number and the change.
4. Lay out the top row: five scorecards. Spend, leads, cost per lead, organic clicks, Meta leads. Cost per lead is a blend of Ads cost and GA4 key events on date, with a calculated field SUM(cost) / SUM(key events).
5. Second row: two charts and a table. A bar of sessions by default channel group, a line of leads by week, and a five-row table of landing pages sorted by key events.
6. Third row: platform truth, side by side. Google Ads conversions from the Ads source and Meta results from the Sheet, labelled "as reported by the platform." They will not match GA4, and the label says so.
7. Add filter controls for campaign and city. Two drop-downs at the top. The client slices; you stop getting Monday-morning "can you pull Mumbai only?" messages.
8. Build page two for the detail. Full campaign table, Search Console queries, device split. Anything that does not change a decision goes here or nowhere.
9. Test the quota. Open the report, change the date range five times, filter twice. If any chart errors, move GA4 to Extract Data before you share it.
10. Share as viewer, schedule the PDF, then leave it alone. The monthly job becomes writing three paragraphs of commentary, not assembling numbers.

How do you share and schedule a report?

Sharing works like Google Docs: a link with viewer or editor access, restricted or open. Give clients viewer access and keep the editor list short; an edited chart is a changed number nobody can explain later.

Scheduling emails the report as a PDF with a preview of page one and a link to the live version, on a daily, weekly, monthly or custom cadence. On the free version Google's scheduling documentation allows one schedule per report at most once a day; Pro raises that to 200 schedules and hourly delivery, plus Chat and Slack. The PDF is a snapshot at the report's default date range — set that default to "last month" or the client gets yesterday's numbers on the first of the month.

Templates are worth a mention because "looker studio templates" is its own search. Google's gallery and most partner-connector vendors offer free ones. Use them to learn layout, then rebuild on your own data sources — a template wired to someone else's field names is a week of debugging you did not need.

What mistakes make Looker Studio reports wrong?

The tool is easy. The mistakes are in what you connect and what you compare.

• Forty charts on page one. A report that shows everything shows nothing, and it is the surest way to hit the GA4 quota. Ten numbers; the rest on page two.
• Blending on the wrong key. Join Google Ads to GA4 on campaign name and one renamed campaign silently drops its cost from the blend, so cost per lead looks better than it is. Join on date for totals; join on a stable ID, or a Sheet that maps names, for campaign-level views.
• Treating GA4 conversions and Ads conversions as the same number. Google Ads counts a conversion on click date with its own attribution and lookback; GA4 counts a key event on the day it happened, across channels. They are two answers to two questions. Show both, label both, never subtract one from the other.
• Summing metrics that cannot be summed. Average position, CTR and conversion rate must be recalculated from their parts, not averaged across rows. A calculated field fixes it; a "Sum" aggregation setting quietly breaks it.
• A stale middle layer. A Sheet or extract nobody scheduled shows March numbers in May. Turn on auto-update and put the "data last refreshed" field on page one.
• Viewer credentials by default. Every client login becomes a fresh GA4 query. Owner's credentials, unless the report genuinely needs per-user data access.
• No UTM discipline upstream. If Meta traffic lands in GA4 as "(direct)," no blend will rescue it. The tagging convention comes before the dashboard.

Where to go from here

If you have never built one: connect GA4 and Search Console today, put five scorecards on a page, and share the link. That alone replaces most monthly exports.

If you already have one and it errors, breaks or nobody reads it: cut it to ten numbers, switch to owner's credentials, and move GA4 behind Extract Data or a Sheet.

And if the report is fine but the inputs are not — key events firing twice, Ads and GA4 disagreeing by 3×, WhatsApp clicks untracked — the fix is upstream. We set up tracking and the reporting layer as part of every performance marketing engagement (management fees in India typically run ₹25,000–₹1,00,000 a month, always excluding ad spend), because a dashboard on bad data is a beautifully formatted wrong answer.