How to Connect GA4 to Looker Studio

Connecting Google Analytics 4 to Looker Studio is a common setup task for marketers who want a reusable report instead of repeating the same GA4 clicks every week. The workflow is straightforward at a high level: authorize Google access, choose the GA4 connector, select a property, create a data source, and then build or attach a report. The details that cause trouble are usually permissions, the wrong property, or numbers that do not match what people see in GA4.

This guide stays at a practical level. Google can change button labels and connector screens, so treat the steps as a workflow rather than a promise that every menu will look identical forever.

What you need before you start

You need a Google account that can open Looker Studio and a GA4 property you are allowed to read. Viewer access is enough to pull data into a report. Editor access is needed if you also manage the GA4 property itself. If you cannot see the property in GA4, you will not be able to select it in Looker Studio.

You also need a clear idea of which property should feed the report. Many organizations have a test property, a staging site, or an old Universal Analytics-era archive sitting next to the production property. Connecting the wrong one is the most common “the numbers look off” problem, and it has nothing to do with chart design.

If several people will edit the finished report, decide who will own the data source. In Looker Studio, credentials and sharing settings affect whether colleagues see data or an authorization error.

Open Looker Studio and add a data source

Start in Looker Studio and create a data source, or add a data source from inside a report. Choose the Google Analytics connector provided by Google. You will be asked to authorize access if you have not already allowed Looker Studio to read Analytics data for that Google account.

After authorization, the connector should list the GA4 accounts and properties available to you. Expand the account, then select the property. Confirm the name and numeric property ID against what you see in GA4 Admin. If the list is empty, the issue is almost always access: the signed-in Google account is not the one that was invited to the property.

Create the data source once the property is selected. Looker Studio will load the available dimensions and metrics from that GA4 property.

Check dimensions and metrics before you design

Do not skip the field list. This is where you confirm that the connection is using GA4, that key events exist, and that ecommerce fields appear only if the property actually collects them.

Look for the metrics your report will rely on: active users, sessions, engagement rate, key events or conversions, and purchase or revenue fields if you expect ecommerce. If a conversion you use in meetings is missing, it may not be marked as a key event in GA4, or it may use a different event name than the one people say out loud.

This is also the moment to notice naming. GA4 field names in Looker Studio are not always the words your team uses in Slack. Deciding the labels now prevents a dashboard that technically works and still confuses every stakeholder.

Create the report and attach the data source

If you started from a blank report, add charts and assign the new GA4 data source to them. If you started from a copied template, replace the sample data source with your newly created one. In both cases, keep the first page small: a few scorecards, a date comparison, and one trend chart are enough to prove the connection.

Add a date range control early. Without it, you will argue about numbers that come from different default periods. A comparison date range is just as important. The point of a reusable report is to see change, not only a single isolated total.

Filters come next. A country filter, a channel filter, or a landing-page search box can make the same page useful for more than one meeting. Add only the filters people will actually use. Too many controls make the report feel unfinished.

Validate the data against GA4

Validation is part of connecting GA4, not an optional extra. Open GA4 and Looker Studio side by side. Use the same date range. Compare a small set of metrics: users, sessions, a key event count, and revenue if you have it.

You should expect small differences. GA4 interfaces, Looker Studio, and exported data can disagree slightly because of processing delay, sampling in some GA4 explorations, different attribution settings, or timezone. A large gap usually means a different property, a different date range, a different conversion event, or a filter that is applied in one tool and not the other.

If the scorecards are close and the trend shape matches, the connection is good enough to keep building. If a single metric is wildly off, check that metric’s definition before rebuilding the whole page.

Reporting considerations after the first connection

Once the data source works, the remaining work is report design. Group metrics the way the team talks: demand, engagement, outcomes, content, and channels. Keep calculated fields documented. If you blend data sources later, test those blends separately because blending is a frequent source of duplicated sessions or broken joins.

Sharing settings matter as much as charts. Viewers need permission to see the report and, in some setups, the underlying data source credentials must be set so colleagues are not prompted to authorize a property they cannot access. For client work, decide whether the client receives view access to the live report or exported snapshots.

Also plan for change. New key events, a redesigned site, or an ecommerce implementation will alter what the connector returns. Revisit the field list when tracking changes. A connection that was correct at launch can become misleading after the event schema moves.

Common issues and how to think about them

• The property list is empty: the Google account does not have access to that GA4 property.
• The report shows zeros: the date range may be empty, a filter may exclude all rows, or the selected property may have no data.
• Conversions do not match GA4: you may be comparing different events, different attribution, or a user metric against an event count.
• Colleagues see authorization errors: the data source credentials or sharing settings need to be reviewed.
• Ecommerce fields are missing: the property may not be sending purchase events yet.

None of these issues require rebuilding Looker Studio from scratch. They require checking access, property, date range, and field definitions in that order.

Using a prebuilt report structure

Connecting the data source is only half of a useful report. The other half is deciding what to show first. If you prefer not to design that structure on a blank page, you can connect the same GA4 property to a prebuilt file. The OptimCamp GA4 Data Studio Template is built for that workflow: make your own copy, connect your property, then adjust the pages you need.

A template does not change the connection steps. You still authorize access, choose the correct property, and validate the numbers. It only gives the report a starting layout after the data source is in place.

Conclusion

To connect GA4 to Looker Studio, authorize the Google Analytics connector, select the correct property, review the field list, attach the data source to a report, and validate a few core metrics against GA4. The technical connection is usually the short part. The useful part is confirming that the report is reading the property you think it is, then giving marketers a date range, a comparison, and a small set of KPIs they can trust. Once that foundation is stable, you can add pages, filters, and branding without wondering whether the connector is working.