Personizelypersonizely.net

All releases

Fix

Google Analytics 4 no longer shows test traffic as Unassigned

With the Google Analytics integration on, some visitors who saw an A/B test or personalization showed up as "Unassigned" in GA4 instead of under their real channel (Organic Search, Paid, Direct and so on). Their traffic source is now kept, so channel reports are accurate again.

What happened

The campaign events we send to GA4 had campaign_id and campaign_name parameters. GA4 doesn't treat these names as ordinary event data: it reads them as campaign tracking, the same as utm_campaign. Because no source or medium came with them, GA4 couldn't place those sessions in a channel and grouped them as Unassigned.

What changed

Campaign events now name the campaign with parameters GA4 leaves alone:

  • A/B tests: experiment_id and experiment_name
  • Personalizations: personalization_id and personalization_name

Everything else stays the same: the campaign_view event, variation_id, variation_name and control, and all widget events.

What you might notice

  • Sessions are attributed correctly from the moment your snippet updates. Sessions GA4 already processed keep the Unassigned channel. GA4 doesn't reprocess past data.
  • If you registered campaign_name or campaign_id as a custom dimension in GA4, it most likely stayed empty, because GA4 never received them as event parameters. Register experiment_name and personalization_name instead.
  • If you forward our events with Google Tag Manager, update the Data Layer Variables that read campaign_id and campaign_name to the new names.

See Google Analytics 4 and GTM for the full list of events and parameters.

  • Integrations
  • Analytics