GA4 Reporting Identity and Attribution Can Change Revenue Overnight
Your GA4 revenue didn’t necessarily drop. Your configuration may have changed.
I’ve seen WordPress and WooCommerce teams shift Reporting Identity or attribution settings and watch conversions, ROAS, and channel performance swing overnight. The business didn’t change. The math did.
Google Analytics 4 makes several reporting behaviors configurable at the property level. Others are modeled. If you don’t know which is which, you can end up reallocating ad budget or questioning SEO performance based on configuration-driven movement.
Reporting Identity, Attribution, and Key Events — What’s Configurable vs. Modeled
1. Reporting Identity (Blended, Observed, Device-based)
Google documents three reporting identity options in GA4: Blended, Observed, and Device-based. Blended uses User-ID, Google signals, and device data when available. Observed uses User-ID and device data. Device-based relies only on device data.
Switching identity affects how users are deduplicated across devices and sessions. According to GA4 Reporting Identity documentation, this changes user counts and can alter conversion paths and revenue totals in reports.
For ecommerce operators, moving from Blended to Device-based typically increases users and can fragment paths. That alone can shift assisted conversion and channel contribution reporting.
Important: identity changes are not universally retroactive across all reports and can create apparent performance swings tied to configuration, not demand.
2. Attribution model and lookback window
GA4 Attribution Settings are configured at the property level. Google confirms you can choose the attribution model and set lookback windows for acquisition and other conversion events.
Changing the model redistributes credit across channels in reporting. It does not rewrite raw event data. If you switch models mid-quarter and don’t document it, your paid search or organic performance may appear to jump or fall purely because of attribution logic.
Search Engine Land has covered how model differences create practitioner confusion, especially when teams compare GA4 to Google Ads or UA-era reports.
3. Creating an event vs. marking it as a key event
In GA4, any event can be marked as a key event. Google’s Key Events documentation is explicit: marking an event as a key event makes it eligible for conversion reporting and downstream optimization use cases.
On WooCommerce sites, I routinely see purchase implemented correctly, but generate_lead or add_to_cart inconsistently marked. That directly affects reported conversions and, if imported, can affect bidding strategies in Google Ads.
Creating an event does not automatically make it a key event. That designation matters for revenue dashboards and ROAS conversations.
Channel Grouping and BigQuery — Why the UI and Export Don’t Always Match
Default Channel Group rules
GA4’s Default Channel Group uses defined rule logic to classify traffic (for example, Paid Search, Cross-network, Organic Social). Google publishes those rule definitions.
If your UTM structure is inconsistent, or you rely on auto-tagging in some platforms but not others, traffic can shift between channels. Cross-network campaigns in particular can surprise teams expecting “Paid Search.”
When leadership compares SEO, Paid Search, and Social performance, they are comparing rule-based classifications. If those rules reclassify traffic, your channel narrative changes.
Why BigQuery won’t match the GA4 UI exactly
Google’s GA4 BigQuery Export documentation explains that export data is event-level and does not include all modeled or thresholded reporting behaviors visible in the UI.
For example, certain Google signals data and privacy thresholding behaviors affect standard reports. BigQuery gives you raw event export. That’s why totals can differ.
If you see unexplained revenue swings, validating event counts and purchase revenue in BigQuery is often the fastest way to separate configuration effects from data collection failures.
What to do next
1. Log your configuration state today.
Document Reporting Identity, attribution model, and lookback windows. Screenshot them. Record the date. Treat these like accounting policy changes.
2. Audit key events.
In Admin, confirm which events are marked as key events. For WooCommerce, verify purchase, add_to_cart (if used for optimization), begin_checkout, and generate_lead are intentionally designated. Remove legacy or duplicate key events that inflate totals.
3. Validate Default Channel Group exposure.
Review GA4’s published channel definitions. Spot-check a week of traffic by source/medium. Confirm UTMs align with how you expect traffic to classify. Standardize naming conventions across Google Ads, Microsoft Advertising, Meta, and email platforms.
4. Spot-check revenue in BigQuery.
Run a simple query summing purchase event revenue for a fixed date range. Compare that to GA4 standard reports. Differences often point to modeling, thresholding, or attribution shifts—not broken tracking.
5. Annotate dashboards.
In Looker Studio, add visible notes for identity or attribution changes. Executives reviewing month-over-month performance need to know when the math changed.
If you manage budget, bids, or forecasts, treat GA4 configuration changes as financial reporting changes. Before reallocating spend or questioning SEO performance, confirm whether Reporting Identity, attribution, key event designation, or channel rules moved the numbers.
Sources
- Google Analytics Help: Reporting Identity
- Google Analytics Help: Attribution Settings
- Google Analytics Help: Key Events
- Google Analytics Help: Default Channel Group
- Google Analytics Developer Docs: BigQuery Export
- Search Engine Land: GA4 Attribution Context
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.
