GA4 Identity, Attribution & BigQuery: A Reporting Audit
By mid-2026, most small businesses have migrated to GA4. The problem I see weekly: leadership compares GA4 UI conversions to BigQuery totals and Search Console clicks—and assumes tracking is broken.
In most cases, it isn’t. Your numbers differ because of four configurable settings and two different data scopes. If you don’t audit them, you distort CAC, ROAS, SEO performance, and lead reporting.
The Four GA4 Settings That Distort Your Decisions
1. Reporting Identity
GA4 allows three reporting identities: Blended, Observed, and Device-based, as documented in GA4 Reporting identity. Blended can combine User ID, Google signals, and device data; Observed uses User ID and device data; Device-based relies only on device identifiers.
Audit check: Admin → Reporting identity. Confirm which identity space is active.
Decision risk: Switching from Device-based to Blended can reduce user counts through cross-device deduplication. That changes conversion rate and cost-per-user math without any traffic change. BigQuery exports event-level data and is not subject to the same UI identity modeling in the same way, which is one reason totals don’t align perfectly.
2. Attribution Settings
GA4 Attribution settings define your attribution model and lookback windows. Google documents that properties can use data-driven attribution or other models, and configure lookback windows for acquisition and key events.
Audit check: Admin → Attribution settings. Confirm the attribution model and lookback windows.
Decision risk: If you assume last-click logic but the property uses data-driven attribution, credit will be distributed across touchpoints. Paid search, organic search, and email may all shift in reported contribution. Budget decisions based on outdated last-click assumptions will be misaligned with how GA4 is actually assigning credit.
3. Key Events
In GA4, conversions are now “key events.” Google’s documentation confirms events must be marked as key events to be used in standard conversion reporting and ad integrations.
Audit check: Admin → Events. Verify which events are marked as key events. Confirm recommended parameters like value and currency are present for revenue events.
Decision risk: If a lead event is not marked as a key event, it will not appear in standard conversion metrics. If value parameters are missing, ROAS and revenue metrics distort. If Google Ads imports rely on specific key events, misconfiguration affects bidding inputs.
GA4’s Default channel group is rule-based and defined in Google’s documentation. It differs from Universal Analytics logic and may differ from ad platform channel definitions.
Audit check: Confirm you’re using Default channel group or a Custom channel group. Document any custom logic and confirm it’s understood by stakeholders.
Decision risk: Channel definitions are not interchangeable across platforms. Organic Search in GA4 will not necessarily match Google Ads views or legacy UA reports. Custom channel group changes are not universally retroactive in all contexts, so historical comparisons can be misleading.
BigQuery and Search Console: Why the Numbers Differ
BigQuery export
GA4’s BigQuery export provides event-level rows with fields such as traffic source and event parameters, as documented in the GA4 BigQuery export schema. It is raw event data.
It is not a “more accurate” version of GA4. It still depends on tagging quality and consent signals. But it does not apply the same UI reporting identity and attribution layers in the same presentation format. Expect differences in user counts and conversion totals when comparing directly to standard UI reports.
Google documents that Search Console and Analytics integration combines Search data (clicks, impressions, queries) with Analytics data, but they remain distinct datasets.
Search Console reports Search clicks and impressions. GA4 reports sessions and events. Differences commonly come from:
- Different definitions of clicks vs sessions
- Time zone settings
- Attribution model differences
- Consent and identity space differences
Search Console is not a traffic analytics system equivalent to GA4. Treat it as Search performance data.
What to do next
Run this 6-step audit this week:
- Document reporting identity. Screenshot the active identity space and note when it was last changed.
- Confirm attribution model and lookback windows. Align reporting expectations and internal dashboards with the configured model.
- Review key events. Verify that all primary leads, purchases, and qualified actions are marked correctly and include required parameters.
- Inventory channel groups. Confirm whether stakeholders are using Default or Custom channel groups and standardize definitions in Looker Studio.
- Reconcile BigQuery logic. If you report from BigQuery, document how you derive users, sessions, and conversions and how that differs from UI modeling.
- Validate Search Console linkage. Confirm properties are correctly linked and explain to leadership why Search clicks will not equal GA4 sessions.
If your numbers don’t match, assume configuration before assuming failure. Most reporting disputes in 2026 are not tracking bugs—they’re identity, attribution, and scope misunderstandings. Fix those first, and your channel ROI conversations get much cleaner.
Sources
- Google Analytics Help: Reporting identity
- Google Analytics Help: Attribution settings
- Google Analytics Help: Mark events as key events
- Google Analytics Help: BigQuery Export schema
- Google Analytics Help: Default channel group
- Search Console Help: Search Console and Analytics integration
Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.
This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.
Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.