You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This traffic is being recorded in Umami, but it's being attributed to the wrong Channel. Since source=google and medium=cpc, this traffic should be attributed to Paid Search channel, but I have 0 visitors from that Channel according to Umami's dashboard.
Oher tools, specifically Google Analytics 4 is identifying this traffic as:
source/medium = google/cpc
Defaul Channel Grouping = Paid Search
Here are some screenshots for clarity. Time range is the same between tools, no active filters.
P.S. I know that GA4 is reporting 5+ times less users, my issue is specifically about Umami's broken channels attributions.
Code responsible for attributing traffic to a specific channel appears to be here:
Upon further inspection, I noticed that even in the official Umami Demo Dashboard, there are no visitors from any Paid channel on the dashboard, despite the clear presence of paid traffic.
Describe the Bug
When exploring website traffic per channels, it seems that Paid Search is being attributed to Direct or Organic Search.
Specifically, I use Google Ads with the following UTM (sampled values except for source & medium):
This traffic is being recorded in Umami, but it's being attributed to the wrong Channel. Since
source=google
andmedium=cpc
, this traffic should be attributed to Paid Search channel, but I have 0 visitors from that Channel according to Umami's dashboard.Oher tools, specifically Google Analytics 4 is identifying this traffic as:
Here are some screenshots for clarity. Time range is the same between tools, no active filters.
P.S. I know that GA4 is reporting 5+ times less users, my issue is specifically about Umami's broken channels attributions.
Code responsible for attributing traffic to a specific channel appears to be here:
Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
v2.16.1
Which browser are you using? (if relevant)
Chrome
How are you deploying your application? (if relevant)
Railway
The text was updated successfully, but these errors were encountered: