Ever looked at a language report in Google Analytics and getting confused because of all the seemingly duplicate values? This post shows you how to rationalize everything – or try to anyway 🙂
Filtering language codes in Google AnalyticsNothing is more annoying than visiting a website and getting spammed by pop-ups, right? I’m pretty sure your users resent that too so if you’re a digital marketer, you are not always in control of how some partner tags get fired. What if you could set up engagement-based triggers to add another layer of control? What if you could control tags based on page count?
In today’s post we’ll be looking at how to set this up with Google Tag Manager by using a simple rule to store and increment the number of page views in a cookie. Then we’ll build a trigger that fires tags after a set number of pages have been viewed.
Ready? Let’s go 🙂
Creating page-count-based triggers in Google Tag ManagerSo your website is equipped with Google Tag Manager (good).
But your webmaster/IT contact is AWOL/bankrupt/defunct (bad).
On top of that, let’s assume that you’re trying to debug something complex such as an e-commerce transaction but you have no way to place test orders to perform basic debugging.
Long story short: debugging Google Tag Manager can prove tricky! But fear not, here is one reliable method you can use!
February 2019 EDIT: Google announced at Superweek Hungary the imminent release of tag templates, allowing for more tag flexibility!
If you use Google Tag Manager on a daily basis like I do (or hourly in my case), you probably love the fact that you can tie in tags for the entire Google ecosystem, especially now that Google released native support for YouTube tracking.
Google Tag Manager prepares support for other major tags
Here is a Google Universal Analytics Cheat Sheet to help you make sure you use the right parameters to track data on your websites and mobiles apps!
Working on Hub’Scan means I need to master every single aspect of Google Universal Analytics data collection. This means I get to maintain an accurate, updated list of parameters for the 500+ tags in the Hub’Scan library.
Don’t get me wrong, there are Google Universal Analytics cheat sheets out there but they are not complete and the official Google reference does not provide a list of all parameters.
Google Universal Analytics Cheat Sheet – Measurement Protocol Parameters
2020 October UPDATE: With the release of Google Analytics 4 (App+Web/Firebase), the old tracking code (analytics.js) is no longer supported, only GA4 and gtag.js are supported going forward.
2019 September UPDATE: In September of 2018, Apple rolled out its Intelligent Tracking Protection (ITP) 2.0 program. When ITP is activated, third-party cookies can only track a user’s activity across sites for 24 hours from the exact moment a user visits a website. After this 24-hour window, these third-party cookies are only able to “remember” a user’s login information. With ITP, all third-party cookies are gone after thirty days.[link]
Recommendation
Use Google Analytics tracking via GTM in order to avoid any code conflict and use a conversion linker
In August 2017, Google announced the Google Universal Analytics Global Site Tag.
The announcement triggered a few discussions on Twitter, with digital marketers and IT folks worldwide asking: “is it time to upgrade already?”
This post explains what is at stake with the Global Site Tag and why you should switch – or not.
Should you switch to Google Analytics’ Global Site Tag?You will be happy to learn that you can now embed DataStudio reports into your web pages.
If, like me, you are a Google Data Studio junkie/power user, you may have felt frustrated by the lack of report embedding and integration into websites such as intranets.
So you took a leap of faith and adapted your site to support the AMP (Accelerated Mobile Pages) format? This can be quite the constraint at first but it pays off in the longer term because it will make your content both more accessible on mobile devices and more visible in Google search results.
Having said that, there are other considerations besides making your content compliant with a streamlined mobile user experience. For instance, AMP does not support JavaScript by default. If your initial reaction was “Eeek, my tags won’t work!”, you were absolutely right. And yes, that includes Google Analytics and other tags.
In this post, I will cover how to setup Google Analytics tracking on AMP pages with Google Tag manager.
Tracking AMP pages with Google Analytics and Tag Manager
Every month, I get quite a few questions about the bounce rate, a metric that is supposed to provide insights into visitor engagement.
How much time did users really spend on a given page?
Did they find what they were looking for?
Why the heck do they leave my site right away instead of browsing more pages?
How can my bounce rate help me make sense of this?
Should I consider that a “bounce” occurs after 10, 15 or 30 seconds? This post is an attempt at demystifying a common metric that is still used and abused. I will cover how to define and calculate the bounce rate, how to analyze it and how to use it to improve your digital marketing campaigns.
So I recently got dragged into multiple discussions about Google Analytics referrer spam and ways to effectively block it so that report data is clean and that channel attribution makes sense. In this (long) post, I’d like to share a method I’ve put together to exclude Google Analytics referrer spam, which requires enlisting the help of Google Tag Manager. How can I handle Google Analytics referrer spam?
French