Looker Studio Blended Data: GA4 + Search Console + Google Ads in One Report (2026)

How do I blend GA4 with Search Console and Google Ads in Looker Studio?

Blend three sources in Looker Studio using date as the primary join key for time-series comparisons, Landing page / URL as the secondary join key for content-level analysis (GA4 + GSC), and Campaign name for paid analysis (GA4 + Google Ads). Critical caveat: GA4 and Search Console measure fundamentally different things — GSC counts search impressions and clicks before the user lands, GA4 counts sessions after they arrive.

A 1:1 match is impossible. Expect GSC clicks to exceed GA4 organic sessions by 5–20% due to bot filtering, cross-device gaps, and cookie consent. The blend is useful for trend analysis and content-level SEO+engagement correlation, not for arithmetic reconciliation.

Why blending is complex: the measurement mismatch

Before building blends, understand what each source actually measures:

Google Search Console:

• Impressions: how many times your page appeared in Google search results
• Clicks: how many times someone clicked through from the SERP
• Average position: your average ranking for the query
• CTR: clicks ÷ impressions
• All data is query and URL-level

GA4:

• Sessions: visits to your site where at least one event fired
• Users: devices/users that visited
• Engagement: what users did after arriving
• All data is session and event-level, filtered through GA4's own bot detection and tied to cookie availability

Google Ads:

• Impressions: ad was shown
• Clicks: ad was clicked
• Conversions: GA4 key events imported as conversions (or pixel-based)
• Cost: spend data
• All data is ad/campaign/keyword level

The practical implication: when you blend GA4 sessions with GSC clicks at the page level, the numbers will never match. Build blended reports to answer correlation questions ("do higher-ranking pages also deliver better engagement?"), not reconciliation questions ("do our GA4 session counts match GSC clicks?").

The three production blend configurations

Configuration 1 — GA4 + Search Console: organic content performance

Use case: For each landing page, show rankings, click volume, engagement rate, and conversion rate together. Identifies pages that rank well but fail to convert, or pages that convert well but have low visibility.

Join key: Landing page (GA4) joined to Landing page (GSC)

GA4 fields to expose:

• Landing page
• Sessions
• Engaged sessions
• Engagement rate
• Key events
• Purchase revenue (if applicable)

GSC fields to expose:

• Landing page
• Clicks
• Impressions
• Average position
• CTR

Blend type: Left outer join with GA4 as the primary source. This ensures all GA4 landing pages appear even if GSC has no impression data for them (e.g., pages accessed directly or via paid channels).

Filters on GA4 source before blending:

• Session default channel group = Organic Search — restrict GA4 data to organic sessions only, otherwise you're mixing paid, direct, and organic sessions with GSC organic query data

The chart to build: A table sorted by Sessions descending, with columns: Landing page, Clicks (GSC), Position (GSC), CTR (GSC), Sessions (GA4), Engagement rate (GA4), Key events (GA4). This table answers: "For our organic traffic, which pages rank and engage well vs which pages rank but don't engage?"

Interpreting the table:

• High position (low number) + high CTR + low engagement rate → landing page quality issue, not SEO issue
• Low position (high number) + high engagement rate → content quality is strong, needs SEO improvement
• High clicks + significantly lower sessions → consent filtering or cross-device gap — normal, expect 5–20% difference

Configuration 2 — GA4 + Google Ads: paid campaign ROAS

Use case: Show ad spend, click volume, session quality, and conversions together per campaign. Single-source paid performance view without jumping between Ads and Analytics.

Join key: Session campaign (GA4) joined to Campaign (Google Ads)

GA4 fields to expose:

• Session campaign
• Sessions
• Engaged sessions
• Key events
• Purchase revenue

Google Ads fields to expose:

• Campaign
• Impressions
• Clicks
• Cost
• Conversions (Ads-reported)

Blend type: Full outer join — you want to see campaigns that have spend but no GA4 traffic (attribution gap) and campaigns that have GA4 traffic but no recorded spend (auto-tagged clicks not matching campaign names).

Calculated fields on the blend:

• ROAS = SUM(Purchase revenue) / SUM(Cost) — GA4 revenue divided by Ads spend
• CPA = SUM(Cost) / SUM(Key events) — Ads spend divided by GA4 conversions
• Click-to-session rate = SUM(Sessions) / SUM(Clicks) — shows how much of Ads click volume reaches GA4 (should be 85–95%; lower indicates tracking issues)

The chart to build: Table sorted by Cost descending. Columns: Campaign, Cost, Clicks, Sessions, Click-to-session rate, Key events, ROAS, CPA. Reference line on ROAS at 1.0 (break-even).

Common issue: Campaign name mismatches between GA4 and Google Ads. GA4 captures campaign names via UTM parameter or gclid auto-tagging. If campaigns use inconsistent naming (spaces vs underscores, title case vs lowercase), they won't join correctly. Standardise UTM campaign names and use them consistently.

Configuration 3 — GA4 + Search Console + Google Ads: full channel view

Use case: Executive-level channel dashboard showing organic and paid side-by-side with their respective quality metrics.

This is a three-source blend. Looker Studio supports multi-source blends. The join structure:

1. GA4 (primary source) → Date as join key
2. GSC → Date as join key
3. Google Ads → Date as join key

Date-level blending allows time-series comparison. For page/keyword or campaign-level detail, use the two-source configurations above.

Fields per source:

• GA4: Date, Sessions (organic), Sessions (paid), Key events, Revenue
• GSC: Date, Clicks, Impressions, Average position
• Google Ads: Date, Cost, Conversions (Ads-attributed)

Filter GA4 before blending: Create two separate GA4 data sources — one filtered to Session default channel group = Organic Search, one filtered to paid channels. Blend both with their respective external sources. This avoids mixed traffic polluting the blend.

The charts to build:

• Time-series: Organic sessions (GA4) + GSC clicks on same axis — shows divergence trend over time
• Time-series: Paid sessions (GA4) + Google Ads cost on dual axis — shows efficiency trend
• Scorecard row: Total sessions, Total key events, Total revenue, Total ad spend, Blended CPA

Five blend configurations that don't work

Blend 1 — GA4 + GSC joined on `Query` GSC has query-level data. GA4 does not expose search query data (Google withholds ~40% of queries as (not provided)). Attempting to join on query produces massive null rows in GA4. Build this analysis in BigQuery using GSC API + GA4 BigQuery export if you genuinely need query-level intent + behaviour correlation.

Blend 2 — GA4 + Google Ads joined on `Keyword` GA4 doesn't reliably receive keyword-level data from Google Ads (broad match + dynamic search ads don't pass keyword to GA4). The join produces fragmented data. Use Google Ads' native Search Terms report, then join at the campaign level in Looker Studio.

Blend 3 — GA4 (all traffic) + GSC (organic) with no filtering Blending all GA4 sessions (direct, paid, social, organic combined) with GSC organic click data produces meaningless session counts next to GSC clicks. Always filter GA4 to organic-only before blending with GSC.

Blend 4 — Blending user metrics across sources GA4 Users and Google Ads Users reached are different counts with different deduplication logic. Blending them and attempting arithmetic produces inflated or nonsensical totals. Keep user metrics from their native sources; don't arithmetically combine them.

Blend 5 — Blending without consistent date granularity Blending daily GA4 data with monthly Google Ads data at the date level will produce null rows for all days not in the monthly aggregation. Ensure all sources are configured to the same date granularity before blending.