Conversion tracking for Webflow, done right

Webflow is brilliant for marketing sites, startups and lead-gen, which is exactly why its tracking breaks in ways a normal CMS never does. You have custom code pasted into a handful of different boxes, native forms that look like they convert but say nothing to your tags, and slick page transitions that quietly move the goalposts. Here is what actually goes wrong on Webflow, and what a clean setup looks like.

Why Webflow is its own special case

Webflow gives you a designer's canvas and a single field for custom code, and that is the whole problem. Your GTM container and pixels get pasted by hand, often more than once, your forms never announce a success to anyone, and the animations and page transitions that make the site feel good also mean the page rarely loads the way a tag expects. Most Webflow tracking issues are not a broken tag, they are the platform behaving differently from the ordinary page load your tags were written for.

The five things we see break on Webflow

1. Custom code is easy to add and easy to get wrong

GTM and pixels get pasted into the site-wide custom code, then again into a page's custom code, then sometimes into an embed for good measure. Duplicated snippets double-fire your tags, and a container dropped in the head when it belongs in the body, or the other way round, can mean a tag that never loads at all.

2. Native form submissions never fire a lead event

Webflow's built-in forms are lovely to build and useless to track. When one succeeds it simply swaps in a thank-you message, and no generate_lead or conversion event is pushed to your data layer. So your demo requests and contact forms, the actual point of the site, go completely untracked until custom code is added to catch the submit.

3. Interactions and single-page behaviour hide your events

Webflow's animations, tabs and page transitions mean content appears and changes without a normal page load. If your tags assume a fresh load every time, clicks and views on tabbed sections, sliders and transitioned pages are simply missed, and you never see them go.

4. Webflow Ecommerce checkout is hosted and limited

If you sell through Webflow Ecommerce, the order-confirmation step is hosted and restricted, so there is little room to add proper tracking. The purchase event is often missing entirely, or it arrives without a value or a unique transaction ID, which quietly breaks your revenue reporting and deduplication.

5. There is no native consent, so a bolted-on banner leaks

Webflow has no consent management of its own, so teams add a third-party banner. It is usually not wired to Google Consent Mode, so your tags either fire before the visitor has agreed or are blocked outright. For UK and EU visitors that is both a compliance risk and a chunk of measurable data thrown away.

What a clean Webflow setup looks like

Done properly, one GTM container owns tracking and lives in exactly one place, so nothing double-fires and nothing sits loading in the wrong slot. Custom code listens for every native form submit and pushes a proper generate_lead event with the form name, so demo requests and contact forms are counted the moment they land. Interactions, tabs and transitions get their own events rather than relying on a page load that never comes. If you run Webflow Ecommerce, the purchase is captured with real value and a transaction ID wherever the hosted checkout allows. And your consent banner is wired to Consent Mode, so you stay compliant without binning measurable data. When that is in place, GA4, Google Ads and Meta all agree on how many leads you actually got.

Common Webflow tracking questions

Why aren't my Webflow form submissions showing up as conversions?

Because a native Webflow form does not fire an event when it succeeds, it just shows a thank-you message. You need custom code to catch the submit and push a generate_lead event, and then your leads start appearing in GA4, Google Ads and Meta.

Why are my tags firing twice?

Almost always because the same snippet is pasted in more than one custom code box, site-wide and on the page, or in an embed as well. Keep the container in one place and the double count disappears.

Does Webflow have built-in cookie consent?

No, there is nothing native, so you add a third-party banner. The trick is wiring it to Google Consent Mode so tags wait for consent rather than being blocked outright, which keeps you compliant without losing all your data.

Datahound are analytics and ad-tracking specialists. We fix broken GA4, Meta CAPI and server-side tracking for Webflow and other platforms. See pricing · Back to datahound.agency