How to Set Up Google Tag Manager on a Webflow Nonprofit Website
Google Tag Manager Setup for Webflow Nonprofits: A Practical Guide
What Google Tag Manager Is and Why It Matters
Every tracking tool added to your website — Google Analytics, Meta Pixel, LinkedIn Insight Tag — requires a JavaScript snippet on the site. Without a tag manager, each script is added directly to the site's code. Google Tag Manager (GTM) acts as a container: a single script added to your site once, through which all other tracking tags are deployed and managed.
For nonprofits, this matters for two reasons. First, it separates marketing and analytics configuration from website development — your Communications team can manage tracking without developer access. Second, it's the correct architecture for GDPR-compliant consent management, covered in detail in How to Set Up CookieYes and Google Consent Mode V2 on a Webflow Nonprofit Website.
Before You Start
What you need: a Google account with access to create a GTM container, a Webflow site on a paid hosting plan, admin access to the Webflow site, and a GA4 property already created in Google Analytics.
If you're also setting up CookieYes and Google Consent Mode V2 — which you should be if your site collects any personal data — read this guide first, then follow the CookieYes guide for the full consent configuration.
Step 1: Create a GTM Account and Container
Go to tagmanager.google.com and sign in. Create a new container, enter the container name (use the site's domain), set the target platform to Web, and click Create. GTM will display two JavaScript snippets: one for the <head> and one immediately after the opening <body> tag.
Step 2: Install GTM on the Webflow Site
In Webflow, navigate to Site Settings → Custom Code. Add the two GTM snippets:
- Head Code field — paste the GTM
<head>snippet - Footer Code field — paste the GTM
<body>snippet (fallback for browsers with JavaScript disabled)
Save and publish the Webflow site. GTM will not be active on the live site until the site is published.
To verify: in GTM, use the Preview button to open Tag Assistant. Enter your site's URL and connect. If Tag Assistant connects successfully, GTM is installed correctly.
Step 3: Publish the GTM Container
GTM has its own publishing step separate from Webflow. After any change in GTM, click Submit, add a version name and description, and click Publish. GTM maintains a full history of published versions, so any change can be rolled back. Write descriptive version names — they make debugging much easier later.
Step 4: Install GA4 via GTM
In GTM, go to Tags → New and select Google Analytics: GA4 Configuration. Enter your Measurement ID (format: G-XXXXXXXXXX, found in GA4 property settings under Data Streams). Set the trigger to All Pages. In Advanced Settings → Consent Settings, enable the consent check for analytics_storage so the tag respects the consent defaults. Save and publish.
Verify: open GTM Preview Mode, browse the site, then check your GA4 Realtime report. You should see active users appearing within a minute or two.
Step 5: Add Meta Pixel and LinkedIn Insight Tag (If Applicable)
Only relevant if your organisation runs paid advertising. If not, skip this step and add these tags later when needed.
Meta Pixel: In GTM, search the Community Template Gallery for Meta Pixel or add a Custom HTML tag with the Pixel base code. Set the trigger to All Pages and require ad_storage and ad_user_data consent before firing.
LinkedIn Insight Tag: Search the Gallery for the LinkedIn Insight Tag template. Enter your Partner ID from LinkedIn Campaign Manager. Set trigger to All Pages and require ad_storage consent.
Both tags should only fire after a user has accepted advertising cookies.
What GTM Is Not the Right Tool For
GTM is excellent for deploying third-party tags. Advanced event tracking — scroll depth events, form submission tracking, button click events, conversion tracking — requires someone with GTM and analytics experience to configure. I install GTM and configure GA4 and consent tags, but I'm explicit with clients that advanced event tracking is a separate engagement handled by a digital marketer or analytics specialist.
When Webflow Analyse Is Enough
For organisations that don't run paid advertising and primarily want to understand traffic patterns and content performance, Webflow Analyse may be sufficient. It provides page views, traffic sources, top pages, scroll depth, and heatmaps built in — without additional tools like Hotjar. For most of my clients who aren't running paid campaigns, I recommend starting with Webflow Analyse. It's one less system to manage and the data is sufficient for quarterly content reviews.
The limitation is that Webflow Analyse doesn't integrate with Google's advertising ecosystem. If you run paid campaigns and need to measure their effectiveness, GA4 via GTM remains necessary.
Further Reading
Eric Phung has 7 years of Webflow development experience, having built 100+ websites across industries including SaaS, e-commerce, professional services, and nonprofits. He specialises in nonprofit website migrations using the Lumos accessibility framework (v2.2.0+) with a focus on editorial independence and WCAG AA compliance. Current clients include WHO Foundation, Do Good Daniels Family Foundation, and Territorio de Zaguates. Based in Manchester, UK, Eric focuses exclusively on helping established nonprofits migrate from WordPress and Wix to maintainable Webflow infrastructure.
Not sure where your site currently stands?
A Blueprint Audit tells you exactly what needs to change — and why.
Before implementing anything new, it's worth knowing what your current site is and isn't doing for your stakeholders. The Blueprint Audit gives you that clarity in two to three weeks.
Related Resources
Google Tag Manager Setup for Webflow Nonprofits: A Practical Guide
How to install and configure Google Tag Manager on a Webflow nonprofit website — covering container setup, GA4, consent integration, and when GTM is more than you need.
Join our newsletter
Subscribe to my newsletter to receive latest news & updates
