We created an ActiveCampaign tag for the Google Tag Manager server container to help connect websites with ActiveCampaign. The benefit of using this tag for the server container is that you can fully integrate your website with ActiveCampaign without the help from developers. Now, you can set up the integration using the Google Tag Manager Server container. The ActiveCampaign tag for the Google Tag Manager server container allows tracking events, creating or updating contacts, or both.
We created a Mailchimp tag for the Google Tag Manager server container to help you connect your site to Mailchimp. This tag allows you to utilize the Google Tag Manager server container to track events, create and update contacts or even do both simultaneously. The main benefit of using this tag is that you can add new users. Previously, it was only possible with the help of backend developers. It means that you can connect your site to Mailchimp using Google Tag Manager. No developers required.
Klaviyo has extensive pre-setup integrations for websites built using popular CMS (like Shopify or woo-commerce). But what if you want to track additional events or have a custom site? In this case, there are two options: set up tasks for the developers or send website events through the server Google Tag Manager. This guide will show how to use a server GTM container to set up Klaviyo website event tracking.
How to set up Facebook Conversion API for BigCommerce using Stape Server GTM app.
Klaviyo Tag for the Google Tag Manager server container is a custom tag that will help you to add new users, send events and parameters from your site to Klaviyo. With this tag, you don’t need to ask your developers to set up the integration. Using this custom tag for the Google Tag Manager server container, you can integrate Klaviyo using the server container events and parameters. The power of Klaviyo cannot be underestimated when it comes to how much revenue it can make for your business, which is why we want you to know about this latest development from us.
In this article, I want to show you how to use Data Tag. This custom tag sends parameters from the Google Tag Manager Web Container to the Server Container. When used together with the Data Client for the Google Tag Manager server container, it allows sending data layer variables, custom parameters, and other data from the web to the server container. As a result, Data Client retrieves information from the Data Tag into the Google Tag Manager Server Events.
Using Facebook server-side tracking (Facebook Conversions API) is getting more popular due to its ability to prevent tracking pixel blocking by ITPs and AdBlockers. Another massive benefit of Facebook conversion API is that it increases FB cookie lifetime. If you haven’t yet implemented FB Conversions API on your site, follow this guide. In this article, I will describe how to set up Facebook events deduplication if you are using both browser and server tracking methods for your site.
Facebook Pixel allows you to track what users are doing on your site, collect remarketing audiences and create lookalikes. If the Facebook pixel is implemented correctly, it will feed relevant information to FB machine learning algorithms. FB ML will use pixel data to show your ads to people who are most likely to convert. For several years now, we could track events on the site via javascript code, Facebook SDK inside apps, or upload offline events. But how can you track users who installed Ad Blocker or track events outside the site? Or how can you extend a cookie lifetime? It can be done by implementing Facebook conversion API. This article will show you how to set up Facebook conversion API via Google Tag Manager Server Container.
Google released a Server-Side version of Google Tag Manager in 2020. Server-side tracking is more complicated than the web container set up, at least for now, since the idea and technology behind server tagging are entirely different from what we used to have on the web. But server-side tagging will give your site huge benefits. Server-side tagging is getting more popular due to its ability to track people using AdBlockers, browsers with ITPs, and other tracking restrictions. The purpose of this article is not to convince you to start using server-side tagging (there is another blog post that describes the main benefits of server-side tracking). I assume that you’ve already decided to implement server-side tagging on your site. This blog post will show you how to check whether Server-Side tracking for GA4 and Facebook conversion API was set up correctly.
Want to track the results of your Google Ads (AdWords) campaigns? Then you need to see what users were doing on the site after they clicked on your ad. The typical user actions include submitting a contact form, adding something to a cart, or completing a purchase. What if you decided to move your tracking to a server-side? In this article, I’ll show you how to set up Google Ads (AdWords) conversion tracking using Google Ads tag for the Google Tag Manager server container.
Website page speed optimization was one of the essential benefits that marketers and web developers saw when the first version of Google Tag Manager was released. It was supposed to happen because tracking scripts would no longer be hardcoded but would be added through Google Tag Manager. So, does the GTM web container speed up your site? This article will showcase how moving to the GTM server from Google Tag Manager Web Container can speed up your website. Please note that you won’t see any pagespeed improvements if you’ll combine server and browser tracking. For example, your site’s pagespeed won’t increase if you use both Facebook pixel and Conversion API. In this case, FB pixel will still work in user’s browsers and slow your site.
For Google Analytics 4, Google still has not provided free options to export raw data to BigQuery or any other database for that matter. But what if you don’t have plans to migrate to GA4 and want to get the benefits of BigQuery raw data? I decided to solve this question with GTM Server Side tagging and created this how-to article for you.
A common issue for data analytics and sales managers is the accurate tracking of user behavior and conversions. And often, they might face a problem that seems to have no solution. Or alternatively, there are no developers who can do this, and the next update of the site is planned only for next month.
Using Facebook Conversions API, you can send events to Facebook Event Manager. That is the perfect alternative to Facebook SDK because Conversions API speeds up page loading and helps track users more accurately. We created a Facebook tag for the GTM Server-Side container that uses Facebook Conversions API to track events.
What if you are faced with spam in Google Analytics reports? Does it mean that someone can access your Google Analytics accounts? Or maybe someone can modify data inside your GA? How can you prevent it? There are two main types of Measurement Protocol spam: referral traffic and events spam. More rarely you can see spam in languages, keywords, URLs, transactions, and so on. In this article, I will explain what Measurement Protocol spam is and how you can prevent it with the help of Google Tag Manager Server-Side tagging.
In this article, I will describe the advantages of using GA4 and GTM server tagging. You can use it as a step-by-step guide on how to send events to GA4 via the GTM server container. As for eCommerce/enhanced eCommerce, I will cover it in another article.
Zapier is the most popular software that helps connect your apps and automate workflow. It became the number one tool in this niche, but using Zapier may be too expensive for some businesses since it limits the number of tasks and events you can send in each plan. This article will explain how you can use Google Tag Manager Server-Side container to replace one of the most popular Zapier features – automatic Slack notifications.
Don't miss out on the benefits of server-side tagging for your WordPress site. Learn how to set it up with Stape plugin in this quick and easy guide!
In this article, I will describe how to set up a custom subdomain within your Google Tag Manager server container. The main advantage of a custom subdomain inside the Google Tag Manager Server container is that it helps to bypass Intelligent Tracking Preventions, AdBlockers and increases cookie lifetime for users browsing in Safari. Pixels will be loaded from your subdomain and run as the first-party.
Collecting data about your website visitors is critical for analyzing and improving the online business presence, reaching users, and converting them into customers. However, collecting data is becoming more problematic because of Intelligent Tracking Prevention, AdBlockers, and a decrease in cookie lifetime. Google Analytics and other similar tools will start seeing fewer data about your website visitors and giving you less information to analyze.
Check what GTM server-side tracking is, how it helps track data accurately, comply with data regulations, and more in our comprehensive guide.
