Installing Google Tag Manager Manually, One Page at a Time
After what went wrong with my first Tag Manager container, I wanted to do this install properly, on this site, with the whole thing recorded instead of just written up afterward from memory.
I’d learned GA4 through a digital job training program this time, not just by poking around on my own like the first attempt. Even with that behind me, I’ve been going through this site’s setup step by step rather than in one sitting, and the first time I actually went to paste the code in, my hands were a bit tense. Nothing dramatic. Just that low-grade worry that I’d get the placement wrong, or that everything would look fine while quietly doing nothing underneath, the way it had before.
I did the manual version first, on purpose, pasting the code directly into a single post. Not because I’d recommend it for a real site. Because it’s the version that shows every awkward decision a beginner has to make along the way.
Copying and Pasting the Snippet
Tag Manager hands you two code blocks with two separate instructions, one for the head of the page, one for right after the opening body tag. Fine, in theory. But on a WordPress site you’re not staring at raw HTML the way those instructions assume, you’re staring at a block editor. So the first real question becomes: where does any of this even go?
Copying the noscript snippet from Tag Manager and pasting it into a single post.
I landed on pasting the noscript snippet right at the very top of the block, ahead of the meta tags and styling already sitting there. That was the moment my stomach actually dropped, hovering over the save button, half expecting to have broken the page for the next person who visited. It isn’t the same, technically, as placing code right after a real <body> tag inside the site’s actual structure. It’s about as close as a normal content editor lets you get. And it works.
Works and correct aren’t the same thing though. That gap between them is exactly what let the tracking on my old site die quietly without me noticing, the same pattern showing up again in a smaller, less damaging way.
Confirming It Fired
Pasting code in isn’t the finish line, even if it feels like it in the moment. Tag Manager has its own way of checking whether a page is sending anything back, and I wanted to use that properly instead of assuming the paste had worked just because nothing looked visibly wrong.
Testing the exact page URL through Tag Manager’s own test tool.
I grabbed the live URL of the post I’d just edited and dropped it into Tag Manager’s test field. Confirmed. Container detected, snippet live, on that one page.
On that one page is the catch. That test tells me nothing about every other page and post sitting on this site. Each of those would need the same process, by hand, with the same odds of getting the placement slightly wrong somewhere along the way.
Why I Bothered With the Hard Way
I could have skipped straight to the plugin and called it a tutorial. I don’t think that version teaches anyone much of anything.
Doing it manually first, on camera, meant sitting inside that exact moment of not knowing: a block editor instead of raw HTML, and no clean answer for where “as high in the head as possible” is supposed to land inside WordPress. That’s a real kind of uncertainty, and it’s more or less what left a half-finished, silently dying tracking setup on my old site for years without me noticing.
Watching the test come back confirmed still felt like something, small as it was. Proof that code placed by feel, not certainty, had done the job anyway.
For the full story of why I was being this careful in the first place, here’s the original container I broke without realising it, zero tags, zero variables, and a warning I didn’t understand at the time.