Install Google Tag Manager and Google Analytics 4 correctly. Get the right foundations in place before tracking any events or conversions.
Every optimisation you run and every decision you defend will lean on the data you set up here. A clean Google Tag Manager (GTM) + Google Analytics 4 (GA4) installation means you can add events, switch consent modes, or debug campaigns without begging developers for deploy time. Follow the steps below exactly; I’ll note where to drop your screenshots so the rest of the team can replicate your work later.
4. Accept the terms; Google shows two code snippets.
5. Copy both the snippets
.png)
Follow the two–snippet rule: the head script lives once in global Site Settings; the body noscript lives on every page via a reusable Component.
![[PRINT SCREEN: Webflow › Site Settings › Custom Code panel showing <script> pasted in Head]](https://cdn.prod.website-files.com/65dcbaba5bc2ba10de80f3c9/681c9799d8a91fe3a79e5142_6814c760b92e2cf17692b1f5_SolidGrowth-com-Custom-code-Webflow-05-02-2025_03_23_PM.png)
Paste this component on every page!
[PRINT SCREEN: Browser View-Source showing both snippets in their correct locations]
By splitting the two snippets this way and turning the body code into a Component you guarantee the noscript loads everywhere and future edits take seconds, not hours.
.png)
[PRINT SCREEN: GA4 DebugView timeline highlighting page_view]
If the event appears, both snippets and the configuration tag are working. If not, check ad-blockers, script blockers, or copy/paste errors.
[PRINT SCREEN: GA4 Realtime report showing 1 active user from your location]
Allow up to 24 hours for standard reports (Engagement, Acquisition) to populate.
Allow up to 24 hours for standard reports (Engagement, Acquisition) to populate.
A clean install of Tag Manager and GA4 follows four steps: add the GTM snippets, create the GA4 property, test every page in preview mode and publish only after verification. Completing those steps today gives you a single source of truth and ends guess-work about site traffic.
I run the same process for every new project because it prevents tedious repairs later. Your analytics now show live page views; the next task is to decide which actions demos, trials, deals belong alongside them. That decision turns raw hits into growth insight and will be the focus of the following chapter.
Tag management that lets you add and control scripts, events and pixels with versioning and consent rules.
Web analytics that tracks user behaviour and conversions, essential for understanding traffic and lead sources when configured well.
Free dashboard tool that pulls data from many sources, great for quick reports and shareable views.
Product analytics for events, funnels and cohorts, useful when you need to see how users move and where they drop in product journeys.
Track what matters for growth decisions. Map key conversions, name events with clear conventions, and document tracking specifications.
Broken tracking means flying blind. Proper implementation shows exactly which traffic converts, which campaigns deliver ROI, and where to double down. Measurement makes optimisation possible.
See playbookCapture specific user actions in your product or website to understand behaviour patterns and measure whether changes improve outcomes or create friction.
Measure which marketing activities drive desired outcomes to allocate budget toward channels that actually generate revenue instead of vanity metrics.
Store information in browsers to track user behaviour across visits and enable personalised experiences without requiring login for every interaction.
Track campaign performance precisely by appending parameters to URLs that identify traffic sources, mediums, and campaigns in your analytics.
