Webflow form as a Google Ads conversion in GTM: 165 sites
Fire the Google Ads conversion when Webflow shows its success message (the .w-form-done block), or on a thank-you page that only people who sent the form can reach. Not on the click on the submit button. On 8 Nov 2026 we read the public GTM containers of the 168 study sites that run on Webflow and send Google Ads conversions. 165 had a readable Ads conversion tag. 83 of them (50.3%) fire one on a form submit or a click. 1 fires on Webflow's success message.
Check this on your own site
Free. Public tags only. Your result opens on the scan page.
How does a Webflow form say it was sent?
A native Webflow form sends its data in the background. The URL stays the same. When Webflow's server accepts the form, the form is hidden and the block with class w-form-done appears. When it fails, w-form-fail appears instead. A form with a Redirect URL in its settings sends people to that page instead.
So by default there is no thank-you URL and no dataLayer event. GTM gets nothing it can use out of the box. Most setups grab the nearest thing: a click on the button, or GTM's Form Submission trigger.
What do 165 Webflow sites fire Google Ads on?
Our 1,727-site study (scanned 5 Nov) has 233 sites built on Webflow. 168 send Google Ads conversions. On 8 Nov we read every Google Ads conversion tag in their public GTM containers: 165 had a readable one. We sorted each trigger by what it waits for. For how Webflow sites compare with WordPress, Next.js and HubSpot CMS sites, see the platform table in the study.
| Trigger | Sites | Counts a sent form? |
|---|---|---|
Webflow success message (.w-form-done becomes visible) | 1 (0.6%) | Yes |
| GTM Form Submission trigger | 38 (23.0%) | Counts the attempt, before Webflow answers |
| Button or link click | 56 (33.9%) | No |
| Submit or click, either one | 83 (50.3%) | Not on its own |
The success message is the signal Webflow gives you, and almost nobody uses it. 7 containers watch .w-form-done. Only 1 sends a Google Ads conversion from it.
The other common triggers are a thank-you page, a custom dataLayer event, and the success event of a form tool placed inside the Webflow page, mostly HubSpot. A HubSpot success event counts a sent form; the HubSpot form guide covers that setup.
Is the GTM Form Submission trigger enough?
It fires on the browser's submit event. Webflow only then sends the data, and it can still fail on a spam check or a server error. By then the Ads tag has fired. The success message only shows after Webflow says yes.
6 sites tie the trigger to a Webflow form ID such as wf-form-Book-demo. That picks the right form, but it still counts the attempt, not the result.
A click trigger is worse: it counts every press of the button, including ones the browser rejects. See click conversions.
How do I check mine?
- In GTM, list every Google Ads Conversion Tracking tag and its trigger. Note any Click, Form Submission or plain Page View trigger.
- Open DevTools, Network, filter on your
AW-number. Press the submit button with the required fields empty. An Ads request now means a click trigger. - Send the form for real with a test address. Exactly one Ads request should leave the browser, after the success message shows. Two means two triggers both count it (duplicate conversions).
- In Google Ads, check which actions are primary. Only primary actions steer bidding (Google Ads Help).
How do I fire on the success message?
- New trigger, type Element Visibility. Selection method CSS Selector, value
.w-form-done. Fire once per page. Tick "Observe DOM changes", because the block is hidden when the page loads (Tag Manager Help). - Several forms on one site? Give each success block its own class in the Webflow Designer and use that as the selector, or add a Page Path condition to the trigger.
- Put the new trigger on your Google Ads conversion tag and remove the click or Form Submission trigger from it. Add a transaction ID if you can.
- Prefer a thank-you page? Set a Redirect URL in the form settings, mark that page noindex, and fire on its exact path. It only works if nobody reaches the page another way.
- Keep the click if you want it as a secondary action with a clear name, so no bid strategy learns from it.
What can't we see from outside?
- Primary or secondary. That setting lives in Google Ads. Every number here counts tags and triggers, not what a campaign bids on.
- When a custom event is pushed. We see the name, not whether the code pushes it before or after Webflow's answer.
- What a click or form ID points to. A sorting script read the triggers by pattern, so a few may sit in the wrong row.
- Server-side tags, gtag snippets outside GTM and offline imports. 3 of the 168 sites had no readable Ads tag in a public container.
- The sample: our 1,727-site study is built from lists, not random. It leans B2B SaaS.
FAQ
Should the Google Ads conversion fire when someone clicks the Webflow submit button?
No. The click comes before Webflow knows the form went through, and rejected sends count too. Fire on the success message or a thank-you page, and keep the click as a secondary action if you want it.
Does the free Fireshift scan check Webflow forms?
It reads every Google Ads conversion in your public GTM container and flags the ones on a click or a page view. It does not test your form, and it can't see whether an Ads action is primary or secondary.
Run the free scan on your site.
Fireshift reads what your site tells Google Ads, GA4 and Meta from the outside. No install, takes seconds.