Looker Studio connectors
A connector is the bridge between Looker Studio and a data source — Google connectors (GA4, BigQuery, Sheets, Ads) and community/partner connectors for everything else. The connector defines available fields, default aggregations, and data freshness/caching behavior, all of which shape what a report can show and how current it is.
What this means
A connector tells Looker Studio how to query a source. Google-built connectors cover GA4, BigQuery, Google Sheets, Google Ads and more; community and partner connectors cover other platforms. Each connector exposes a set of fields with types and default aggregations that become the report's building blocks.
Freshness, caching, and field config
Connectors cache results and have a data-freshness setting that controls how often Looker Studio re-queries the source; shorter freshness means fresher data but more queries (and cost, for BigQuery). The connector's field configuration — types, default aggregation, whether a field is a dimension or metric — determines what charts can do. When numbers look stale, check freshness; when a calculation is wrong, check the field's type and default aggregation.
- Google, community, and partner connectors
- Connector defines available fields and types
- Freshness/caching controls how current data is
How it appears in analytics and logs
What a report can display is bounded by its connector's schema. Stale numbers usually mean data freshness/cache settings; missing fields mean the connector doesn't expose them or they need configuration.
Diagnostic use case
Bring a data source into a report by choosing the right connector, then map its fields and set freshness so the dashboard reflects current data at an acceptable cost.
What WebmasterID can help detect
WebmasterID's first-party data can feed a report alongside other connected sources without relying on third-party cookies.
Common mistakes
- Blaming the report for staleness set by data freshness.
- Overlooking a field's default aggregation in calculations.
- Connecting a source that exposes more than intended.
Privacy and accuracy notes
Connectors inherit the source's access controls; a connected source can expose its data to report viewers. Connect only sources you intend to share and avoid identifying fields.
Related pages
- Looker Studio data blending
Data blending in Looker Studio combines fields from up to several sources into one logical table by joining on configured keys. It supports join types (left outer, inner, full outer, cross). The common failure is join-key cardinality: a one-to-many key fan-out multiplies metric rows, so blended totals can silently overcount.
- Looker Studio calculated fields
Calculated fields let you derive new fields with formulas — arithmetic, CASE logic, text and date functions — at the data-source or chart level. The decisive subtlety is aggregation: a formula's result depends on whether it is computed per-row then aggregated, or on already-aggregated values, which differs between field-level and chart-level calculations.
- Scheduled email reports
Scheduled email delivery sends a Looker Studio report as a PDF to chosen recipients on a recurring schedule. It is the simplest way to push reporting to stakeholders who won't log in. The caveat: the PDF is a snapshot rendered at send time, with the filters and freshness state then — not a live link.
- Multi-site analytics
Feed first-party data into connected reports.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.