Why Your GA4 Channel Numbers Changed: Aggregate Identifiers, “Data Not Available,” and the WordPress Tracking Checks to Run
If your GA4 source/medium or default channel numbers moved and nothing obvious changed in your campaigns, do not assume SEO fell off or paid traffic suddenly improved. Google documented two GA4 changes in 2025 that can affect attribution and reporting, and on WordPress or WooCommerce sites those shifts can overlap with real tracking problems.
First, Google said GA4 began using aggregate identifiers to improve attribution for paid Google Ads traffic in some reports. Second, GA4 introduced the value (data not available) for cases where traffic-source attribution data cannot be provided. Both changes can alter channel mix without a real change in demand, rankings, clicks, or conversion volume.
What changed in GA4 reporting
Per Google Analytics help documentation and the GA4 “What’s new” log, aggregate identifiers can make traffic-source dimensions more complete for eligible Google Ads traffic. That is an attribution and reporting change, not a traffic-generation change. In practice, some sessions or conversions may now appear under paid source/medium or channel dimensions differently than before.
Google also added (data not available) as a reporting value for traffic-source dimensions when attribution data cannot be shown. That is not the same as (not set), and it is not the same as true (direct) / (none).
A quick way to think about the three:
- (data not available): GA4 cannot provide the traffic-source attribution data for that dimension.
- (not set): the expected dimension value was not populated for that record or context.
- (direct) / (none): GA4 treated the visit as direct under its attribution rules.
Google’s direct-traffic documentation matters here too: not every rise in Direct means people typed in your URL. Some apparent “direct” shifts are really attribution loss, unavailable source data, or journey breaks between domains.
For WordPress operators, this is where reporting changes and implementation issues can get mixed together. A WooCommerce site with redirects, payment handoffs, consent tools, GTM changes, link shorteners, or checkout on another domain can lose attribution continuity even while GA4 is also reclassifying some traffic more accurately.
What to do next
Before changing budgets or declaring a channel win or loss, run a short audit.
- Confirm Google Ads linking and auto-tagging. Make sure the GA4 property is linked to Google Ads and auto-tagging is enabled. If paid traffic reporting changed after Google’s update, this may be reattribution rather than campaign movement.
- Check whether gclid and _gl survive the journey. On WordPress, test landing pages, redirects, caching layers, security tools, affiliate plugins, and checkout transitions. If redirects strip query parameters or a plugin rewrites URLs badly, attribution can break.
- Review cross-domain measurement. If checkout, booking, forms, or payment steps touch another domain, verify GA4 cross-domain setup and linker behavior. Google’s cross-domain documentation is explicit: the linker parameter has to persist through the click path.
- Inspect unwanted referrals. Payment providers, subdomains, and third-party checkout domains commonly create self-referrals or referral overrides in WooCommerce builds. Referral exclusions can help, but only when they match the actual user journey and domain structure.
- Compare outside GA4. Look at Google Ads clicks and cost, Search Console clicks and landing-page trends, and total conversions or orders. If those are stable while GA4 channels moved, you may be looking at reclassification more than performance change.
- Segment the problem. Check whether the shift is isolated to paid Google traffic, certain landing pages, one browser family, or a checkout path. That helps separate GA4 reporting updates from broken implementation.
The practical takeaway is simple: a channel shift in GA4 is no longer enough evidence by itself to call a marketing change. Treat (data not available) as missing attribution data, not as direct traffic and not as the same thing as (not set). Then check the WordPress basics that most often break attribution: Ads linking, auto-tagging, cross-domain continuity, referral handling, and parameter preservation through redirects and checkout.
Sources
- GA4 what's new
- Traffic-source dimensions
- Data not available in GA4
- Identify unwanted referrals
- Cross-domain measurement
- Direct traffic in GA4
- Search Engine Land recap
Know someone who would benefit from this update? Share this article with them.
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.
