Webflow sites
The form says thank you. Google Ads never hears it.
Webflow sites look clean, but tracking on them often isn't. Native forms show a success message instead of a thank-you page, code ends up in the wrong place, and booking tools on other domains lose the click. We track every form once, place the code properly and keep the source on every lead.
WHO IT'S FOR
- B2B, SaaS and service businesses with marketing sites on Webflow
- Agencies building or managing Webflow sites for clients who run ads
- Webflow sites using HubSpot forms or external booking tools
What's tricky on Webflow
Where Webflow tracking usually goes wrong.
- 01
Native forms don't load a new page
By default, Webflow forms hide the form and show a success message on the same page. There's no thank-you URL to track, so conversions need a listener for the success state, or a redirect set up on purpose.
- 02
Where code goes matters
Webflow has site-wide custom code, page-level code and embed elements. Tags placed in a page embed or in the wrong section load late, load twice, or only on one page, and custom code generally only runs on the published site.
- 03
CMS templates repeat everything
Code on a CMS template page runs on every item built from it. A conversion tag put on a template by mistake can fire on hundreds of pages, and template pages need their own events if they hold forms.
- 04
Leads often finish somewhere else
HubSpot forms, Calendly, Chili Piper and other booking tools load from their own domains. Without cross-domain setup or a success listener, the lead is recorded but the click that brought it is lost.
What we set up
What we connect, and what we clean up.
What we connect
- Native Webflow form successes tracked once in Google Ads, GA4 and Meta
- Embedded HubSpot forms and booking tools tracked with their own success events
- GTM installed once in site-wide code, with tags managed there instead of in page embeds
- Consent Mode v2 connected to the client's consent banner
Mistakes we fix most
- Conversions counted on a page view because a tag was pasted into a page embed
- Tags on CMS templates firing across every collection page
- Booking tools on other domains dropping the click ID and UTMs
- A consent banner that blocks nothing, or blocks GTM entirely
How we set it up
Step by step, in the client's own accounts.
Pricing
Form, booking and consent-ready tracking is in Essentials, $390 per client account. CRM attribution and offline conversions are in Revenue Connected, $890. Starts with a free tracking check.
See full pricing- 01Audit code placementSite-wide code, page code and every embed element, with what each one loads and where, including CMS templates.
- 02Install GTM onceGTM in the site-wide head and body, with hard-coded tags moved into it so there's one place to manage tracking.
- 03Track native formsA listener for each Webflow form's success state, firing once and passing the form name, or a deliberate redirect where the client prefers a thank-you page.
- 04Track embedded forms and bookingsSuccess events for HubSpot forms and booking tools such as Calendly, plus cross-domain or URL passing so the click ID survives.
- 05Set up consentConsent Mode v2 connected to the consent tool the client uses on Webflow, tested for each consent choice.
- 06Capture the sourceClick IDs and UTMs passed into hidden fields so each lead reaches the CRM with its campaign attached.
- 07Test and documentTest submissions on the published site, every form and booking path, and a test log your team can repeat after each redesign.
Outcomes
From demo request to customer
Example stages for a B2B or service client. The CRM behind the site decides what can be sent back, and the client decides what each stage is worth.
- Stage 1
Form or booking
A successful form or confirmed booking, counted once.
- Stage 2
Qualified
Marked in the CRM after a first conversation.
- Stage 3
Opportunity
Sent back with an estimated value.
- Stage 4
Customer
Closed won, sent back with the real value.
Platforms covered
Works with the client's existing stack.
- Webflow
- Google Tag Manager
- Google Ads
- Meta
- GA4
- LinkedIn Ads
- HubSpot
- Calendly
- Chili Piper
- Consent Mode v2
Something else? Tell us which tools the client uses and we'll confirm before you pay.
What we do and don't claim
We're not affiliated with or endorsed by Webflow. Webflow's forms, custom code options and consent features change over time, so we describe them generally and test on the client's published site.
Webflow tracking: questions
4 questions
It can make tracking simpler, but a thank-you page can be reached without submitting the form. We usually track the success state directly and only redirect if the client wants a thank-you page anyway.
Yes. HubSpot forms load their own code, so Webflow's form settings don't apply. We add a success listener for HubSpot forms and make sure they aren't also counted by a native form trigger.
We need someone who can edit site settings and publish, either our access to the workspace or your developer. Most tracking then lives in GTM.
We track the confirmed booking as the conversion and pass the click ID and UTMs to the booking tool, so the lead keeps its source when it reaches the CRM.
Got a client on Webflow whose numbers don't add up?
Send us one account. We review it for free and send a short video of what's working and what isn't.