|
We refer to the following cases. Unallocated ga4 Why does unallocated traffic occur and how to fix it Well, now that we know that unallocated channels in Analytics 4 cluster users or sessions whose source the platform does not recognize, let’s see where it will situations arise and how to resolve them. Analytics 4 is not configured correctly: The basic thing is to make sure that the Analytics 4 implementation has been done correctly. It is recommended that we implement tags through tag manager or gtag.js and place the implementation code correctly. It is important to ensure that when someone visits the website, the session_start event is triggered, which contains information that determines ownership.
Google it. UTM parameters: UTM parameters are missing or misconfig Telegram Users Number List ured in the URL used in the campaign. It is important that when we use links for campaigns and need to use UTM, this is done according to Google's order and logic. In the case you'll see below, this is because the newsletter platform doesn't use URLs with UTM very well. Unallocated Analysis Other causes and solutions of unallocated traffic The cases and solutions presented above are the main ones, especially the misuse of URLs with UTM parameters. That said, there are other situations where Analytics 4 can classify traffic in unallocated channels, and the solution is different.

Other cases and solutions for unassigned traffic: Consent mode: In this case we send the event to Analytics 4, but the user does not accept the cookie and the platform does not recognize its origin. You have two options, accept this portion of unallocated traffic as is natural since you have implemented correct cookie management, or you can stop sending events to Analytics 4 if the user does not accept cookies. Actions/events sent by the server or related third parties: This occurs when Google Analytics cannot determine the source because at some point, the user's information and events related to their activity on the website have been lost.
|
|