Fixing Webflow forms that submit successfully and track nothing
Webflow forms submit over AJAX and swap in a success message without any page navigation, so a conversion trigger built around a thank-you page URL never fires — the form works perfectly and the tracking records nothing. The fix is to bind the event to Webflow's actual success state rather than to a navigation that doesn't happen, and to carry the click ID as a hidden field so the lead arrives with a source attached.
Free30 minutesNo obligation
Webflow forms · what breaks
The situation, as it usually presents — Webflow forms
- 01
Forms submitting fine and conversions at zero
The classic AJAX symptom.
- 02
A thank-you page trigger that never fires
Because there's no thank-you page.
- 03
Leads arriving with no campaign source
No hidden field carrying the click ID.
Webflow forms · the fix
What changes — Webflow forms
Conversion firing on real submission success
Not on a navigation.
Click ID carried into every submission
Hidden field, populated on landing.
Multiple forms distinguished
Rather than counted as one.
Webflow forms · architecture
Why this pattern keeps recurring — Webflow forms
Webflow's form behaviour is standard for a modern site builder, and it's exactly what breaks the most commonly used trigger.
- 1
No navigation means no page-view trigger
The success message replaces the form in place. Nothing about the page changes in a way a URL trigger can see.
- 2
Webflow's native form handling can't be replaced
You work with its success state, not around it.
- 3
Hidden fields need populating on landing
The field can exist and stay empty if nothing writes the click ID into it.
- 4
All forms look alike to a generic trigger
A newsletter signup and a demo request both count as conversions unless separated.
Webflow forms · diagnose
How the root cause gets found — Webflow forms
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Submit a form and watch for a page change
There won't be one.
- 02
Compare Webflow submissions to platform conversions
For a closed month.
- 03
Check what the current trigger is bound to
Usually a URL.
- 04
Confirm hidden fields exist and are populated
Both, not just the first.
- 05
Check whether forms are distinguishable
In the event data.
Webflow forms · prove
How the work is proven — Webflow forms
Against the client's own records, not a dashboard turning green.
Source of truth
Webflow form submission records
- Conversion confirmed firing on a real submission, with no navigation.
- Click ID present in the submission data.
- Each form separable in reporting.
- Submission count reconciled against platform conversions for a closed month.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Webflow forms · free audit
What we check in the free audit
- Submit a form and watch for a page change
- Compare Webflow submissions to platform conversions
- Check what the current trigger is bound to
- Confirm hidden fields exist and are populated
- Check whether forms are distinguishable
Checked against
Webflow form submission records
Free30 minutesNo obligation
Webflow forms · when not to buy
Why there are no client numbers on this page — Webflow forms
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Webflow forms · what we deliver
What the work involves — Webflow forms
Trigger bound to Webflow's success state
The w-form-done state or the submit event.
Click ID captured on landing
And written into hidden fields on every form.
Each form given its own identifier
So they're separable in reporting.
Error states excluded
A failed submission is not a lead.
Written guarantee
95%+ tracking accuracy
Measured against Webflow form submission records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, for advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Webflow forms questions, answered
The trigger is almost certainly waiting for a thank-you page. Webflow submits over AJAX and swaps in a success message, so that page view never happens.
You can, and it's simpler. It costs you the inline success experience, and a refresh of that page will double-count unless guarded.
Read it from the URL on landing, store it, and write it into a hidden field on every form. It has to be populated, not merely present.
Yes — give each a distinct identifier in the event data. Otherwise a newsletter signup and a demo request are the same conversion.
Free · 30 min
Get Webflow form conversions firing
WhatsAppFree30 minutesNo obligation
