How do you know if your website is successful? Your GA4 analytics tool can tell you that if you set up conversion tracking.
GA4 conversion tracking and creating goals in Google Analytics 4 are easy, and there are many ways of doing it in GA4. Let’s explore 3 methods to track conversions on your website, at Google Analytics 4.
🚨 Note: Google Analytics 4 is the iteration of Google Analytics’ Universal Analytics. Please update your Analytics and ensure you have linked your accounts.
Master the basics with our FREE GA4 Course for Beginners
Here is an overview of what we’ll cover:
- Define a Pageview as Conversion, by modifying the page_view event
- Create a custom event with GTM
- Use eCommerce tracking to send a Purchase event
Let’s get started.
Define a Pageview as Conversion, by modifying the page_view event
💡 Top Tip: Keep your GTM, GA4, and your website pages ready to navigate smoothly throughout the demo.
How do we mark a particular page view as a conversion? Our Google Analytics Debugview shows real-time results, tracking everything.
Let’s suppose we want to track when someone signs up for our merch and news. We want it as a conversion. So we head towards the sign-up form at the Demoshop.
We sign up with my name and click on Submit, to elicit a response/ data from my Google Analytics4, DebugView.
The website shows a success page for my sign-up submission. How did Google Analytics record it?
When we sign up on a form from our website, the success page pops up and Google Analytics records it as a page_view event.
The page_view shows parameters on page location indicating ‘sign-up-form/success/’.
This is what we want as a conversion to track. To mark it as a conversion, we head to my All Events report on Google Analytics.
It shows us a record of all events that occurred.
You can click on the event and fetch more data about the event. Here, we click on page_view and we avail data about all page view events.
It can also display data about Page path, User engagement, etc.
It’s easy to mark it as a conversion by switching your option at the Mark as conversion column. But this would lead to marking all your page views as conversions. However, we don’t want this.
We only want the particular event to be marked as a conversion.
First, click on Create event in the top right corner of the Analytics site to create your new event.
Give a name to the event. Here, we’re naming it sign_up_demoshop.
Second, input the conditions under which the page view is recorded on Google Analytics. We’ve applied 2 conditions – one, where event_name equals page_view and another when page_location contains /success/.
Finally, you can choose to copy the parameters from the source event from the Parameter configuration. Here, we’ve chosen to copy it.
Let’s go ahead and create this event by clicking on Create.
🚨 Note: This event would show up on your All Events page when some data is recorded, and it’s registered by Google Analytics 4.
We’ll try testing this by signing up at our Demoshop again. Let’s go to DebugView at our Analytics and we can see the events pouring in. We notice the sign-up-demoshop event is recorded.
You can click on it to view the Parameters and User properties of the event that just occurred.
When the event is present in your All events list, you can click on the switch and mark it for conversion. Once done, you’ll be able to track the particular page as a conversion.
Your conversions are very useful in your User acquisition report. The user acquisition report tells a lot about where your users come from, average time event counts, and conversions.
User acquisition can tell a lot about how users interact with your website and has data on Engaged sessions, Event counts, Conversions, and much more.
This is the first method to classify a pageview as a conversion.
Create a Custom Event with GTM
Welcome to method number two. This time, we use a little bit of Google Tag Manager magic. Let’s get started!
Considering that we want to record the success of a sign-up form from our Demoshop, we’re going to create a trigger and a tag, connect it to our web page and let Analytics take care of recording the data for us.
To start, head over to the GTM workspace and click on New to create a generic formSubmit trigger.
We’ve named it ‘formSubmit’ for easy identification and have set the trigger type to Form Submission.
Save the trigger created. Let’s test this by going over to Demoshop and signing up on another form. This time, after submitting the form, you can see the trigger being fired on Google Tag Manager.
To ensure that your trigger doesn’t fire at any other event, you can refine your trigger settings. For this, go through the variables of the formSubmit to narrow it down.
Find the Form ID & copy it. You can head over to the Manager Assistant and check out the variables.
Scroll down and you’ll be able to find the FormID. For us, it’s ‘gform2’.
Here, our Form ID is ‘gform2’. We copy this ID and head over to the triggers settings. Note that we’ve established conditions for the trigger to fire only when Click ID equals gform2.
Go to the trigger that you created, select the ‘Some Forms’ option, and specify the condition when the trigger is to be fired.
🚨 Note: If you don’t have a Form ID variable, you can always choose another variable from the list to refine your trigger.
We will rename this trigger to formSubmit – sign up, because, now, this trigger will fire only after the sign-up form has been submitted.
In addition, you can select the Wait for Tags option if the user is redirected to another page. Selecting this option ensures you are giving Google Analytics enough time to record the event when the page loads and fires the trigger.
Moreover, you can state the conditions when you want it to be fired. We have set the conditions such that the trigger will be fired if the ‘Page URL matches RegEx.*.
Now that the trigger is set up and ready, we’ll go ahead and connect it to an event tag.
To create a new tag, hover over the plus sign, choose tag type as Google Analytics: GA4 Event, and Configuration Tag as GA4 – Config / Pageview – All Pages.
We’ve named it GA4 – Event – Sign UP Form.
Now, we will go to Event Name and Event Parameters. You are free to choose any event name or event parameter, but there are some predefined parameters from Google Analytics.
Moving forward, we’re using the predetermined parameter called method that is specific for Sign Up events. Back at our Google Tag Manager, we input the Parameter Name as method and the Value as form.
Don’t forget to scroll down and connect the formSubmit – sign up trigger to the GA4 – Event – Sign UP Form tag.
Click on Save.
After all this, we reach the Demoshop page again and submit another Sign-up form. This time, after submitting, we can now go to Google Analytics DebugView and analyze the events that have occurred on our website.
We notice the sign_up_demoshop has fired and a few moments later, the sign_up event shows up on the timeline.
If you take a closer look into the Parameters of the event, you can find that the method has a value of form.
Having the trigger fired, you can see that this event could be a scroll, a click, the visibility of an element, or anything you want to track. Thus, the possibilities for Google Tag Manager working for you are innumerable.
Bringing this to an end, you can head over to the All Events page and find the sign-up event and mark it as a conversion.
Now, let’s go to the last method of setting up GA4 conversion tracking – on eCommerce websites.
Use eCommerce Tracking to Send a Purchase Event
Google Analytics can track eCommerce websites for you.
🚨 Note: Make sure you set up your GA4 settings properly for your eCommerce sites.
ECommerce events on Google Analytics and Google Tag Manager are audited and you can find the data under Analytics → Reporting → Monetization → E-commerce purchases.
Under this section, you can review all the conversions and purchase activity that has occurred on your website.
At our end, we have a demo Order Form and a summary of an order for a product worth $11.99. Clicking on Submit gives us the Thank You page.
For an eCommerce conversion to occur in our Google Analytics, we need to set up a data layer at the GTM, so that specialized data about the purchase can be recorded and reported.
The data layer provides your GTM and GA4 with the data in the background for the tools to analyze and report to you through the screen.
Google Analytics4’s documentation on setting your data layer is a code so that the data can be recorded in the background. Google Analysis provides more to eCommerce tracking than just tracking purchases.
The recommended events section has a predetermined event called sign_up and it will trigger when someone signs up on a form. The parameter for this trigger is method.
For this demo guide, we’re going to stick to tracking purchases. This code would need to be deployed on your website on the thank you page, for Google Tag Manager to have that data available, and then send it on to Google Analytics 4.
If your eCommerce shop is on Woocommerce, Shopify, or such eCommerce stores, you might find a plug-in available for you. Having a plug-in can save the time and hassle of entering the code into your GTM and GA4. It can directly send over the data to your GTM and GA4.
To try this out, let’s head to our Demoshop’s thank You page and edit the code.
We’ve already got our code snippet into the code editor, and we’ll save it.
Heading to the Tag Assistant, you’ll be able to find the code in the data layer.
Go over to the purchase → Data Layer. The data layer is set up. This information is ready and can be sent to Google Analytics 4. The event key in predetermined events at Google Tag Manager for eCommerce sites is ‘purchase‘.
You need to follow the syntax to ensure proper formatting. In GTM, you’ll have to first build a custom trigger.
It is built such that it will fire only after the page loads. Giving it time to load the data about the order on the data layer, and then fire.
The trigger is named custom – purchase. Choose the trigger type as Custom Event and the Event name purchase. You can choose to set it to All Custom Events because we don’t need to narrow our report.
After all this, we’ll create a Google Analytics 4 tag. Name it GA4 – Event – purchase.
This is an event tag, so make sure you choose the Google Analytics: GA4 Event, from the list of tags presented to you.
We will proceed to connect to the Configuration tag followed by the Event Name. Don’t forget that the Event Name is equal as per the documentation, in this instance, it’s {{Event}}.
Next, we need to add the Event Parameters. We want to add everything we want to measure from the purchase. Here, we’ll enter all the parameters from hierarchy 1.
The parameters we’ve applied are as follows:
- transaction-id
- Affiliation
- value
- tax
- shipping
- currency
- coupon
- items
To pull the information from the data layer, you need to set up data layer variables. Let’s try setting up the variable for transaction ID.
Back at our tag, we enter the Parameter Name as transaction_id and the value/data layer variable is customized by generating a new variable.
The variable is called dlv – transaction_id. Remember to save the Variable Type as Data Layer Variable.
Your Data Layer Variable Name has to follow the same path as the code. In this instance, its ecommerce.purchase.transaction_id.
Once you’ve set it up for your transaction ID, you’ll have to follow the same for the other variables and ensure the tag is complete. Having completed this, save and you’ll be ready to send data to Google Tag Manager.
Once you’re done, pull a quick review of the tag settings and connect it to the custom trigger that you just created. Once done and saved, you can test this by hitting the preview button.
To test our exercise, we head back to Demoshop and go to the Order Form. We’ll click on Submit and this time the Google Tag Assistant will record the tag being fired.
You can take a look at the event from the Google Tag Assistant and find more details about the event.
Meanwhile, in the Google Analytics 4 DebugView, we can observe the key events that have taken place on our website. Notice that the purchase done is marked as a conversion.
You can pull up more data about the purchase as you click on the event. This opens up a new window with Parameters, User Properties, and Items.
Under Items, you will be able to see the data layer parameters – coupon, currency, item, etc.
🚨 Note: Purchase events are by default marked for conversion at Google Analytics.
This is the third way of creating a conversion inside of Google Analytics 4 with the help of Google Tag Manager and the data layer which you need to implement.
So, there we go! Those are the 3 ways of setting up your GA4 conversion tracking!
Summary:
We hope this showed you three novel ways of setting up GA4 conversion tracking. However, you need to think of the best way that works for you.
If you want to track a pageview as a conversion, you can create a new event off the page view. But, if it’s not a pageview and it’s more specialized like a form submit, then you might want to send it at an event.
To get the most out of Google Analytics 4, check out our guide on GA4 metrics and get a better understanding of your user behavior.
Did you try setting up GA4 conversion tracking? Which way of setting it up do you prefer? Let us know in the comments below!
Master the basics with our FREE GA4 Course for Beginners
Wow, this is very helpful! Huge thank you!
Do you know how I could create an event that fires if someone is on the site for more than 30 seconds?