Back to our generic link click trigger. Save it and refresh the preview and debug mode by clicking the Preview button in the GTM interface again. Go to the page where you wish to track links. Click any link on a page. It was listening to link clicks on a page and once it spotted one, it pushed a Link Click event to the Data Layer, and, therefore, it became visible in the debug console.
To sum up, we created a generic link click trigger because we needed to have the link click auto-event listener enabled on a page. If at least one link click trigger is enabled on a page not activated but just waiting for a moment to fire , the link click listener becomes enabled in the background. In order to create more precise triggers, we need one more ingredient, variables. What are those?
They are little pieces of information that can be used both in Tags and Triggers and, in fact, in other variables too. For example, Click ID.
You can use it as a trigger condition e. Click Link Click event and go to the Variables tab of the Preview mode. Keep looking for anything related to clicks. Now go to the Data Layer tab o the preview mode while Link Click event is still chosen. Because built-in click variables are not enabled in the Google Tag Manager interface. So what? If some data is not available as a variable in GTM, you cannot use it in your triggers.
A panel will appear on the left side. Then go to your website and click any of the menu links. Actually, click at least two of them. Return to the preview mode and you should see Link Click events in the preview mode. Click the first Link Click event and go to the Variables tab of the preview mode. Then click on the second Link Click event. I am currently looking for some variable that I could use to distinguish a menu link click. I want to fire it precisely on a menu link click.
I will use this in my Just Links trigger. Important: in your case, the classes might be different. Then you should be looking for other variables or go more advanced with CSS selectors.
Select your existing GA 4 Configuration tag and then enter the event name. Its value is up to you. Any of the following options are perfectly fine:. These are just some of the examples. Since we are working with a custom event, we can name it whatever we want as long as we follow the limitations of name length , for example.
But this time, sending just the event name is not very useful. How about we also send the name of the menu item and the URL? We could do that by sending additional event parameters. I made these parameter names up and you can do it too. To send custom parameters, you must expand the Event Parameters section in the Google Analytics 4 event tag and then click Add Row. Enter the name of the first parameter. Insert it as well. If you want to send more parameters, you are free to do that.
You can send up to 25 custom parameters with a single event. The next step in this workflow is to update our trigger and then assign it to the Google Analytics tag.
We want our tag to fire not on all clicks, but only those that are menu links. In Step 2, we have already identified the main characteristic of the menu link. In Google Tag Manager, go to Triggers and find the trigger that you have created in step 1. Also, change its name. Save the trigger. Assign it to the GA4 tag. You can do that by clicking anywhere on the Triggering section of the tag and then select that Just Links trigger.
Go back to the Preview mode and click those Link Click events. Now, you will need to go to Google Analytics 4 and check the DebugView. You will learn more about that in this blog post. Unless you register those parameters as custom dimensions in Google Analytics. After you register these dimensions, you will start seeing them in the reports within 24 hours.
Learn more about custom dimensions in GA4 here. Some clicks might be more important to your business than others, thus they should be configured in Google Analytics 4 as conversions. But that does not mean that buttons always require this trigger. Many buttons are just links that are coded to visually look like buttons. So you can always try to use the Just Links trigger first before trying the All Element trigger. However, I want to show you what the All Elements click trigger is and why is it different from the Just Links.
As you can guess from its title, All Elements tracks clicks of all elements on a web page including links. You can try it for yourself.
Leave all the settings as they are and save the trigger. This means that the All elements click auto-event listener has been enabled and all clicks are now being tracked. We could definitely make use of some parameters here, for example, gtm.
If we want to use it in the GTM tag, trigger, or another variable, we need to turn this data point gtm. Luckily, all the built-in click variables were already enabled in one of the previous chapters about menu link clicks.
Just links and All elements triggers share the same set of click variables. Every time a visitor adds a product to a cart, we can send an event to Google Analytics. This button has no link, therefore, Just Links trigger will not help. In order to create a precise trigger that tracks clicks of only the Add To Cart button, first, we need to click that button and inspect what kind of data is available in the Preview and Debug mode.
Scroll down and keep looking for all the click-related variables. Google Analytics 4 is the latest GA version, launched in October With it, Google hopes to provide smarter insights so that businesses would take better marketing decisions and improve their ROI.
Starting October 14th , GA4 properties are the default when you create a new property. That is because data collection principles of these properties are a little bit different than that of previous Universal Analytics properties. And these differences also bring new options and terminologies, like Data Streams. A Data Stream is a data connection created specifically to track an app or a website. GA4 properties do not have views like regular Universal Analytics properties so they use Data Streams instead.
So to have the data available in a Google Analytics 4 property, you need to add Firebase to your app and link it to Analytics. After this the GA4 property will start getting data. And all of this without a tracking property ID. For GA4 properties using Web based Data Streams , the data collection principles are the same as for Universal Analytics properties, as they use the gtag.
This is a headache as I want the UA tracking code and cannot find it for love or money. If they want to add someithing then by all means but do so, but not go changing things for the hell of it. Not everyone has hours to spend researching how to do one simple task. Time is money for me and I have wasted loads of time and have simply got no where. You could read the last part of the article for more details. For the default Gtag. I need to integrate with a payment platform that only accepts the UA format.
How to proceed if this ID no longer appears in the new version of analytics? If your payment platform accepts only old UA formats, then I would suggest to create a Universal Analytics property instead of GA4 property. Thank you a lot and God Bless You.
Thank you Carol so much! This new GA4 update was driving me crazy. The most incredible is the lack of information about it from Google itself. Hi Carol: Awsome details. Thank you. Does it mean that the Universal Analytics property generated here is for websites only? Yes, that ID is only for websites. Hi Carol: Thank you so much for your reply. I am still lost.
I am not a developer. Rather I am an author and trying to publish my books as apps. I am using an app builder program which allows me to put in Admob banner ad unit id. I created the firebase account and registered the app. It gave me a banner ad unit id. Which I included in the app before uploading to Google Console. The apps are showing but nothing is being reported. I only have an. I do not have a project file. Analytics is asking:. I skipped these two steps and I am seeing ads on my app and people are downloading it.
It has been several days. I tried adding json file to java option but no still nothing. The main difference in setting up different types of tags is will be in configuring what the tag fires on. The next step is to select or create a trigger for the tag to fire on. You will need to set the fire on conditions for your tag.
I have included a few examples of the different types of triggers for different events on your site. It is a good idea to check that your events work as you intend. To view results immediately you can preview your Google Tag Manager events using the preview feature and carry out your event action to see whether the tag fires successfully.
Within Google Analytics you can also see events fired within the last 30 minutes by going to the Real-Time section and then Events section. Goals can also be set up in Google Analytics based on your events. To do this login to your Google Analytics account and follow these instructions:. Google Analytics Event Tracking is a valuable addition to measuring user interactions on your website. It can be used in combination with traditional Google Analytics goals to measure micro or macro conversions on your site.
Using Google Tag Manager and Tag Manager events means it is now easier for you to set up and control the events you want to track or you can still change the code on your site manually to add events if you prefer.
If you need help with your Google Analytics don't hesitate to contact us. Using Google Analytics event tracking. You can set up event tracking manually on each link or use Google Tag Manager to automate your event tracking.
What can Google Analytics event tracking be used for? Some of the typical uses for event tracking are listed below: Tracking outbound link clicks to other websites. Understanding how many users clicked on mailto email addresses or click-to-call phone numbers. This can help you to better understand the number of enquiries you are getting from your site.
Tracking PDF and other media downloads. Measuring interactions with video content, such as time spent watching a video. Collecting data about how many users filled in and submitted a form, although I would always recommend sending users to thank you pages whenever possible. Google Analytics Event Tracking in Google Analytics — Examples of tracked event categories What to consider before you start To use event tracking you will need to have Google Analytics installed on your website.
Before you jump into setting up event tracking, it is important to consider the following points: There are two versions of Google Analytics tracking code. Check whether you are user the older Universal Google Analytics Analytics. I recommend migrating to the newer version of Google Analytics and Google has written a guide on how to migrate to using gtag.
Decide on which elements of your site you want to track , whether it is PDF downloads or clicks on outbound links. Adopt a consistent and clear naming convention for the different action, label and category options available to you when you are setting up event tracking.
Every name you give to each category, actions, and labels appears in the event tracking reports. Decide whether you want to set up auto-event tagging or manually tag links on your site.
If you have a lot of documents and page elements to track it may be worth setting up Auto Event Tagging and using Google Tag Manager Events. How does Google Analytics event tracking work? Action Required is the type of interaction, such as downloading a document.
Label Optional is useful for summarising what the event is about, such as clicks on navigation menu options. How to set up Google Analytics event Tracking Depending on the number of events you would like to track, or the level of control you would like to have on the tracking parameters for your events, you can setup up auto event tracking, or manually tag links on your website.
Auto event tagging will fire on the following: When users click on links. Clicks on any type of page element. After a certain visit duration or at timed intervals. On submission of a form. Step 4 — select what the event tag will fire on The next step is to select or create a trigger for the tag to fire on.
Trigger for measuring clicks on an email address link An example of a completed trigger for an email address clicked link is below. To do this login to your Google Analytics account and follow these instructions: Go to the property where you want to set up the goal Click on Admin and then go to Goals and click on Add New Goal Give your goal a name and select the event goal radio button option Fill in the fields with the attributes for your specific goal.
Remember to select Equal to, Begins with or Regular Expression options based on your event attributes. Category Action Label Value Save your Goal Remember to complete a test goal so that you have data and then come back the next day to check your event goal works Screenshot showing how to create an event-based goal in Google Analytics Conclusion Google Analytics Event Tracking is a valuable addition to measuring user interactions on your website.
Have you just learned something new? Then join the 80, people who read our expert articles every month. This field is for validation purposes and should be left unchanged. Enjoy this article?
Subscribe for weekly insights. You may also like. Contact us. We use cookies to understand how you interact with our website.
0コメント