Yes, Webflow has analytics, but it does not replace Google Analytics 4 for most teams. Which one you use depends on what you need to measure, how much setup you are willing to do and how you handle cookie consent. Plenty of sites sensibly use both: a simple built-in view for everyday checks and GA4 for anything involving campaigns, conversions or attribution.
This guide explains what each option gives you, how they differ, how to connect GA4 to a Webflow site properly, how to track the actions that matter and the mistakes that corrupt the data. It is written for site owners and marketers rather than analysts, so each step comes with the reason behind it.
Does Webflow Have Analytics?
Webflow offers built-in analytics for traffic, plus an add-on product called Webflow Analyze for deeper insight. The basic dashboard covers the essentials most site owners want to see: visitors, page views, top pages and where traffic comes from. Which tiers are available to you depends on your plan, so check what your Webflow plan includes and what any add-on costs before relying on it, because plans and pricing change. I wrote about the add-on when it launched in Webflow Analyze: unveiling Webflow's latest data-driven feature.
Webflow Analytics vs Google Analytics 4
Where Webflow's built-in analytics works well
- Simple setup: it is already part of the platform, so there is no tag or code to add.
- Quick view of traffic: good for checking how pages perform without learning a new tool.
- Privacy: Webflow describes its analytics as cookieless, which can reduce the need for a consent banner. Confirm the current details and your legal obligations for the regions you serve.
Where GA4 is stronger
- Custom events and conversions: track button clicks, form submissions, scroll depth and anything else you define.
- Audiences and attribution: see how channels and campaigns contribute to results.
- Funnels and exploration: build reports that follow people through multiple steps.
- Integrations: connect with Google Ads, Search Console and BigQuery.
The trade-offs of GA4
- It has a steeper learning curve than a simple dashboard.
- It usually needs a cookie consent setup for visitors in regions that require it.
- Its numbers can differ from Webflow's because the two tools measure visits differently.
How GA4 Thinks About Data
If you used the older Universal Analytics, GA4 will feel unfamiliar, and understanding its model saves a lot of confusion. GA4 records events, not just page views. A page view is an event, a scroll is an event, a click on an outbound link is an event, and so is a form submission you define yourself. Some events are collected automatically, some are enhanced measurement options you can switch on, and the rest you create.
You then mark the events that matter to your business as key events (previously called conversions). Reports on acquisition, engagement and conversion all build on those. The practical consequence is that GA4 is only as useful as the events you set up. A fresh installation tells you how many people visited. It does not tell you how many people requested a demo until you track the demo request.
Which Should You Use?
- Use Webflow's analytics if you want a quick, low-maintenance view of traffic on a small site.
- Use GA4 if you run campaigns, need conversion tracking or want to connect analytics with advertising.
- Use both if you want a simple dashboard for everyday checks and GA4 for deeper reporting. Expect small differences in the numbers.
You may also come across privacy-focused alternatives such as Plausible or Fathom, and product analytics tools such as Mixpanel or PostHog. They are worth considering if consent banners are a problem or you need to analyse behaviour inside a product, but for most marketing sites the choice is between what Webflow offers and GA4.
How to Add Google Analytics 4 to Webflow
- Create a GA4 property in your Google Analytics account and choose Web as the platform.
- Create a data stream for your site and copy the Measurement ID, which looks like G-XXXXXXXXXX.
- Open your Webflow site settings and find the Google Analytics field under the apps and integrations area. Paste in the Measurement ID and save.
- Publish your site. Changes to site settings only go live after publishing.
- Check it works by opening GA4's Realtime report and visiting your site in another tab. You should see yourself as an active user.
For anything beyond basic page views, install GA4 through Google Tag Manager instead, so you can add and change events without editing the site each time. If you use Tag Manager, do not also paste the Measurement ID into the Webflow settings, or every visit will be counted twice. My guides to optimising your Webflow website with Google Analytics and measuring conversions in Webflow with GA4 go further.
Settings to Change Straight Away
A new GA4 property has some defaults that are worth changing in the first ten minutes:
- Data retention: the default retention for event-level data is short. Extend it to the longest option in the property's data settings so you can run explorations over longer periods.
- Internal traffic: define your office IP addresses as internal traffic and filter them out, so your own visits do not distort the data.
- Enhanced measurement: review which automatic events are on, such as scrolls, outbound clicks and file downloads, and switch off anything you do not need.
- Link Search Console: connecting it lets you see search queries and landing pages alongside behaviour.
- Link Google Ads: if you run ads, connect them so conversions can feed back.
Set Up Conversion Tracking
Page views tell you little on their own. Decide which actions matter, such as a contact form submission, a demo request or a download, and track those as key events in GA4.
Form submissions
Webflow forms do not reload the page on submit; they show a success message in place. That means a standard page-view trigger will not fire. There are two reliable approaches. The first is to redirect to a thank-you page after submission, then track visits to that page. This is the simplest and works well, but you should keep the thank-you page out of the sitemap and set it to noindex so it does not appear in search. The second is to use a Tag Manager trigger based on form submission or on the success state appearing, which keeps people on the page.
Button clicks and downloads
Use Tag Manager click triggers filtered by element classes or link URLs. A clear class naming system makes this far easier, which is another reason to follow Webflow naming conventions.
Test before you trust
Use GA4's DebugView or Tag Manager's preview mode to confirm each event fires once, with the right name, when you expect it. Then mark the event as a key event. For a deeper walkthrough, see setting up a Google Analytics goal for your Webflow website.
Cookie Consent and Privacy
GA4 uses cookies, so in regions with consent rules you need to ask before it runs, and you need to handle what happens when someone declines. Consent management tools integrate with Tag Manager and can pass consent signals to Google's tags. The details depend on where your visitors are and on your legal advice, so treat this section as a prompt to check rather than an answer. Also expect that some visitors will block analytics scripts or decline consent, which is one reason GA4 and Webflow's numbers differ.
Why the Numbers Never Match
Teams often panic when Webflow, GA4 and Search Console report different traffic. They are measuring different things in different ways:
- GA4 depends on consent and on scripts not being blocked, so it can undercount.
- A cookieless tool can count visits GA4 never sees.
- Bot filtering differs between tools.
- Search Console counts clicks from Google Search, not visits, and processes them differently.
- Sessions, users and visits are defined differently in each tool.
Pick one tool as the source of truth for each question, and compare trends within a tool rather than absolute numbers across tools.
Going Beyond Numbers
Analytics tells you what happened, not why. To understand why people leave a page or do not convert, pair it with qualitative tools. Heatmaps and user recordings show behaviour on the page, and A/B testing lets you check whether a change actually improves conversion. My roundup of 5 tools to collect data and optimise your Webflow website covers options.
Common Mistakes
- Installing GA4 twice, for example through site settings and a tag manager, which double-counts visits.
- Forgetting to publish after adding the Measurement ID.
- Not filtering your own traffic, so internal visits distort the data.
- Ignoring consent, which can break tracking or create compliance risk in some regions.
- Comparing the two tools' numbers directly without remembering that they count differently.
- Tracking nothing but page views, then wondering why the data cannot answer business questions.
Analytics When You Migrate a Site
If you are moving a site to Webflow, set up analytics before launch and keep the same GA4 property, so you can compare before and after. Check that tracking fires on the new site on launch day and that your key events still work, because a rebuilt form or button often loses the class or trigger the old tag relied on. See my website migration checklist and the Webflow SEO checklist for the full list of launch checks.
Frequently Asked Questions
Does Webflow have built-in analytics?
Yes. Webflow includes basic traffic analytics and offers Webflow Analyze as a more detailed option. What you can access depends on your plan and any add-ons.
Should I use Webflow analytics or Google Analytics?
Use Webflow's for a simple view of traffic. Use GA4 when you need conversion tracking, attribution or advertising integrations. Many sites use both.
How do I add Google Analytics to Webflow?
Create a GA4 property and data stream, copy the Measurement ID, paste it into the Google Analytics field in your Webflow site settings, then publish.
Why are my Webflow and Google Analytics numbers different?
The tools measure visits differently, treat bots and blocked scripts differently, and Google Analytics depends on cookie consent. Small differences are normal.
Do I need a cookie banner for Webflow analytics?
It depends on the tool and where your visitors are. GA4 generally needs consent handling in regions that require it. Check your obligations or ask a legal adviser.
How do I track form submissions in Webflow with GA4?
Either redirect to a thank-you page and track that page, or use a Google Tag Manager trigger for form submissions. Then mark the event as a key event in GA4.
Should I use Google Tag Manager with Webflow?
If you need more than page views, yes. It lets you add and change tracking without editing the site. Just make sure GA4 is installed in one place only.
