|
Post by account_disabled on Jan 28, 2024 5:56:06 GMT
This means the tool may still have bugs, discoveries and improvements. do to prevent unassigned traffic include: Reporting identity Google Analytics 4 uses methods like User ID, Google signals, Device ID, and Modeling for tracking user data across platforms. Selecting the right method can help prevent unassigned traffic. Device-based is the recommended one nowadays. Event configuration Unassigned traffic can also stem from incorrectly configured events. Ensure your Google Tag Manager settings DB to Data spot-on. Events and parameters must also be tagged following Google’s guidelines. Other causes of unassigned traffic include: Events sent through regular tracking without session_start (h/t Antoine Eripre). Incorrect session tracking due to short user visits, ad blockers, or connection and data collection errors. Ad blockers and other devices Devices or ad blockers that hinder Google’s data capturing can also cause misclassifications of traffic, Himani Kankaria has found. Simon Vreeman noted mobile apps as a potential source of channel assignment issues. Use of audience triggers As Himanshu Sharma highlighted the use of audience triggers in GA4 can greatly increase the volume of unassigned traffic. If the event generated by the audience trigger isn’t tied to an existing session, perhaps because the session has ended or the criteria are met outside of the user’s current session, the source/medium might default to (not set) / (not set), which then appears as Unassigned in some GA4 reports.
|
|