Use a naming scheme and folders.

[kexej28769@nongnue]

Also use a naming scheme and folders, because you're not going to be working there forever, and someone in the future is going to want to look at this and think, "Why did they set it up like that? What does that word mean? Why is that variable called foo?" You know, things that have annoyed me about developers for years and years, developers I love you, but please stop naming things. It doesn't mean anything to anyone but you. So our naming scheme, and you can totally steal it if you want, is we have product, result, and then what.

So, for example, we'll have our tag for Google Analytics benin number data download. So it'll say Google Analytics. That's the product that's being discussed. The event is what's the result of that existing thing. Then what's the PDF download. Then it's really clear, okay, I need to fix this thing with the PDF download. Something's wrong.

It's kind of weird. Now I know exactly where to go. Again, with folders too, so let's say you implemented something like content consumption, which is a Google Tag Manager trick that you can get on our website Kickpoint.ca, and I'll make sure to link to it in the transcript. Let's say you grab that. Then you'll want to take all the different tags and triggers that come with content consumption and toss it into its own folder and then separate it from all your core stuff.