Wire up your tracking layer. One container, GA4 and Meta together.

• A GA4 property with a Measurement ID (G-XXXXXXX) in hand
• A GTM container with a Container ID (GTM-XXXXXXX) in hand
• One container firing four tags: GA4 page views, GA4 sign-up conversions, Meta page views, Meta subscribe conversions
• The container wired into your website through a single field
• Proof it works: a real test conversion showing up in both Google and Meta

• Your Meta Dataset / Pixel ID from Module 1 (the 15–16 digit number), pasted somewhere handy
• Your website's public URL
• A Google account you're logged into (which one matters, see Step 0)
• Access to your site's settings where you can paste a tracking ID (newsletter aside: Beehiiv → Website → Settings → Pixels)
• 45 uninterrupted minutes

GTM is a switchboard. You install it once.

Most people bolt tracking on the messy way: a Google snippet here, a Meta pixel there, a TikTok tag over there, each pasted into the site's code separately. Six months later nobody knows what's installed, half of it's broken, and adding a tool means editing code again.

Google Tag Manager fixes this. Picture a switchboard:

Your website  ──fires events──►  dataLayer  (a belt of "things that happened")
                                     │
                                     ▼
                          Google Tag Manager   ← ONE snippet on your site
                          the switchboard that listens
                                     │
                 ┌───────────────────┼───────────────────┐
                 ▼                   ▼                   ▼
            GA4 tags           Meta pixel tags      (future: TikTok,
        (Google Analytics)   (Facebook / Instagram)  Google Ads…)

You install one thing on your site: the GTM container. From then on, every tracking tool you'll ever want lives inside GTM, turned on with clicks instead of code. Your site pushes "events" onto a dataLayer (a conveyor belt announcing "someone loaded a page," "someone subscribed"). GTM listens and fires the right tags to the right platforms.

Three words and you'll follow everything:

• GA4, Google Analytics 4. Google's free analytics. Its address is a Measurement ID, G-XXXXXXX.
• GTM, Google Tag Manager. The switchboard. Its address is a Container ID, GTM-XXXXXXX.
• The Meta pixel/dataset, the thing you made in Module 1. It rides inside GTM.

Order of build: GA4 first (get its ID), then GTM (the container that holds everything), then wire GTM into your site, then verify. Let's go.

1. Decide: a dedicated brand Google account (recommended) or your personal one.
2. Make sure you're logged into that account before you start. Juggling several Google logins? Google adds ?authuser=N to the URL, confirm by clicking your avatar (top-right) and reading the email.

1. Go to analytics.google.com. New to it on this account? You'll get a "Start measuring" welcome, click it.
2. Account setup: name the account (your brand), leave data-sharing at defaults. Next.
3. Property setup: name it ("[Your Brand] Website"), set time zone and currency to your local ones. Next.
4. Business details: pick an industry and size. (For a newsletter I use "News" and the smallest size.) Next.
5. Business objectives: "Generate leads" and "Understand web traffic" are the right two for a newsletter. Create.
6. Accept the Terms of Service, a real legal agreement for your business. I also tick the GDPR Data Processing Terms box (more privacy-protective even if you're US-only). I Accept.
7. Set up a data stream: choose Web, enter your URL and a stream name, leave Enhanced Measurement ON. Create stream.

Grab the Measurement ID. After the stream is created, GA4 shows a "Google tag" install panel. Inside it your ID appears in a line like:

gtag('config', 'G-XXXXXXX');

That G-XXXXXXX is your Measurement ID. Copy it next to your Meta dataset ID. Do NOT install the snippet it's showing you, GTM fires GA4 for us. Close the panel.

1. Go to tagmanager.google.com (confirm you're still in the right Google account).
2. Click Create Account.
3. Account name: your brand. Country: yours. Leave "share data anonymously" unchecked.
4. Container name: your domain. Target platform: Web.
5. Create, then accept the GTM Terms of Service (a separate agreement from GA4's, I tick the GDPR box and click Yes).
6. An "Install Google Tag Manager" box appears with two snippets. You don't need to copy these, your platform has a dedicated field for the ID (Step 5). Just note the Container ID at the top, GTM-XXXXXXX. Close the box.

You now have both IDs: your GA4 G-XXXXXXX and your GTM GTM-XXXXXXX, plus your Meta dataset ID from Module 1. Everything else happens inside this container.

We build, in order: 3 variables (reusable values), 2 triggers (the "when should a tag fire?" rules), 1 template (the official Meta building block), 4 tags (the things that actually fire).

Left nav → Variables → New (under "User-Defined Variables"). Create three:

1. ID-GA4, type Constant. Value: your G-XXXXXXX. Save.
2. ID-META, type Constant. Value: your Meta dataset ID from Module 1. Save.
3. DLV-EMAIL, type Data Layer Variable. Name: eventProps.email (version 2). Save.

Open Triggers → New. Create two:

1. Subscriber Sign-Up, type Custom Event. Event name: signedUp. Save.
2. Page View (History Change), type History Change. Save.

GTM has a gallery of pre-built, vetted tag templates. Meta's official one is the safe way to fire the pixel, you never want to hand-write pixel code.

1. Left nav → Templates → Search Gallery (under "Tag Templates").
2. Search Meta Pixel and pick the one by facebook (verified checkmark).
3. Add to workspace, then accept its permissions (it needs to inject the Meta script and read the dataLayer, expected for any pixel).

Open Tags → New for each. Tip: to reference a variable in any field, type {{ and pick it.

Top-right, click Submit → Publish. Name the version ("Initial tracking setup") and publish.

1. Go to your site's tracking settings. (newsletter aside: Beehiiv → Website → Settings → Pixels.)
2. Find the Google Tag Manager field. Paste your GTM-XXXXXXX.
3. Leave the standalone Google Analytics and Meta Pixel fields BLANK.
4. Save (and republish the site if your platform asks).

Two checks: page views, then a conversion. Open your browser's developer tools → Network tab for both.

Check A, page views are firing

1. Open your live site in a normal tab. In the Network tab, filter for collect (GA4) and facebook.com/tr (Meta).
2. Reload. You should see a GA4 collect request carrying your G-XXXXXXX, and a facebook.com/tr request carrying your dataset ID with ev=PageView.

Check B, a real conversion fires

1. Do a real test subscribe on your site (an email you control).
2. Watch for a GA4 collect with en=sign_up, and a facebook.com/tr with ev=Subscribe and a hashed email attached.
3. Cross-confirm: GA4 → Reports → Realtime shows a sign_up; Meta Events Manager shows a Subscribe within minutes to a few hours.

Both checks pass? Your tracking layer is live and verified. You can now see every subscriber a campaign produces, which means you can finally spend on ads like an adult.

Verification checklist.

• GA4 property created; Measurement ID G-XXXXXXX copied down
• GTM container created; Container ID GTM-XXXXXXX copied down
• Container has 3 variables, 2 triggers, the Meta Pixel template, 4 tags, and is Published
• Conversions API opt-in is unchecked on both Meta tags
• GTM field on your site is filled; standalone GA4 and Meta fields are BLANK
• On a page load: GA4 collect and Meta PageView both fire
• On a test subscribe: GA4 sign_up and Meta Subscribe (hashed email) both fire
• The sign_up shows in GA4 Realtime and the Subscribe in Meta Events Manager (within 24h)

Ad campaigns, where the tracking pays for itself.

You now have a foundation that sees. Because every subscribe fires a clean, attributed conversion to Meta, you can run a cold campaign optimized directly toward subscribers, not clicks, not "reach," actual people joining your list, watch your true cost-per-subscriber in real time, and scale what works. Tracking first, then spend. That's the whole reason we did this before touching a campaign.

Every landmine, one place.