“Corrected Transcript:
Okay, so here we are back in Google Tag Manager. This is part three, right? We started out in part one, where we connected and created a container in Google Tag Manager. In part two, we went out to Facebook, and we created the pixel over there in the Facebook Events Manager. Now, we’re back in Google Tag Manager. Remember, the last thing we did in part two was we copied that pixel code, right? That JavaScript code. So now here we are, and you go to yours, not mine, and we’re in tags, and it says there’s nothing. Click the new button, okay? Choose a tag type. All right? And so let’s do that, and we’re going to use custom HTML. Now it’s not actually HTML, it’s JavaScript, but it means the same thing. You see those little brackets; that just means anything that appears on a webpage, okay? So custom HTML, and it’s going to fill this in. Okay, paste your code here, right? And by the way, yes, you could write your own tags if you want to learn how to do that. It’s not that difficult. In fact, several AIs can help you do that, but we’re not going to do that. We’re going to get rid of that boilerplate. Remember, it’s on my clipboard, right? Haven’t disturbed that. Oh, for goodness’ sake. Yes, I did. One second. Here we go. That was a recording I just did. And so I’m going to go back, and I’m going to copy the code. That was probably a better way to establish continuity. Anyway, wasn’t it? There we go. There it is. The Facebook pixel code, Meta, AKA Facebook. Okay, so now what do we do? Are we done? Not quite. That’s the tag configuration. Great. Let’s look at the settings. Enable only fire this once per event. Yes, that’s true. Consent settings. Don’t need to worry about that. Additional tag metadata. I mean, that can be useful, but we don’t need that. Tag sequencing. We don’t need to do that either, although there are cases where you might want to. And so yeah, we’re good here. Okay, now triggering. So when does Google Tag Manager actually fire? And so, hang on, let me go back. So this is not actually on your website. You notice that we didn’t actually modify your website. You did not go into WordPress and change the header scripts or whatever. Didn’t do that. So how does your website actually trigger it? Well, that’s from the Google Tag Manager code that’s on your website. So on your website, there’s a little piece of code that goes to Google Tag Manager, and Google Tag Manager decides what other code to run. I know it’s pretty wild, right? And it’s faster than you might think by that description. So, but triggering, we do need to do this. We’re going to say trigger on all pages is what we want. Now, yes, it could be consent initialization. There could be some other reasons to do those. Not important. You will know if you need to do that. Seriously. Somebody legal will tell you, I don’t know, whatever. So add, all right, so now we have the custom HTML and we have the triggering. Oh, let’s name this. Why do you think, oh, how about FB Pixel? Where have you seen that before? Alright, so hit save. Woo-hoo. Are we done? Not quite, not quite. So, you’ll notice there’s this blue button right up here that says Submit. Let’s do that. Because what happens right now is this is kind of like sandboxed, it’s not live on your website. Everything that’s done with Google Tag Manager is versioned so that you can fall back if you screw something up. Trust me, that does happen. So I’m going to do submit, publish a new version, version name, and it doesn’t matter. I’ll just say one. I mean, it’s up to you what you want to do there. It’s going to show you the entire list. In fact, I’ll go back and show you one of mine. And there we are. And so the version, there’s one tag, and it’s five variables, blah, blah, blah. Ignore that; it doesn’t matter. Well, I mean it does, but not at the level we’re talking about. Okay? Alright, good. And you can see it’s the event and the hostname and the path and URL, all that’s what you would expect of analytics type stuff, right? Okay, so now version two is live. That’s interesting. Version one. Oh, what happened to version one? Version one was empty. And so when you create a Google Tag Manager for the first time, it’s empty. That’s version one. So this is literally version two, which I named one. Okay? Fair enough. Alright, let’s go back and look at the setup. I should actually have two versions of that, maybe. No, I don’t. I just have the one version. Alright, so here we are. Is it working well? How do you find out? Fortunately, there’s an app for that. So let’s go out to our browser. I figure out where my browser is, and we’re going to go to a plugin in Chrome. It’s available in others as well. Where is it? Where’s the Pixel? Why isn’t it in Chrome? I have lots of these. Email tracker. Evernote, what? Okay, help me out here. I’m looking for the Facebook Pixel Helper. I click that, and it’s going to show me. Uh oh, no Pixel found. Oh, I’m not on my website. Good grief. Okay, the owner’s job, sorry, that’s kind of a messy take, but, so now I’m going to use as soon as everything loads, you know, dragged down by video recording on my desktop. Here we go. And so the Facebook Pixel Helper, come on, scroll into view. Hmm, I thought I clicked it. Come on. There we are. And it says one pixel found on fionasdrive.com, and it shows us the ID. Now we don’t need to go check that, but I mean, if you want to feel free, right? You can go back into Facebook, and you’ll find that that Pixel ID is, in fact, the one that we just installed. Okay, that’s it. What did we do? Alright, so first, in Google Tag Manager, we connected to Google Tag Manager and created a new container for our brand new website. That’s part one. Part two, we went into an ad account we had already set up in Facebook. Now that’s the important point here, okay? You have to set up an ad account in Facebook first so that there is an actual pixel for your website. We then went and found that pixel code, which is a little chunk of JavaScript that you’re going to install manually. Pretty easy. Copy paste. We copied that code, we went back into Google Tag Manager, and we pasted that code as a new tag. Bam. Hit save, publish. And then we can verify in the Chrome browser or in other browsers as well that yes, that pixel is installed. That’s it. We have now connected tracking between our website and Facebook. Easy as pie.”
