Category - Google Tag Manager

Form submission is one of the main ways to collect leads on a website. The simplest way to gain more insights is to send form submission data to Google Analytics 4. There are many ways to implement forms, which means there are also many ways to track them. I’ve already written an article on how to track user interactions with forms using Google Tag Manager . But that article didn’t cover working with the basic Form Submission trigger, which I want to walk you through now.

The importance of tracking form submissions on a website can’t be overstated — it’s one of the main ways users can leave a request. I’ve previously written articles on how to track form submissions in Google Tag Manager using a basic trigger or through validation inside the tag manager . Today, I want to show you another method — it’s suitable for forms where a thank-you popup appears after a successful submission. This method is based on using the Element Visibility trigger type. So, on the one hand, this article is about form tracking, and on the other — about working with the Element Visibility trigger.

Google Tag Manager allows you to track a huge number of events occurring on the page using standard triggers, but in some cases, they’re not enough. That’s when sending custom events and using the corresponding trigger comes to the rescue. With custom events, you can track any user action — from adding a product to the cart to pressing a specific keyboard button.

There’s no need to elaborate much on the importance of tracking scroll depth and time spent on a page. The more insights we gather about user interaction with page content, the better. Especially when approached from two angles: First, based on this data, you can understand how engaging and useful your content is for users. Second, you can segment users based on their interaction with a particular page. These segments can then be used, for instance, to create remarketing audiences. I’ve already written about scroll tracking using Google Tag Manager’s built-in functionality , and about how to evaluate content interaction by sending an event based on scroll depth and time spent on a page . Today, we’ll go through another solution based on a custom JavaScript script. This method allows you to capture both the maximum scroll depth and the precise time spent on a page.

I’ve already written in the first part of this article how important click tracking is for web analytics: Tracking Element Clicks on a Website Using Google Tag Manager . (If you haven’t read it yet — be sure to do so.) But even more important is tracking link clicks. When a user clicks a link, they might leave your site for another one — and you lose that visitor. Or they might click a phone number or email and contact you — which, of course, is much more pleasant. If you’ve read the previous article, you know that link clicks can be tracked using two types of triggers: All Clicks and Just Links . We've already covered the first one, so today we’ll focus on the second.

The three main ways users interact with your website are page views , scrolling , and element clicks. I’ve already covered the first two in previous articles. Today, let’s focus on the third.

Video production is not a cheap pleasure. And if you’ve created a video, it’s important to understand how users interact with it. If you're using Google Tag Manager in your work, tracking this is not difficult.

Scrolling is one of the primary actions users perform on a website. Tracking this behavior allows you to better understand how visitors interact with content on the page. Although GA4 can, by default, track 90% scroll depth using enhanced measurement events, this is often not enough to properly analyze user interaction. In this article, we’ll dive deeper into the possibilities of tracking scroll activity using GTM.

If you’ve worked with Google Tag Manager, you’ve definitely come across the Page View (All Pages) trigger — for example, when setting up Google Analytics 4 or Facebook Pixel . Many people mistakenly believe that this trigger listens for the page load event, but that’s not entirely true. In fact, Page View is an event that gets pushed to the dataLayer at the moment the GTM container loads (event name: gtm.js ).

In standard Google Analytics reports, there are three metrics that reflect user behavior: Bounce Rate, Pages/Session, and Average Session Duration. While Pages/Session is usually interpreted correctly, in my experience, many digital marketers misinterpret Bounce Rate and Average Session Duration. In this article, I’ll explain what bounce rate really is — and share a method to improve it (read: measure it more accurately).