PPC PRITAM - Strategy, Tracking, Automation, Growth
Looker Studio Data Sources•8 min read•By PPC Pritam

Looker Studio Data Source Not Connecting: Common Causes and Fixes

When a Looker Studio data source will not connect, the report cannot pull data and every chart tied to that source breaks. The cause is usually authentication, account access, the connector itself or a change to the underlying resource. The fix depends on which of those failed, so confirm where the connection breaks before reconnecting everything.

Table of Contents

  • 01.What a connection actually depends on
  • 02.What to check first
  • 03.Authentication and reconnection
  • 04.Account access and the underlying resource
  • 05.Connector-specific behavior
  • 06.When to recreate the data source
  • 07.How to test the fix
  • 08.How to validate the final result

What a connection actually depends on

A data source connection is not a single link. It is an authenticated relationship between Looker Studio, a connector and an external account or resource. When it fails, one of those pieces broke. Authentication can expire, the connected account can lose access, the connector can change or the underlying resource can be deleted or moved. Each cause has a different fix.

Connection failure causes
CauseWhat happensWhere to check
Expired authToken no longer validReconnect the source credentials
Lost account accessConnected account removed from resourceAccount permissions on the source app
Connector changeConnector deprecated or updatedData source settings, connector gallery
Deleted resourceLinked sheet or view removedOpen the source resource directly
Wrong accountSigned into a different Google accountAccount switcher in Looker Studio

What to check first

Start here
  • Confirm you are signed into the Google account that owns or has access to the source.
  • Open the data source settings page and look for a reconnection or reauth prompt.
  • Open the underlying resource directly, such as the GA4 property or the Google Sheet, to confirm it still exists and you can access it.
  • Note the exact error message on the connector, because it usually names the failing layer.
  • Check whether the connector is still available in the connector gallery if it is a third-party connector.

Authentication and reconnection

The most common cause is expired authentication. Looker Studio connectors authenticate against an external account using tokens that can expire or be revoked. When that happens, the source shows a reconnection prompt. Reconnecting means reauthorizing the connector with the correct account. If the reconnect fails, the account you are signed in as may not have access to the underlying resource. Switch to the correct account and try again.

Account access and the underlying resource

A connector can be healthy but the connected account can lose access to the resource. For a Google Sheets source, confirm the sheet still exists and the connected account has edit or view access. For a GA4 source, confirm the account still has access to the property. For a Google Ads source, confirm the account is still linked. If the resource was deleted, no reconnection will work and the source must be recreated from a valid resource.

Connector-specific behavior

Connector behavior varies. Native Google connectors like GA4, Google Ads and Google Sheets are maintained by Google and rarely disappear, but their available fields and connection methods can change. Third-party connectors for CRM or other platforms are maintained by external developers and can be deprecated, updated or removed. If a third-party connector stops working, check the connector listing for status or version changes. Do not assume every connector recovers identically after a reconnect.

When to recreate the data source

If reconnection fails repeatedly and the underlying resource is intact, recreate the data source. Add a new data source using the same connector and resource, then point the broken charts at the new source. This is faster than troubleshooting a corrupted source connection. Note that recreating a source means reapplying any custom field formatting or calculated fields that lived in the old source.

How to test the fix

  1. 1.After reconnecting, open the data source fields page and confirm fields populate without an error.
  2. 2.Return to the report and refresh, then confirm the broken charts now render data.
  3. 3.Change a value in the underlying resource and confirm it flows through after the data freshness window.
  4. 4.Have a second user open the report to confirm the connection works for viewers, not just editors.

How to validate the final result

A data source is fully recovered when its fields page loads without error, the charts using it render real data and a second user can view the report without a connection prompt. If the source reconnects but fields are missing, the underlying resource schema may have changed and the source needs to be refreshed or recreated to pick up the new fields.

Frequently Asked Questions

Why does reconnecting my data source not fix the broken charts?

Reconnection restores authentication but does not fix schema changes. If fields were removed or renamed in the underlying resource, the charts that reference those fields stay broken until you update the field references or recreate the source.

Do I need to recreate my data source if authentication expires?

Usually no. Expired authentication is fixed by reauthorizing the connector through the reconnection prompt. You only need to recreate the source if the underlying resource was deleted or the connector itself is no longer available.

Related Service

Need help applying this to your business?

Explore Marketing Integrations
PPC Pritam
Written by PPC Pritam

PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.

Related Guides

Looker Studio Troubleshooting

Looker Studio Report Not Loading: What to Check First

When a Looker Studio report fails to load, the cause sits at the report, data source, connector, permissions or browser layer. Isolate which layer is failing before rebuilding anything, because the fix depends on where the break is.

Read Article
Looker Studio Troubleshooting

Looker Studio Showing No Data: How to Diagnose the Problem

No data means either the source has no matching rows or the chart filters everything out. These need opposite fixes, so confirm which one applies before changing the report configuration.

Read Article
Looker Studio Audit

Looker Studio Dashboard Audit Checklist: How to Validate Every Important Metric

A complete audit checks data sources, authentication, date ranges, dimensions, metrics, filters, calculations, blended data and the final totals against the source platforms. Work through each layer in order.

Read Article