Track Fluent Forms Submissions as Google Ads Conversions
Fluent Forms makes it easy to collect leads, but getting those leads counted correctly in Google Ads is where most setups fall short. Browser-based methods such as thank-you-page visits or tag-manager events can miss a meaningful share of real conversions because of ad blockers, privacy restrictions and device switching. This guide shows a server-side approach: capture the Google Ads identifiers with each Fluent Forms submission, store them alongside the lead, and send the conversion to Google Ads either at submission time or later when the lead becomes a customer.
Why server-side tracking matters
The core difference is where the conversion event is assembled. Browser-side tracking has to win a fight it often loses: a script must load, survive any content blocking, keep its cookie alive long enough, and stay attached to the same device the ad was clicked on. Each of those steps is a place where a real lead can disappear from the count.
Server-side tracking changes the order of operations. The identifiers are captured when the visitor arrives, stored with the lead, and sent to Google from your own systems rather than from the visitor's browser. The conversion record no longer depends on a script firing at the moment of submission.
Google has reported that server-side tracking typically produces a 23% average increase in total recorded conversions and a 10% reduction in cost per conversion, because the bidding algorithms receive more complete conversion signals. Those are Google-reported averages, not a guarantee for any individual account; confirm current figures before quoting them as your own benchmark.
Choose when the conversion should fire
The first decision is timing. Firing on form submission is simpler and suits businesses that treat a lead as the conversion. Firing later, when a deal is created or a customer pays, gives Google Ads a revenue-quality signal but requires a CRM in the middle.
Use this checklist to decide:
- Fire at submission if your sales cycle is short, your form is the main conversion event, or you do not yet have a CRM pipeline.
- Fire at a CRM milestone if you need to distinguish raw leads from qualified opportunities or paying customers.
- Fire both only if you deliberately want separate conversion actions for lead volume and revenue quality.
- Whichever you choose, send the conversion server-side rather than relying on a browser pixel.
Option 1: Fire when the form is submitted
A purpose-built connector such as Converly can send a server-side conversion to Google Ads each time a Fluent Forms form is submitted. You select the Fluent Forms submission as the trigger and the Google Ads conversion as the action. The connector detects the submission, extracts the lead's name, email and phone number, hashes that data with SHA-256, and forwards it to Google Ads together with context such as GCLID, GBRAID, WBRAID and User Agent. More matching context improves the chance that Google attributes the conversion to the correct campaign, ad and keyword.
This route avoids custom code and avoids needing to work directly with Google's API, while still delivering the server-side benefits described above.
Option 2: Fire when a lead becomes a customer
If Fluent Forms feeds a CRM such as Salesforce, HubSpot or Pipedrive, you can carry the Google Ads identifiers through the form submission and fire the conversion later, when a deal is created or marked closed won. The workflow has four stages.
- Install the tracking snippet on your site and add hidden fields to your Fluent Forms forms. The four fields needed are GCLID, WBRAID, GBRAID and User Agent. In the Fluent Forms editor, drag a Hidden Field from the Advanced Fields section for each one, and set each field's Default Value to the value the tracking tool expects. Hidden Fields are available in the free version of Fluent Forms. The snippet and any trial terms come from the tool owner; see the owner-supplied trial terms before publishing a signup offer.
- The snippet watches where each visitor comes from. When someone arrives from a Google Ads click, it captures the identifiers and stores them in the browser. On form submission, those values are written into the hidden fields and captured with the rest of the lead data.
- Send the submission to your CRM. Fluent Forms Pro includes native integrations for HubSpot, Salesforce, Pipedrive, ActiveCampaign, Zoho and others, with Zapier as a fallback. The identifiers are stored on the contact or lead record.
- When the lead reaches the milestone you care about, send the captured data back to Google Ads as a conversion. Zapier or Make can connect to most CRMs and provide a visual mapping screen for matching the captured values to the correct Google Ads destination fields.
Hidden field map
The table below lists the four hidden fields and what each one carries. Set the Default Value for each field to the exact name the tracking tool documents; the field labels alone are not the values.
Four reasons server-side conversions are more reliable
- Content blockers cannot intercept the conversion. A browser script can be stopped before it runs; a server-side send is not in the browser to be blocked. The original material cites research putting ad-blocker usage above 30% of internet users, but does not name the study, so treat that percentage as an unverified captured figure rather than a current benchmark.
- Short-lived cookies stop being the weak link. Apple's Intelligent Tracking Prevention clears tracking cookies after a couple of days, which breaks the link between an early click and a later conversion. Server-side matching can lean on the lead's email as a stable identifier instead.
- Cross-device journeys are joined. A lead who clicks on a phone and converts on a desktop can still be matched when identity data is sent directly to Google.
- Duplicate and missing events are reduced. Server-side tracking fires on a successful form submission rather than on a thank-you page load, so counts align more closely with real leads in the CRM.
Three reports worth running once conversions flow
Conversions by keyword shows which search terms actually produce leads rather than clicks, so budget can move toward profitable terms. Conversion value by campaign becomes possible when you pass deal value from the CRM; it matters because a tax-filing client and a CFO-advisory client are not worth the same to an accounting firm. Conversions by geography breaks results down by country, state, city or postcode, which is especially useful for local service businesses; Google's location bid adjustments then let you bid more in areas that produce paying customers and less in areas that only produce clicks.
Getting the data right
Server-side conversion tracking gives you cleaner data for manual decisions such as keyword and location bids, and it gives Google's automated bidding more accurate signals. The benefit depends on sending accurate conversion data in the first place. Whether you fire at submission or at a CRM milestone, send the conversion from the server rather than from the browser.
| Field | What it carries | Where to add it |
|---|---|---|
| GCLID | Google Click Identifier for the ad click | Fluent Forms Hidden Field (Advanced Fields) |
| WBRAID | Web-to-app identifier used by Google Ads | Fluent Forms Hidden Field (Advanced Fields) |
| GBRAID | App-to-web identifier used by Google Ads | Fluent Forms Hidden Field (Advanced Fields) |
| User Agent | Browser and device context for matching | Fluent Forms Hidden Field (Advanced Fields) |
Field labels are not the values. Each field's Default Value must be set to the exact name the tracking tool documents.
Frequently asked questions
Do I need Fluent Forms Pro to add hidden fields?
No. Hidden Fields are available in the free version of Fluent Forms. Fluent Forms Pro is only needed for the native CRM integrations; Zapier can cover CRMs without a native integration.
Which Google Ads identifiers should I capture?
The four fields are GCLID, WBRAID, GBRAID and User Agent. Capturing all four gives Google more context for matching the conversion to the original click.
Should the conversion fire at submission or in the CRM?
Fire at submission if the form fill is your conversion event. Fire at a CRM milestone if you want Google Ads to learn from qualified opportunities or paying customers rather than raw leads.