Webflow Analytics: Analyze vs GA4, Setup and Conversion Tracking

Webflow analytics comes in two forms: Webflow Analyze, a paid native add-on that tracks sessions, visitors, bounce rate, clicks and scroll depth with no script to install, and third-party tools such as Google Analytics 4, which you connect by pasting a measurement ID into Site settings. Analyze is the quickest way to see how pages perform while you edit them. GA4 is free and goes deeper on acquisition, funnels and ads, which is why many Webflow sites run both.

This guide covers what Analyze tracks and costs, how to connect GA4 step by step, how the two compare, and the parts most guides skip: tracking form submissions as real conversions, separating ChatGPT and Perplexity traffic, putting a dollar value on each landing page, and fixing numbers that do not match.

Your Webflow Analytics Options at a Glance

What Webflow Analyze Tracks

Analyze captures events automatically once you turn tracking on and publish. According to Webflow’s Intro to Analyze help article, it records:

• Click events on buttons, links and forms.
• Unique visitors. A person who comes back on another browser or device counts again.
• Sessions, which end after 30 minutes of inactivity.
• Bounce rate: the share of sessions where the visitor neither clicks anything nor opens another page. Scrolling and leaving still counts as a bounce.
• Time on site and time on page.
• Audience attributes such as traffic source, referrer, country, device and language.

The reports you get

• Site overview: traffic, bounce rate, average time on site, top referrer, top pages, top events, top audiences and the conversion rate of each goal.
• Page details: sessions, visitors, bounce rate, time on page, devices, top clicks, and the top 10 internal pages people viewed before and after the page.
• Analyze mode: an overlay in the Designer with clickmaps, scroll depth and the average page fold on the page you are editing. Webflow builds these maps from click and scroll events, not session recordings.
• Goals: code-free goals that count clicks on chosen buttons and links, such as “Request a demo.” You need Designer permissions or above to create them.

Limits worth knowing before you rely on it

• Data starts when you enable tracking. There is no backfill, and turning Analyze off removes access to the history.
• Results appear within about 30 minutes of publishing. The default view is the last 7 days, and you can view up to 90 days at once.
• The Pages list shows up to 150 top pages. For other pages, open the page in Webflow and use Analyze mode.
• Staging domains are excluded by default; you can choose to include them.
• On sites using Localize or Optimize, clicks are shown in aggregate across variations.

Webflow also sells an AI layer called AEO analytics: prompt insights (how often AI answers mention or cite your brand for prompts you track), LLM bot insights (which AI crawlers visit and what they read) and AI-referred visitor analytics. Prompt and bot insights are limited to Webflow’s Team and Enterprise tiers with the Analyze add-on, while the feature page says how AI-referred traffic converts is available on any Analyze plan.

Webflow Analyze Pricing and Plan Requirements

Analyze is an add-on to a paid Site plan (Basic, CMS, Business or Enterprise). As of October 2026, Webflow’s pricing page lists it from $9 per month, priced by the number of sessions per month, with tiers running from 2,000 to 500,000 sessions. Enterprise pricing is set with sales. Only Workspace admins can buy, upgrade, downgrade or cancel it.

GA4 itself is free, and Webflow’s help center notes that you do not need a paid plan to use the Google Analytics integration. Adding other scripts through custom code does need a paid Site or Workspace plan.

Privacy, Cookies and Consent

Analyze does not use cookies to recognize visitors. It runs in the browser using local storage and anonymous identifiers, collects no personally identifiable information, filters bots automatically and has no session replay. Your data stays inside Webflow rather than flowing to an ad platform.

That does not make it consent-free everywhere. Webflow’s help article says GDPR and CCPA compliance depends on the tracking default you pick (always on, opt-in or opt-out) and your consent setup. Opt-in and opt-out need a consent management platform; Webflow lists integrations with tools such as OneTrust, TrustArc, DataGrail and Finsweet’s consent components. Some comparison articles state that Analyze needs no banner in the EU. Webflow does not promise that, so make the call with your legal team.

GA4 sets cookies and sends data to Google, so in the EU, UK and a growing number of other regions it usually runs behind a consent banner. Every visitor who declines is missing from GA4, which is one reason GA4 often shows fewer visits than a cookieless tool. Our guide to cookieless conversion tracking explains what you can and cannot measure without cookies.

How to Connect Google Analytics 4 to Webflow

Webflow only accepts GA4 measurement IDs. The integration takes about as long as it takes to find your ID:

1. Create a GA4 property and web data stream. In Google Analytics, create a property, pick the Web platform and add a data stream for your domain.
2. Copy the measurement ID. It starts with G- (Webflow also accepts GT-, AW- and GTM- IDs). IDs are case sensitive.
3. Paste it into Webflow. Go to Site settings > Integrations > Google Analytics, paste the ID into the Measurement ID field and click Save changes.
4. Publish the site. Nothing is tracked until the tag is live.
5. Check the Realtime report. Open your live site in another tab and confirm your visit shows up in GA4 Realtime. Standard reports can take a day or so to fill in.
6. Turn on ecommerce tracking if you sell. With Webflow Ecommerce, the integration sends product view, add to cart and purchase events once ecommerce tracking is enabled.

Three details that save trouble later:

• Add GA4 in one place only. Use either the integration field or a Google tag in the head code, never both, or every pageview is counted twice.
• The integration routes through Google Tag Gateway. Webflow says this reduces losses to ad blockers, and the proxied traffic does not count toward your bandwidth.
• Search Console is separate. Webflow’s Google site tools app can connect Analytics, Tag Manager and Search Console and show common metrics in the Designer. Search Console is where you see the queries that bring organic visits.

Webflow Analyze vs Google Analytics 4

Choose Analyze when the people improving the site are the people who build it. Seeing that nobody scrolls past the second section, right on the canvas where you can fix it, is faster than any report. It also suits agencies that want to show clients simple results without training them on GA4.

Choose GA4 when you run paid campaigns, need funnels, want to segment audiences, or need to tie conversions to channels and campaigns. Its free price and links to Google Ads and Search Console are hard to match.

Run both when design and marketing need different answers. Decide upfront which tool owns which metric: for example, Analyze for page engagement and GA4 for channel and conversion reporting.

Other Analytics Tools That Work on Webflow

Any tool that installs with a script works on Webflow: paste its snippet into Site settings > Custom code (head code) and publish. Common choices in the Webflow community:

• Plausible and Fathom: lightweight, cookieless traffic dashboards on one screen. They stop at traffic and simple goals.
• Matomo: cloud or self-hosted when you must keep data on your own servers.
• Microsoft Clarity and Hotjar: recordings and heatmaps that show how people behave on a page. They do not replace an acquisition tool.
• PostHog and Amplitude: product analytics for funnels and retention, more useful for apps than marketing sites.

None of these answer the question a marketing site owner eventually asks: which pages and channels produce leads and sales, and what are they worth? The next sections cover that.

How to Track Webflow Form Submissions as Conversions

On most Webflow sites the form is the conversion: demo requests, quotes, contact forms, newsletter sign-ups. Webflow’s native forms submit in the background and swap the form for a success message on the same page, so no new page loads. That trips up tracking in three ways:

• Analyze goals count clicks, not submissions. A click on the submit button also fires when a required field is empty and the form is rejected. Treat a click goal as an upper bound.
• GA4’s automatic form events are not guaranteed. Enhanced measurement can send form_start and form_submit, but detection on background submissions is inconsistent. Test it before you trust it.
• There is no thank-you URL to count unless you create one.

Three ways to get a reliable count

1. Redirect to a thank-you page. In the form’s settings, set a redirect URL such as /thank-you-demo. In GA4, create an event from page_view where the page location contains that path, then mark it as a key event. Use one thank-you page per form so each conversion stays distinct, and keep the page out of your navigation and sitemap.
2. Fire an event when the success message appears. With Google Tag Manager, trigger on the visibility of Webflow’s success block and send a generate_lead event. This keeps visitors on the page and only counts accepted submissions.
3. Use a tool that captures form submits for you, then compare its count with the submissions in Webflow’s Forms tab for the same dates. The Forms tab is your ground truth.

Seeing ChatGPT and Other AI Assistant Traffic on a Webflow Site

Visitors who click a link in ChatGPT, Perplexity, Claude, Gemini or Copilot usually arrive with that assistant as the referrer. GA4 files them under Referral by default, mixed with every other site that links to you. Webflow’s AI-referred reports cover this inside Analyze; in GA4 you build it yourself with a custom channel group.

Google’s custom channel groups documentation walks through an “AI assistants” channel: add a channel with a source condition that matches a regex, then move it above Referral so it wins. Google’s sample regex opens with a very loose pattern (any source matching “.*ai”), which can sweep in unrelated sites. A tighter version that names the domains:

Two caveats. Custom channel groups apply to reports retroactively, so you can check history right away. And when an assistant sends no referrer, for example from some mobile apps, the visit lands in Direct and no rule can recover it. The full method, including how to tie these visits to conversions, is in our guide to AI conversion tracking.

From Sessions to Revenue: Value by Landing Page and Channel

Sessions tell you a page is visited. They do not tell you whether it pays for itself. To get there, give each conversion a value, then report value by landing page and channel. Here is an illustrative example for a B2B site on Webflow whose main conversion is a demo request.

The arithmetic: value is demo requests × $1,200 (30 × $1,200 = $36,000), and value per session is value ÷ sessions ($36,000 ÷ 1,200 = $30). The blog post brings the most traffic and the least value per visit. The AI assistant row is small but valuable per session; with only 6 conversions, watch it for a few months before moving budget. Neither Analyze’s traffic charts nor a sessions report would show any of this.

To build this yourself, work out a value per lead (our guide on how to calculate conversion value shows the method), send it as the value of your GA4 key event, and report by landing page and session channel. For Webflow Ecommerce, the purchase event already carries revenue. The wider process for organic search is in our SEO conversion tracking guide.

If you would rather not maintain tags and regexes, SEOConversion installs on Webflow with one script, captures form submits and high-intent clicks automatically, reads Webflow’s ecommerce dataLayer, and reports conversions and value from Google, Bing and AI assistants by landing page.

Why Webflow Analyze and GA4 Numbers Don’t Match

Webflow’s help center says discrepancies between tools are expected. That is true but not useful when a client asks which number is right. Work through these causes in order:

Which Webflow Analytics Setup to Choose

Whatever you pick, set it up before a redesign or launch. Analytics only counts from the day it is switched on, and a migration without a baseline leaves you guessing whether the new site performs better.

FAQ