By default, the time period for a session to be considered an “engaged session” is 10 seconds. This means that if a user is on a website for at least 10 seconds, the session is considered an “engaged session.” This threshold is quite low and it should be updated to a longer period. In GA4, the options for increasing the time period for engaged sessions are 10, 20, 30, 40, 50, and 60 seconds. We recommend selecting 30 seconds as the timeframe for determining an engaged session for a regular content website because that’s a more accurate capture of an engaged session.
Not adding an internal traffic filter
Internal traffic is broadly defined as website traffic from your internal team or office. For example, if a staff member visits your website while browsing on their computer at your office, that visit is considered a part of internal traffic. Internal traffic can skew your website data because you may see a lot of website traffic to your website, but a good portion of that traffic is your internal team members visiting your website and not clients visiting your website. To avoid collecting website traffic from your internal team and skewing your data, you can define internal traffic in your GA4 property by adding your office IP address to your GA4 property. Any website traffic that comes from such IP addresses will be excluded from your GA4 data, assuring accurate data collection in your GA4 property.
By default, the data retention period in GA4 is 2 months. You can change it to 14 months. This change lets you create exploration reports and extend the time of your report to the previous 14 months. If you don’t make this change and set the data retention period to 2 months, you’re only able to look back at 2 months of your historical data.
Not activating Google Signals
Google signals are session data from sites and apps that Google associates with users who have signed in to their Google accounts and who have turned on Ads Personalization. This association of data with these signed-in users is used to enable cross-device reporting, cross-device remarketing, and cross-device conversion export to Google Ads. If you activate Google Signals in your GA4 property, your GA4 property is able to better identify unique users on multiple devices. If a user logs in to their Google account on their computer and phone and visits your website from both devices, GA4 is able to determine that both visits come from the same user. This more accurate data collection approach lets GA4 capture a more precise reflection of your website performance.
Not creating custom audiences
One of the new, effective features in GA4 is the ability to create custom audiences. You can build audiences based on specific conditions. For example, you can build audiences of new visitors, returning visitors, visitors who have converted on your website, or visitors who have been to specific pages on your website and haven’t converted. Building custom audiences lets you dig deeper into the website behaviors of these specific audiences and find opportunities to improve your website performance. For instance, you can build a custom audience of those who have converted on your website and another custom audience of visitors who haven’t converted on your website. Once the audiences are created, you can compare the website behaviors of these two audiences and determine the differences between the two and find opportunities to convert more visitors who haven’t been converted into conversions.
Leave a Reply