google / cpc as the source, (organic) as the campaign. Google hasn't fixed it since 2024. How to check whether you're affected and how to get campaign names back.
The source / medium says google / cpc, so GA4 knows the visit came from an ad. The campaign says (organic) or (not set). Since the summer of 2024 this shows up in a lot of properties, and as of October 2026 Google hadn't published a fix or an explanation.
Practitioners link it to consent: it mostly hits visitors who denied ad_user_data or turned off personalised ads in their Google account. Google hasn't confirmed that.
Before you blame Google, check the three things that cause the same picture and that you can fix yourself:
Then open Traffic acquisition, switch to Session source / medium, filter on google / cpc and add Session campaign as a secondary dimension. If (organic) or (not set) still shows up there, you're dealing with the Google-side issue.
The workaround is to send the campaign name yourself as a UTM parameter, next to the gclid. GA4 stores it in a separate dimension, Session manual campaign name.
By hand that's a lot of work, and it breaks every time someone renames a campaign. Google Ads has no ValueTrack parameter for the campaign name, so a tracking template alone won't do it. Jan Zdarsa's Google Ads script automates the same UTM method: it writes each campaign name into a custom parameter, sets a tracking template with UTMs, and runs every hour. It covers Search, Display, Shopping and Performance Max. Demand Gen and Video you still tag by hand. Keep auto-tagging on.
UTMs don't fix every session: some still show up as (organic) or (not set). Check the report every few months to see whether Google has fixed it on its side.
Installation steps for the script are on newmetrics.io. A related but different problem is (not set) as the landing page, see where those (not set) landing pages come from.
Want to talk about this?