GA4 Reporting Identity and Attribution: A Practical Manual

Many GA4 revenue mismatches in 2026 are configuration problems, not broken tracking.

If your WooCommerce revenue doesn’t align with Google Ads, or your CRM shows more qualified leads than GA4 reports, the first place to look is reporting identity and attribution settings—not your tag manager.

Reporting Identity and Attribution Settings — Where Revenue Math Gets Distorted

1. Reporting identity changes your user and conversion counts

GA4 offers three reporting identity options: Blended, Observed, and Device-based, as defined in GA4 Reporting Identity documentation.

Blended uses User-ID, Google signals, and device ID where available.
Observed uses User-ID and device ID, but not modeled cross-device data.
Device-based uses only device ID.

This setting affects how GA4 deduplicates users across devices. It does not change raw data collection, but it does change how users and conversions are reported.

For WooCommerce sites with logins, enabling and correctly implementing User-ID can materially reduce inflated user counts and duplicate conversions across devices. If you switch from Device-based to Blended, your historical reports may look different because reporting logic changes—even though your tagging didn’t.

If leadership sees user counts “drop” after a change, that’s often deduplication—not traffic loss.

2. Attribution settings shape channel credit

GA4 attribution settings live at the property level, not inside individual reports, as documented in GA4 Attribution Settings. Here you select:

The reporting attribution model (for example, data-driven or last click).
The lookback window for acquisition and other conversion events.

Change the model and your channel performance reshuffles immediately in reports. Data-driven attribution redistributes credit across touchpoints based on observed conversion paths. Last click assigns full credit to the final interaction.

This does not change how events are collected. It changes how credit is assigned in GA4 reporting. Budget decisions based on channel ROAS should always note which model is active.

3. Key events are not cosmetic

In GA4, events marked as key events (formerly conversions) are the actions used in standard reporting and shared with linked Google Ads accounts, as explained in Mark Events as Key Events documentation.

If you mark “form_submit” as a key event but forget to qualify it (for example, no spam filtering or no lead-type distinction), you train bidding systems on low-quality signals.

For WooCommerce, confirm that purchase is properly configured and that revenue parameters are accurate. For lead-gen, separate micro-events (like “page_view” or “scroll”) from true sales-qualified actions.

4. Default channel grouping quietly shapes executive dashboards

GA4’s default channel grouping determines how traffic is bucketed into Paid Search, Organic Search, Email, Paid Social, Cross-network, and more.

Common misclassification issues I see:

Email traffic missing proper UTM medium and landing in “Unassigned.”
Paid social tagged inconsistently and reported as Referral.
Performance Max traffic appearing under Cross-network, confusing channel comparisons.

If your channel grouping is messy, your executive summary is distorted before anyone debates strategy.

5. BigQuery changes the level of control

The GA4 BigQuery Export documentation confirms that event-level data can be exported to BigQuery with full schema access.

This does not fix bad tagging. But it does give you:

Event-level reconciliation against CRM or WooCommerce order tables.
The ability to re-analyze attribution logic outside GA4’s interface.
Clear visibility into raw parameters when revenue doesn’t align.

If leadership needs defensible revenue numbers, BigQuery is the control layer—not another dashboard.

6. Search Console linking answers different questions than Ads linking

According to Google’s Link Search Console and GA4 documentation, linking Search Console surfaces query and landing page data inside GA4 reports.

This integration helps you understand:

Which queries drive sessions.
How organic landing pages perform post-click.

It does not replace native Search Console analysis, and it does not pass keyword-level data into conversion modeling the way Google Ads linking does. Treat it as diagnostic context, not a revenue source of truth.

What to do next

Check reporting identity. Confirm whether you are using Blended, Observed, or Device-based. If you support logins, validate User-ID implementation before changing identity.
Document your attribution model. Screenshot the current property-level attribution setting. Make sure budget discussions reference that model explicitly.
Audit key events. Review every event marked as key. Remove low-intent actions. Validate revenue parameters for ecommerce.
Review channel grouping. Test common UTMs. Identify “Unassigned” or misclassified traffic. Clean up naming conventions.
Confirm Google Ads linking. Ensure only intended key events are shared for bidding.
Link Search Console. Use it to evaluate query-to-landing-page performance, not to reconcile revenue.
Enable BigQuery export if stakes are high. Especially for WooCommerce or multi-touch lead environments where CRM reconciliation matters.

If GA4, Ads, and your CRM don’t align, start with configuration. Reporting identity, attribution settings, and key events shape the story your data tells. Fix those before you question your traffic—or your team.

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.