Tags: Google Analytics 4

The main reason why Google Tag Manager is installed on a website is to set up analytics systems without needing a developer's help. In this article, we’ll look at how to install three core analytics systems on your website: Google Analytics, Facebook Pixel, and Hotjar.

At the time of updating this article, there are 77 types of tags available in Google Tag Manager. Of these, 75 are various pre-installed templates, such as Google Tag, Google Analytics: GA4 Event, Google Ads Remarketing, Hotjar Tracking Code, and Google Ads Calls from Website Conversion. There are also 2 types of custom tags: Custom HTML and Custom Image .

Google Tag Manager is one of those tools that can make your life simpler, more efficient, and in some cases, even bring in extra profit. "Why are you still struggling with tracking codes, writing massive specs, and waiting for your developer to implement them? Just use Google Tag Manager and make your life easier!" — This is something many marketers have heard before finally adopting this tool for their business needs. Sounds familiar? You need to add a tracking code to the website, so you write a task for the developer... and then wait... and wait... and wait?

One of the most common questions I hear from businesses is how to calculate the time between a user’s first visit to the site and their final conversion or purchase.

If you’ve ever analyzed Facebook traffic in Google Analytics, you’re likely familiar with the situation where you see numerous referrals from different Facebook subdomains to your website.

Among the three main ways to submit a request on a website — submitting a form, making a phone call, or writing in the chat — the first one accounts for the lion’s share and is tracked much more often than the others. Most internet marketers want to know exactly which sources bring visitors who submit forms, and that’s great. But beyond successful submissions, there are other types of interactions with forms, and tracking them helps us understand why some interested users never actually converted. Let's explore how to track the following user interactions with forms (listed from simplest to more advanced):