How to Set Up Google Analytics 4 and Use It Effectively
In this blog, we’ll be not only answering a few of your questions about the upgrade to Google Analytics 4, but we’ll also walk you through how to set up this new version.
Keep reading to see how to navigate through this update to Google Analytics!
What is GA4?
GA4 is built off the backbone of the App + Web platform (aka Firebase). GA4 takes a different approach to data collection and reporting than what you are used to seeing in Universal Analytics (UA).
Google is pushing marketers to re-think how they interpret user data by changing to an ‘event’ based model. Data is collected and presented differently in GA4, as it focuses more on the events and interactions from the user’s journey.
It is also important to note that this will become the new default Google Analytics moving forward as new Google Analytics setups normally* require you to set up GA4 and not UA. Luckily, we can run GA4 parallel with a current UA setup so we can show you how to set this up.
*New UA Property setups are still available. Look for the ‘Show Advanced Options’ link after clicking ‘Create Property.’ You will have the option to create both GA4 and UA or create UA only.
How to Set Up GA4
It’s time to set up GA4 on your Google Analytics account.
1. Let’s get started by navigating to your Admin Settings within your Google Analytics Account. Under Property Settings, look for the ‘Upgrade to GA4’ link.
If the upgrade option isn’t available to you, you can click on ‘Create Property’ to create a new GA4 Property and skip ahead to step 4 after following the Create Property setup.
2. Click ‘Get Started’ to begin the setup process with Google Analytics’ setup wizard. Then you’ll have several options depending on your current GA setup.
If you are using the Google Site Tag to implement UA, the wizard will be able to enable data collection with your existing tags.
If you are not using the Global Site Tag, the following steps will outline how to enable data collection using Google Tag Manager (GTM).
3. In order to start the data collection, we’ll need to generate a Measurement ID for our new GA4 Property. The Measurement ID is similar to the UA ID. Enter the ‘Tag installation’ menu by clicking the right arrow shown below.
4. GA4 doesn’t have Views like its predecessor. Instead, it has Data Streams. The Data Stream expands beyond the Pageview Request as it measures certain events automatically such as Scrolls, Outbound Link Clicks, Site Search, File Downloads and more. Expand the Add Stream dropdown and select the app to track.
In this example, we’re tracking a website so we’ll select Web.
5. Configure your Data Stream by entering your Website URL and Stream name. Click ‘Create Stream’ when finished.
6. Now we have our Measurement ID. Copy or make note of the Measurement ID as it is required for setting up the GA4 Configuration Tag in Google Tag Manager.
7. Navigate to your Google Tag Manager Dashboard, create a New Tag, Select ‘Tag Configuration,’ and choose ‘Google Analytics: GA4 Configuration’ as the Tag Type.
8. Next, we’re going to add the Measurement ID. I recommend creating a Constant Variable for the Measurement ID instead of entering it manually. This will allow you to reference the Measurement ID for other Tags and prevent inconsistencies in the future.
Complete the following steps to create a Constant Variable:
A. Click on the Variable icon
B. Create a new Variable
C. Click the Variable Configuration to populate the Variable Type list
D. Select the ‘Constant’ Variable under Utilities
E. Enter your GA4 Measurement ID into the Value field and hit Save
9. Now that the Tag is set, configure your Trigger to fire on All Pages and hit Save to complete the GA4 Configuration.
10. You can test your GA4 Tag with Tag Manager’s Preview Mode or you can publish your container to push the new Tag live. Remember to publish your container after testing or your GA4 Property won’t receive data. Once the tag is live, you can view live hits by visiting the GA4 Realtime report. You can also view the published Tag in Google Tag Assistant.
Now that you’ve set up GA4, you can start using it to track users and their actions more effectively.
What if you’re having trouble getting website traffic period? Our digital marketing experts can help.
Quick House Cleaning Items after Upgrading to GA4
Like UA, there is a Data Retention setting within GA4 that lets you choose how long GA retains user and event data before automatically deleting it. I recommend bumping it up to 14 months, the maximum amount allowed. It can be found under Property < Data Settings < Data Retention.
Define Internal Traffic
In Data Settings, you will see another setting that should be familiar called Data Filters. Similar to the View > Filters setting in UA, GA4 gives you the ability to filter event data in your property. Let’s walk through excluding internal traffic by excluding our internal IP address.
By default, GA4 will automatically create a Data Filter to exclude internal traffic. However, it is up to us to configure the internal traffic to be excluded. Before we dive into the settings within the Data filter, let’s define the internal traffic.
- Navigate to Data Streams, select your stream and click ‘Tagging Settings’
- Select ‘Define internal traffic’ and click ‘Create.’
- In ‘Configuration,’ enter a descriptive Rule name and enter the IP address to be excluded.
- Hit Save.
Navigate to Data Settings > Data Filters and select the ‘Internal Traffic’ filter that GA4 created.
The Filter details don’t require changes with a standard IP exclusion. However, we have 3 options in ‘Filter state’ that are new with GA4:
- Testing: The filter doesn’t permanently change the data but can be identified with the dimension name ‘test data filter.’
- Active: The filter permanently changes the data.
- Inactive: The filter is not considered for processing the data.
Testing can be selected if you want GA4 to consider the data but not to permanently change it. When Testing is selected, the data from the filter can be viewed in reports by using the ‘test data filter’ dimension. This can be temporary to test your filter before making it Active. If you are certain that the IP Filter should permanently be excluded from the data, select ‘Active’ as your Filter state.
With data collection enabled and house cleaning items complete, now you can start exploring GA4. The dashboard and reports are completely different than UA and it will take some time to get used to. Explore the different reports as this will become the new long term standard for Analytics.
GA4 will look a little light at first, but there are many enhancements available that offer more robust reporting and analysis. The GA360 ‘Analysis Hub’ enhancement is available for free within GA4. The ‘Analysis Hub’ report takes a deep dive into user behavior, funnels, and pathing. It will be important to remember that GA4 uses Event based modeling and User scoped dimensions.
To not completely throw you in the deep end, here are some nuggets to help you get familiar with GA4.
Tips for Working with GA4
Mimic the Landing Page Report from UA
- Navigate to Life Cycle > Engagement > Pages and screen
- Select ‘Page path and screen class’
- Expand the ‘Event count’ dropdown and select ‘session_start’*
*Note – Sessions will differ when comparing GA4 to UA. Since GA4 processes data differently with Event based modeling, Sessions may appear lower when compared to UA.
View Reports by Medium (Comparable to Segments and Acquisition Report)
- Click the ‘All Users’ icon at the top of the page to edit the Build comparison
- Type ‘User medium’ into the Audience Name dimension field
- Select ‘organic’ from the dimension value dropdown and hit Apply
Other Mediums such as ‘cpc’ or ‘social’ can also be applied to reports. ‘User source/medium,’ ‘User source,’ and ‘User campaign’ are other available dimensions.
Session dimensions are available in GA4 but are less important than UA. Start using User scoped dimensions as GA4 is more focused on user interactions than session based interactions.
Setting Up Thank You Pages as Custom Events and Conversions
In GA4, Conversions are built from Events. GA4 Conversion implementation will be different if you’re used to the standard Conversion configurations in UA. However, if you’re a Google Tag Manager user this should be familiar.
GA4 will pick up some Events, but it won’t find everything you need to complete your GA4 configuration. For example, our thank you page from a contact form wasn’t being collected as an Event so we created a Custom Event in GA4 to start collecting this data.
- Navigate to Events > All events
- Select ‘Create event’
The Custom Event will be similar for those who use Tag Manager. The matching conditions are almost a mirror of the Trigger configuration in GTM. Here are the conditions to be configured for the custom event:
- Parameter: This is the referenced event. Similar to the Variables dropdown in GTM, you select the necessary event.
- Operator: Define the condition to trigger the custom event.
- Value: The value of the parameter.
We have two ways to track our thank you page from the available list of parameters in the dropdown. One being the page title (page_title) and the other being the page URL (page_location).
For the sake of testing, we created two Custom Events targeting both parameters but only one is necessary. Below are the two configurations created for our contact form thank you page. The page_location parameter details the entire page URL with protocol and all e.g. https://www.webtalentmarketing.com/thank-you/.
There are no other pages ending in /thank-you/ on the WTM website. In our case we chose the operator ‘ends with’ but keep in mind that if we had another page ending in /thank-you/, this would also trigger the Custom Event. Remember this when creating Custom Events so you don’t create false positives in your data. Also keep in mind that if you use page_title as the trigger, you’ll have to update it whenever you change the page’s title tag.
GA4 is slow to process the data in the reports. It will take some time for these Custom Events to populate in the All Events report. The Realtime report will render the event hits minutes after testing. Test your events and check Realtime to ensure your configuration is correct.
It took 24 hours for our Custom Events to populate in the All Events report. The wait was mandatory for the final step of turning the custom event into a conversion. From the All Events report, mark the event you wish to track as a conversion by switching on the toggle as shown below. This enables the event as a conversion and it can be viewed in the Conversions report.
Need More Tips for GA4?
We’ll be updating and adding more nuggets as improvements to GA4 are still being rolled out. Check back for more details on the latest enhancements and look out for our new piece coming soon about setting up Ecommerce Tracking for GA4!
At WTM, we’re experts at taking your digital marketing to the next level. If you want enhanced website tracking, better SEO, or paid search ads to improve your revenue, contact us now.