Ad Blocking is in no way a one-way street, and the impact of tracking script blocking extends far beyond just advertisements.
Many have been made about ad blocking apps and extensions these days, but what do they really do for users? One reason why people might consider installing adblokers on their device or browser is because of annoying ads and pop-ups that appear on the sites. But not only ads can be affected by AdBlockers.
In this post, I will discuss how adblockers can affect tracking scripts that are placed in Google Tag Manager. I will also show how to avoid GTM blocking by adblockers using server-side tracking.
This post is not encouraging anyone to track users without their permission. You should always respect user decisions and ask for their consent before firing any tracking scripts.
Some people might use GTM for non-tracking purposes (like implementing schema markup or adding a chat on the site). If GTM is blocked, it might negatively impact organic rankings or customer experience.
Adblocker is a software or browser extension that can alter or remove advertising content from websites. It can block advertising, tracking, and other content using different methods. One of the methods is by targeting the URL where this content originated.
By default, most ad blockers prevent only ads from being shown. It can be done either by knowing the URL of the advertising network (because of a specific database of URLs that is part of advertising networks) or using the names of tags in the code.
The default setup of the adblockers won’t hurt Google Analytics or Google Tag Manager. They will block only ads on the page that the user visits.
But users can adjust settings and ask adblockers to remove any tracking scripts. In this case, Google Tag Manager won’t work. It means that all scripts added inside the Tag Manager won’t work. If you add Google Analytics scripts outside of Google Tag Manager, it will be blocked as well.
In the past few years, more and more people have been using adblockers to escape advertisements. Since advanced settings of AdBlocker can affect GTM, your tags will be affected too. People might not even know that when they enable the advanced setting of ad blockers, they might block, for example, the ability to contact support via chat on the site.
2. Log in to your stape.io account and choose a container-> Click Power-ups -> Click Config near the Custom web GTM loader.
3. Paste your Web Google Tag Manager ID. Once you’ve clicked update, you will see a modified GTM code that you’ll need to update on your website.
Two changes were made:
These changes will help to avoid Google Tag Manager blocking by ad blockers.
4. Update the GTM code on your site with the GTM code you copied on the previous step.
Enable adblocker and use the console to check if GTM is loaded. Google Tag Manager code was not blocked, but you might see that the Google Analytics request was blocked. In the next step, I will show how to prevent Google Analytics from being blocked.
5. Server-side Universal Analytics makes data more accurate compared to web UA. But most Ad Blocker or Brave browsers will still block ss UA requests. There is a way to make UA even more resistant to tracking prevention mechanisms.
This method has a few steps:
6. Add Data Tag from the GTM Web template gallery.
7. Create a new tag -> Tag type Data Tag -> Select event name -> Add you GTM server URL ->Add preview header -> If you enable Send all from DataLayer and Send Common Data, it will allow Data Tag to send all information it can find in the web GTM to the server GTM. Add event and user data you want to send to the server container.
8. Open server container -> download Data Client from the Github -> Open template tab and click Add New in the Client Templates section -> click Save.
9. Create a new Client -> Client type Data Client
10. Create a new Tag -> Tag type Universal Analytics -> Add Universal Analytics ID -> Add client_id.
Universal Analytics tags won’t work without client id.
You have two options here:
11. Create a trigger for UA tag -> Trigger type Custom -> Client Name equals Data Client
12. Open the preview mode of the web and server GTM containers. You should see that Data Tag triggered in the Web container and UA tag triggered in the server container.
13. If you see that both tags fired, publish web and server containers. Now you can test the setup with adblocker.
Enable GTM server preview mode again and copy the preview header by clicking three dots at the top right corner -> Click send request manually -> Copy X-Gtm-Server-Preview HTTP header.
Open stape.io account and choose a container -> Click Power-ups -> Preview Header config -> Paste preview header you copied on the previous step -> Save.
Open your website with enabled adblocker. Open console and check if Data Tag requests worked.
You should also see that UA tag triggered in the Server GTM preview.
14. To test that Universal Analytics worked, you can use UA Real-Time reports.
After you've finished testing, do not forget to remove the preview header from your stape.io account.
Similar to UA, Google Analytics 4 data can also be affected by tracking prevention software. There is a way to overcome such situations by using stape's custom GA4 loader. If you already set up a custom web GTM loader, then the GA4 loader should also work. All you need to do is open your site, go to the Network tab and check the GA4 request. It should look like the screenshot below. If you did not set up a web GTM loader, just follow these steps to enable custom loader power-up.
Google Tag Manager is not a tracking tool by design and can be used for many other purposes other than tracking user behavior on the site. That is why blocked GTM can negatively impact not only Google Analytics, Facebook, or any other tracking tool but can go far beyond it.
In this blog post, I showed how to use server-side Google Tag Manager to avoid GTM blocking by Ad Blocker. Hope this method won’t be misused. In the end, it is up to you whether or not to set up Google Tag Manager as described in this article.
All it takes is a few simple questions. Click Get A Quote, fill up the form, and we will send you a quote.
By the end of 2024, Chrome and Chrome-based browsers will be done with third-party cookies. Safari and Firefox already implemented Intelligent Tracking Algorithms that can block trackers. That leads to the next point: digital advertising methods that rely on third-party cookies to target consumers might become ineffective or even stop working altogether. This change in how advertisers track users will hurt many publishers and ad networks that rely on these third-party companies to display ads and collect data from site visitors to understand their audience. In this blog post, I will explain what a third-party cookie is, why it matters, and how server-side tracking can help businesses transit to the world without third-party cookies.Sep 20, 2021
One of the ways to use server-side tracking is sending data directly from your server endpoint to the server GTM container. This guide will show how you can send requests to the GTM server container with webhooks and how to see and test webhook data in the server Google Tag Manager container. We’ll also go over some common scenarios where it makes sense technically and practically speaking.Sep 16, 2021
Find out how to use server-side tracking with Google Tag Manager and avoid being blocked by AdBlocker.