![]() ![]() Set these to the endpoints configured in the Client template I’m using a custom Client template in the Server container to pick up requests for the ad blocker bait file as well as for the pixel that is used to generate an event data object. If you haven’t set it up yet, I recommend you take a look at my article on the topic. ![]() Note that to understand everything that’s happening here, you need a fairly good grasp of server-side tagging. ![]() There are additional caveats related to each of these measurements, but I’ll tackle those when they come up. The ratio of homepage views where Google Tag Manager was blocked.The ratio of homepage views where Google Analytics was blocked.The ratio of homepage views where ads were blocked.In this article, I’ll show you how I’m measuring three different things: What I’m showing you here are some of the components you need to create the detection system, but most of the work needs to be done client-side (where the detection happens), so you need to adjust these ideas to make sense for what your site runs on. Let’s start with a major caveat (first of many): Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava into your email inbox! You can even use the detection technology to conditionally block your server-side tags! That way you can truly act according to the user’s wishes and keep those data streams between the browser and the server container alive.īy the way, if you’re interested in knowing more about ad and content blockers in general, I recommend you listen to this Technical Marketing Handbook podcast episode, where I interviewed Pete Snyder of Brave about this very topic. That way you can calculate just how many of your analytics and ad requests are blocked due to these tools. While ad and content blockers should be allowed to run their course, I do think it’s absolutely vital that their impact be measured. Instead, I want to take the technology that allows you to circumvent and instead use it to detect. However, this is not another article lamenting this disconnect between data-hungry analysts and their unsuspecting site visitors. By circumventing the user’s wish to block scripts, you are disrespecting them and forcing their browser to download scripts that they wanted to avoid downloading in the first place. Well, I’ve gone on record over and over again to say how this is poor justification for using server-side GTM. After all, by virtue of serving the container JavaScript from your own domain, you escape many of the heuristic devices today’s blocker technologies employ. For many, it seems, one of the most important justifications for server-side Google Tag Manager is its resilience to ad and content blockers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |