Professionals collaborating in an office setting, focused on digital data analysis during a meeting.

GA4 Identity & Attribution in 2026: Why Your Numbers Don’t Match

BySplinternet Marketing

Your GA4 interface, Looker Studio dashboard, and BigQuery export can all be correct — and still disagree.

In 2026, most reporting conflicts I see in WordPress and WooCommerce environments are configuration problems, not tagging failures. Reporting Identity, Attribution Settings, and Default Channel Grouping each control different layers of reporting logic. If those decisions aren’t documented and aligned, executives end up questioning revenue, ROAS, or lead volume for the wrong reasons.

What Reporting Identity and Attribution Actually Control (and What They Don’t)

Reporting Identity affects how users are deduplicated in reports — not how events are collected or stored.

GA4 Reporting Identity allows you to choose Blended, Observed, or Device-based identity. Per Google’s documentation, Blended can use User-ID, Google Signals, and device identifiers; Observed relies on collected identifiers without modeled cross-device data; Device-based uses device-level identifiers only. These settings change how users and conversions are stitched together in the GA4 interface.

They do not change the underlying event stream collected by your tags.

Google Signals enables cross-device reporting for signed-in Google users and introduces modeling and privacy thresholds in reports. That impacts UI metrics like Users and conversion paths. Signals data is not exported as cross-device joins in BigQuery event tables, and thresholding can affect what you see in standard reports.

Attribution Settings change how conversion credit is assigned in reports — not how events are captured.

GA4 Attribution Settings define the property-level attribution model (for example, data-driven or last click) and lookback window. As documented by Google, these settings affect how conversions are credited across GA4 reports and advertising integrations.

They do not rewrite the underlying event records. Changes to attribution models also do not retroactively reprocess all historical data in every reporting context. If your model changes, expect reporting differences moving forward and potentially within eligible historical ranges.

Default Channel Grouping affects labeling — not raw source data.

GA4’s Default Channel Grouping defines how source/medium and campaign data are bucketed into channels like Organic Search, Paid Search, or Cross-network. Editing or redefining channel logic affects how traffic appears in reports. It does not alter the original source, medium, or campaign parameters stored with events.

If revenue shifts between channels after a configuration change, that is usually classification logic — not demand volatility.

Why BigQuery and Looker Studio Disagree with the GA4 Interface

GA4 BigQuery exports contain event-level data. They do not replicate all interface-level modeling.

Google’s export documentation makes clear that BigQuery receives raw event data. It does not apply Reporting Identity stitching, Google Signals cross-device modeling, or UI-level attribution reweighting for you. That means:

  • No automatic Blended identity deduplication.
  • No Google Signals joins in export tables.
  • No applied data-driven attribution model unless you build it.

So yes — BigQuery may show higher user counts than the GA4 interface under Blended identity. That does not make BigQuery “more accurate.” It makes it less modeled. Accuracy depends on your reporting objective.

Looker Studio introduces another variable. If you use the native GA4 connector, property-level identity and attribution settings flow into your reports. If you connect Looker Studio to BigQuery instead, you are responsible for defining:

  • User stitching logic.
  • Attribution model replication (if required).
  • Channel grouping rules.

Search Engine Land has covered ongoing attribution reporting confusion since GA4 replaced Universal Analytics. The pattern in small-business environments is consistent: mismatches are typically configuration drift, not broken tags.

A common executive scenario:

  • GA4 UI (Blended, data-driven) shows $100,000 in revenue.
  • BigQuery dashboard shows $108,000.
  • CFO assumes tracking failed.

In reality, identity stitching, modeled cross-device behavior, attribution weighting, or channel classification differ between environments.

What to do next

1. Document Reporting Identity.
Admin → Reporting Identity. Confirm Blended, Observed, or Device-based. Record whether Google Signals is enabled and whether thresholding appears in reports.

2. Confirm Attribution Settings.
Admin → Attribution Settings. Record the attribution model and lookback window. Ensure leadership understands how conversion credit is assigned in executive dashboards.

3. Review Default Channel Grouping.
Compare GA4’s channel definitions against any custom logic used in Looker Studio or BigQuery. Align paid media, SEO, and BI teams on one documented standard.

4. Align BigQuery modeling logic.
If executives rely on BigQuery dashboards, explicitly define:

  • Device-level vs. stitched user logic.
  • Whether to approximate GA4’s attribution model.
  • Channel classification rules.

Do not assume parity with the GA4 interface.

5. Add a reporting disclosure block.
Every executive dashboard should state:

  • Reporting Identity used.
  • Attribution model used.
  • Channel grouping logic used.
  • Data source (GA4 UI vs. BigQuery export).

Before troubleshooting tracking, reconcile configuration. In most U.S. small-business audits I perform, revenue “discrepancies” trace back to identity, attribution, or channel logic — not broken implementation.

Configuration discipline prevents revenue misinterpretation. In a GA4-only reporting stack, that’s operational risk management — not just analytics hygiene.

Sources

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.

Related Posts

Splinternet Marketing