Nothing 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 🙂

So 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!