Track Webflow Form Submissions as Google Ads Conversions
A reliable setup starts by deciding what counts as a conversion, then preserving the ad-click identifiers from the landing visit until that moment. That preserves the link between a campaign click and a later form or customer event, even when blockers, browser privacy limits or a device change would break a browser-only tag.
Why browser-only tracking loses conversions
Browser-based tracking has three common failure modes. Ad blockers can stop the Google Tag from firing at all. Browser privacy features can limit tracking to a day or two, so a click followed by a form a week later is lost. A click on a work computer and a form on a home computer or phone also breaks the link. Server-side sending moves the conversion from the browser to Google's servers, so those browser conditions do not prevent delivery. Captured evidence in the source cites Google data showing a typical 23% average increase in recorded conversions and a 10% reduction in cost per conversion with server-side tracking, and studies suggesting browser methods can miss up to 30% of conversions.
Decide when a lead counts as converted
Choose the trigger that matches your business definition. Immediate submission suits teams that value every qualified form fill. A later CRM milestone suits teams that only want paying customers counted, and it also lets you send conversion value from the deal or opportunity. The checklist below works for either choice; only the final trigger changes.
Workflow: capture identifiers, carry them through, send server-side
Install the attribution snippet on the site, in Webflow under Project Settings, Custom Code, Head Code. Add hidden fields to the form for GCLID, WBRAID, GBRAID and User Agent. Because Webflow has no dedicated hidden-field element, add a code block at the bottom of the form and paste the supplied code into it. When a visitor arrives from a Google Ads click, the tool stores those identifiers in the browser. When the visitor submits the form, the values are written into the hidden fields and captured with the submission alongside the name, email, phone and other entered details. For the CRM route, push the submission, including those identifiers, to the CRM via an integration tool such as Zapier or Make, so the values sit on the contact or lead record. When the chosen milestone occurs, map the stored GCLID, WBRAID, GBRAID and User Agent values to the Google Ads conversion fields in Zapier or Make and send the conversion server-side.
Immediate-submission route without custom code
For immediate submission, a purpose-built server-side tool can listen for the Webflow submission, extract the contact details, hash them with SHA-256 as Google requires, and post the conversion to Google Ads. It can also include click identifiers, UTM parameters and User Agent, giving Google more context to match the conversion to the campaign, ad and keyword that produced the click. Without such a tool, the equivalent manual route involves custom JavaScript in Google Tag Manager to listen for the submit event, extract and hash the details, and post to Google's API, which typically needs a developer.
What accurate conversion data unlocks
Accurate conversion data improves reporting, because campaigns can then show conversions, conversion rate, cost per conversion and return on ad spend, sliced by campaign, ad group, keyword, ad or country. It also improves automated bidding: smart bidding needs reliable conversion data to learn what a good searcher looks like, otherwise it bids aggressively on the wrong people. It supports better retargeting, because people who landed but did not convert can be re-engaged through Search bid adjustments, Display campaigns or YouTube ads aimed only at that audience.
Three reports to run once conversions flow
Conversions by keyword shows which search terms produce conversions rather than only clicks, helping shift budget toward profitable terms. Conversion value by campaign, available when value is sent from the CRM, separates high-value and low-value customers instead of treating them as equal, and shows revenue, cost per conversion and return on ad spend per campaign. Conversions by geography breaks results down by country, state, city or postcode, which is especially useful for local services, and location bid adjustments can then raise bids where paying customers come from and reduce them where they do not.
Bottom line
Server-side conversion data supports both manual decisions, such as bidding higher on proven keywords or regions, and automated bidding, which needs trustworthy signals to learn. Thank-you page visits and browser-fired events do not provide that reliability. Whether the trigger is the form submission itself or a later paying-customer milestone in the CRM, sending the conversion server-side is the step that delivers the improvement.
| Route | Trigger | Identifiers carried | Best when |
|---|---|---|---|
| Immediate submission | Webflow form submitted | GCLID, WBRAID, GBRAID, User Agent plus hashed contact details | A form fill is your conversion |
| CRM milestone | Deal created or opportunity closed won | Same identifiers stored on the CRM lead record, plus optional conversion value | Only paying customers should count |
Both routes send server-side; they differ only in trigger timing.
Frequently asked questions
Why do thank-you page and tag-manager methods miss Webflow form conversions?
Browser-based methods can miss conversions when ad blockers stop the tag, browser privacy limits shorten tracking windows, or the click and form happen on different devices. Sending the conversion from the server avoids relying on the browser tag firing at conversion time.
Should the conversion fire on form submission or later in the CRM?
Fire at submission if a form submission is your conversion definition. Wait for a CRM milestone such as a created deal or closed-won opportunity if only paying customers should count, and carry the captured identifiers through to the CRM so they are available at that later point.
What data travels with the conversion?
The workflow described captures GCLID, WBRAID, GBRAID and User Agent, plus the lead details entered in the form. In the immediate-submission route, contact details are hashed with SHA-256 before being sent to Google Ads.