What the diagnostic checks
On 30 July, Google Analytics added a data-quality indicator named "Campaign data accuracy is affected by missing URL parameters." It appears inside individual reports rather than as a property-wide banner, and it fires when landing-page URLs arrive carrying a GCLID but without the GBRAID or gad_ parameters that Google Ads appends.
Those parameters do specific jobs. GBRAID, introduced in March 2022, carries campaign data without linking to an individual user, and works as a fallback where GCLID cannot, such as when a user denies ad_user_data consent. gad_source identifies the ad source and gad_campaignid identifies the campaign that drove the click.
Three mechanisms strip them before the analytics tag can read them: redirect chains that drop parameters somewhere between the click and the final landing page, CDN or security filters applying canonicalization rules mid-journey, and tags firing before the parameters are readable on the page. Google's documentation adds a fourth failure mode of its own, requiring gad_ parameters to sit before any hash fragment in the final URL.
Why the organic misfile is the expensive one
Losing the parameters produces two different outcomes, and they are not equally dangerous. The first shows up as "(not set)" in campaign reporting, which looks broken enough that somebody investigates it.
The second credits the paid click to organic search. Measured organic performance rises, return on ad spend falls, and no error appears anywhere in the interface. Budget then moves toward the channel that appears to be outperforming, which is the channel that was handed the other one's traffic. The error funds its own repetition.
Google says fixes take 24 to 48 hours to register, and the diagnostic may continue displaying during that window. Access is split: every property role can see the indicator, while Editor and above can act on the remediation controls, including a "View URLs" list of the affected page paths.
What to do about it
Trace one landing page from click to tag
Take a live ad, click it, and watch what survives. Compare the URL Google Ads appends against what the analytics tag finally reads, checking each hop in the redirect chain and anything your CDN rewrites along the way. One traced page usually explains the pattern for the whole account, because the stripping is almost always a shared piece of infrastructure rather than a per-page fault.
Check who in the property can act on it
Viewers, Analysts, and Marketers can see the diagnostic but cannot use the remediation controls. If the person watching your reports is not an Editor, the indicator gets noticed by someone who cannot open the affected-URL list, which is how a flagged problem sits unresolved for a month.