GBP Insights shows actions. GA4 shows on-site behavior. Search Console shows queries and impressions. None of them shows everything. And when you compare the numbers across platforms, they do not match. This is not a bug. It is a feature of three different measurement systems with different definitions, different scopes, and different sampling methods.
Understanding where the numbers diverge and why is essential to building a reliable view of your local search performance. Businesses that rely on a single platform’s data make decisions based on incomplete pictures. Businesses that cross-validate across all three make decisions based on triangulated evidence.
What Each Platform Measures (and What It Misses)
GBP Insights: Actions and Discovery (But Not Revenue)
GBP Insights tells you how people interact with your business listing. The data includes: how they found you (direct search for your business name versus discovery search for a category or service), what actions they took (website click, phone call, direction request), how your photos perform relative to businesses in your category, and how your Google Posts engage viewers.
GBP Insights also shows search queries that triggered your listing, though this data is more limited than Search Console’s query reports. It groups queries by type and shows relative frequency rather than exact counts for lower-volume terms.
What GBP Insights misses: everything that happens after the action. Someone clicked your website link. Did they book an appointment? Did they call after browsing? Did they bounce immediately? GBP tracks the handoff to your website but not the outcome. Someone called from your listing. How long was the call? Did it result in a booking? GBP counts the call initiation but not the conversation or conversion.
The other critical gap: GBP Insights data has historically been limited to 6 months in the dashboard interface. Connecting GBP Insights to Looker Studio via the GBP API extends historical data to 18 months, which is essential for year-over-year seasonal comparisons that 6-month windows cannot provide.
GA4: On-Site Behavior (But Attribution Gaps for Local)
Google Analytics 4 tracks what users do on your website: pages visited, time engaged, scroll depth, conversion events (form submissions, button clicks, phone number clicks), and user flow through your site.
GA4’s event-based model provides more flexibility than Universal Analytics for tracking local-specific interactions. You can create custom events for: click-to-call taps, direction button clicks, booking widget interactions, and chat initiations. Each of these represents a local conversion action that GA4 can measure if properly configured.
What GA4 misses for local SEO: the source distinction between GBP listing clicks and standard organic search clicks. GA4 lumps both under “organic” unless you use UTM parameters to differentiate. A visitor who clicked your website link from your GBP listing and a visitor who clicked your organic search result both appear as “google / organic” in default GA4 reports.
This gap matters because GBP-sourced and organic-sourced visitors have different intent profiles. GBP visitors have already seen your listing (reviews, photos, hours) and are further along in the decision process. Organic visitors may be researching and comparing options. Treating them identically produces misleading conversion rate analysis.
GA4 also cannot track visitors who saw your GBP listing but took action without visiting your website. The customer who called directly from the listing, requested directions, or memorized your address and showed up never appears in GA4.
Search Console: Query and Impression Data (But No Conversion)
Google Search Console shows which queries generated impressions and clicks to your pages. It reveals the actual search terms driving traffic, your click-through rate for each query, your average position, and which pages receive impressions for which queries.
Search Console data is the most granular view of your search visibility. It answers questions that neither GBP Insights nor GA4 can: which specific keywords drive your traffic, which pages Google considers relevant for which queries, how your CTR compares across different query types, and whether your organic visibility is growing or shrinking at the query level.
What Search Console misses: conversions. Search Console tells you people clicked. It does not tell you what they did after clicking. It also does not include Map Pack data in the same way as organic web results. Your GBP listing impressions and clicks in Maps are reported separately and less granularly than organic web data.
Search Console also samples data for high-traffic sites, meaning the numbers are approximations rather than exact counts. For most local businesses, traffic volumes are low enough that sampling is not a significant concern, but for multi-location businesses with substantial traffic, the approximation can be meaningful.
Where the Numbers Don’t Match (and Why That’s Normal)
GBP “Website Clicks” vs GA4 Sessions: The Discrepancy Explained
This is the most common source of confusion. GBP reports 500 website clicks last month. GA4 shows 380 sessions from organic Google traffic. Where did 120 clicks go?
The gap has multiple causes. GA4 tracking script may not fire before the user bounces. If someone clicks your GBP link but leaves before the page fully loads, GBP counts a click but GA4 never registers the visit. This is especially common on slow-loading mobile pages. Ad blockers and privacy browsers prevent GA4 from loading on some visits. GBP counts the click server-side while GA4 requires client-side JavaScript execution. GBP counts the click even if the destination page returns a server error, while GA4 only fires on successful page loads. Some GBP “website clicks” may be directed to Google-cached or AMP versions that do not contain your GA4 tracking code.
Expect a 15% to 30% discrepancy between GBP website clicks and GA4 sessions. This is normal. If the discrepancy exceeds 40%, investigate: your GA4 tracking code may be broken on specific pages, your site speed may be causing excessive pre-load bounces, or your GBP website URL may be pointing to a redirect chain that loses visitors.
Track the discrepancy ratio itself as a diagnostic metric. If the gap suddenly widens, something technical has changed.
Search Console Impressions vs GBP Discovery Searches
Search Console impressions count instances where your page appeared in Google search results. GBP discovery impressions count instances where your listing appeared in Google Maps and Google Search for non-branded queries. These sound similar but measure different things from different surfaces.
Search Console tracks your website URLs in organic web results. GBP Insights tracks your listing card in the Map Pack, Google Maps, and the local finder. A search that triggers both a Map Pack (showing your listing) and an organic result (showing your website) may generate one impression in GBP Insights and one impression in Search Console, counted by different systems with different timestamps and different definitions of “impression.”
Do not try to reconcile these numbers to exact precision. Use them as complementary indicators. Search Console shows your website’s search visibility trajectory. GBP Insights shows your listing’s visibility trajectory. Both should trend in the same direction over time. If they diverge (website impressions growing while GBP impressions decline, or vice versa), investigate which channel is changing and why.
Date Range Alignment and Sampling Differences
GBP Insights data updates with a 48 to 72 hour delay. Search Console data has a similar delay, typically 2 to 3 days. GA4 processes data in near real-time but can retroactively adjust numbers as processing completes.
When comparing across platforms, ensure you are looking at the same completed calendar period and allow sufficient lag time for all three platforms to finalize their numbers. Comparing GA4 data from today against GBP data that has not yet processed today’s activity produces false discrepancies.
Monthly comparison is more reliable than daily or weekly comparison because the processing delays average out over 30 days. For daily monitoring, rely on a single platform rather than cross-comparing daily numbers across three platforms with different processing timelines.
Building a Cross-Validated View
UTM Tagging GBP Links to Separate Listing Traffic in GA4
The single most impactful technical setup for local SEO measurement: add UTM parameters to your GBP website link. Set UTM source as google, UTM medium as organic, and UTM campaign as gbp (or any consistent label you choose).
With UTM tagging, GA4 creates a distinct traffic segment for GBP-sourced visits. You can then analyze: how many GA4 sessions come specifically from GBP clicks versus other organic clicks, what GBP visitors do on your site (which pages they visit, how long they stay, whether they convert), whether GBP visitors convert at a different rate than other organic visitors, and which GBP entry pages perform best for conversion.
This single setup transforms your analytics from “we get organic traffic” to “we get X leads from our GBP listing and Y leads from organic search results, and they convert at different rates.” That distinction informs whether to invest more in GBP optimization or organic content.
Implementation note: when you change the GBP website URL to include UTM parameters, it may take Google a few days to propagate the change. Verify the UTM parameters appear correctly in GA4 traffic reports before relying on the data.
Combining Search Console Query Data with GA4 Conversion Data
Search Console tells you which queries drive clicks. GA4 tells you which pages convert. Combining them answers the highest-value question: which search queries produce revenue?
The process: export Search Console data showing queries, clicks, and landing pages. Export GA4 data showing landing pages and conversion events. Join on landing page URL. The result shows which queries drive traffic to your highest-converting pages.
For queries driving clicks to high-converting pages, protect and expand those rankings. For queries driving clicks to low-converting pages, investigate the mismatch. The content may not align with the query intent. The page may have a UX problem. The call-to-action may be weak or invisible on mobile.
For high-impression, low-click queries, optimize your title tags and meta descriptions to improve CTR. You are already visible for these queries. Capturing more of the existing impressions as clicks is often easier than ranking for entirely new queries.
Mapping GBP Actions to GA4 Landing Pages and Events
Create a unified view that maps GBP actions to website behavior. GBP tells you someone clicked to call, clicked for directions, or clicked to your website. For website clicks with UTM tagging, GA4 tells you what happened next.
Build a monthly reconciliation that shows: GBP total actions (calls plus directions plus website clicks), GA4 sessions from GBP (via UTM tracking), GA4 conversions from GBP sessions, and estimated total leads from all GBP sources (including calls and direction requests that never touch your website).
This reconciliation is imperfect. Calls from GBP cannot be tracked in GA4 without call tracking integration. Direction requests cannot be followed to actual visits without foot traffic data. But the reconciliation provides a more complete picture than any single platform alone.
Reporting Framework for Clients or Decision Makers
Which Platform to Use as the Source of Truth for Which Question
Use GBP Insights as the source of truth for: listing visibility and discovery trends, GBP-specific actions (calls, directions, photo views), competitive photo benchmarking, and search query categories triggering your listing.
Use GA4 as the source of truth for: website traffic volume and engagement, on-site conversion events, landing page performance, and user behavior flow from discovery to conversion.
Use Search Console as the source of truth for: keyword-level performance (impressions, clicks, CTR, position), indexation health and coverage issues, CTR optimization opportunities, and organic visibility trends at the query level.
No single platform answers every question. The skill is knowing which platform to consult for which question and how to combine insights across platforms for a complete picture.
A Three-Source Monthly Report Template
Structure the monthly report in four sections:
Section 1: Listing Performance (source: GBP Insights). Total impressions (discovery vs direct), total actions (breakdown by type), month-over-month and year-over-year trends, and any notable changes in query patterns.
Section 2: Website Performance (source: GA4). Total organic sessions, sessions from GBP specifically (via UTM), conversion events by type, conversion rate by landing page category, and engagement metrics for key pages.
Section 3: Search Visibility (source: Search Console). Total impressions and clicks, top query performance, new queries gaining traction, queries losing position, and CTR trends.
Section 4: Synthesis. The one or two insights that emerge only when you look across all three platforms. Example: “GBP impressions grew 15% but website clicks from GBP dropped 8%, suggesting our listing is visible but less compelling. Review score dropped from 4.8 to 4.6 this month, which likely explains the action rate decline.”
The synthesis section is where the cross-validation produces unique value. Any reporting tool can export data from one platform. The synthesis requires human analysis connecting patterns across platforms.
Connecting GBP Insights to Looker Studio for Historical Analysis
GBP Insights in the dashboard interface shows only 6 months of data. For year-over-year comparison, which is essential for businesses with seasonal patterns, connect GBP to Looker Studio via the Google Business Profile API.
Looker Studio provides: 18 months of historical GBP data, custom visualizations combining GBP data with other sources, automated monthly reporting that updates without manual export, and the ability to overlay GBP trends with GA4 and Search Console data in a single dashboard.
The setup requires: Google Cloud project with Business Profile API enabled, Looker Studio connector for GBP (several third-party connectors are available), and initial configuration to map data fields to visualizations.
Once configured, the Looker Studio dashboard becomes your single source for cross-platform local SEO reporting, automatically refreshing with minimal maintenance.
Platform capabilities and data definitions in this guide reflect GBP Insights, GA4, and Google Search Console as of February 2026. Google periodically updates reporting features, metrics definitions, and API access across all three platforms. The GBP Insights to Looker Studio connection provides the most robust historical data for year-over-year analysis.