If you've opened the browser console in Google Chrome (since Chrome 76), you might have seen a bunch of warnings in a yellow background related to something called a SameSite cookie attribute that is either missing or incompletely set for cookies set on external domains. If you use Google Tag Manager, especially in Preview mode, you might have seen a warning about the http(s)://www.googletagmanager.com domain. Even though the warning is very prominent, hogging up some prime real estate in the browser console warning, it is, for now, just a warning.
Google Tag Manager now lets you add unit tests directly to your custom templates. This is useful, since it allows you to control the code stability of your templates, especially if you've decided to share those templates with the public. I recently shared a general guide for how template tests work, but I wanted to expand the topic a little, and share with you two walkthroughs of custom template tests: one for a variable template and one for a tag template.
I've written about outbound link click tracking before. It's a very solid way to track interactions on the site, as clicking a link that leads away from a site is a signal of … well, something. In Google Tag Manager it's now extremely easy and efficient to track outbound link clicks, thanks to the introduction of a new configuration in the Auto-Event variable. This article will introduce the new method and show you how you can quickly set it up!
A surprisingly common question in forums and communities seems to be why the built-in Click variables show up as undefined in Google Tag Manager's Preview mode, even if you click around the site. In this article, I'll walk you through some of the reasons why this might happen. Tip 104: What to do when Click variables are undefined Here's the situation: you want to create a Click trigger for your tags, but in order to do so, you'd need to see what values the built-in Click variables (e.
With Intelligent Tracking Prevention, the Safari browser is on a crusade against cross-site tracking. One of the most obvious and long-standing ways to battle cross-site tracking has been to block third-party cookies in the web browser, and this is exactly what Safari does by default. However, Google Tag Manager's Preview mode relies on a third-party cookies, so that it can serve you the draft version of the container while serving the regular, live container to your site visitors.
- OLDER POSTS
- page 1 of 16