Skip to content

How to track FormAssembly submissions as Google Ads conversions

FormAssembly is a flexible form builder, but its submissions do not automatically become Google Ads conversions. If you rely on thank-you-page visits or browser-side events, ad blockers, browser privacy limits, and cross-device journeys can hide a meaningful share of real leads. This guide explains how to capture the identifiers Google Ads needs, pass them through FormAssembly and your CRM, and send conversions server-side so your bidding and reporting rest on cleaner data.

Why server-side conversion tracking matters

Browser-based tracking depends on scripts loading and cookies surviving. Ad blockers can stop the Google Tag from firing. Safari's privacy features can limit cookie life to roughly a day, so a click on Monday and a form submission on Thursday may never be connected. And when someone clicks an ad on a work laptop but converts later on a phone, the original click is easily lost.

Server-side tracking avoids those browser-side failure points by sending conversion data directly to Google's servers. Google has reported that this approach typically produces a 23% average increase in recorded conversions and a 10% reduction in cost per conversion, because its algorithms learn from more complete data. Treat those figures as Google's reported averages, not a guarantee for your account.

Choose when the conversion should fire

There are two practical timing models. Pick the one that matches how your sales process works.

Submission-time tracking records a conversion as soon as the FormAssembly form is submitted. This is the simplest option and works well when a form submission is the meaningful action you want Google Ads to optimize toward. A visual workflow tool such as Converly can listen for the submission, pull the lead's details, hash them with SHA-256, and send the conversion to Google Ads along with identifiers such as GCLID, GBRAID, WBRAID, and User Agent.

CRM-stage tracking records a conversion later, when a lead becomes a qualified opportunity or a paying customer. This is better when raw leads vary widely in quality and you want Google Ads to optimize toward revenue rather than form fills. It requires carrying the identifiers from FormAssembly into your CRM and then triggering the conversion from there.

A simple decision rule: if your sales team treats every form submission as equally valuable, start with submission-time tracking. If lead quality varies enough that you would rather bid toward closed deals, use CRM-stage tracking.

Set up the hidden fields in FormAssembly

For CRM-stage tracking, the first job is to make sure each FormAssembly form carries the identifiers your CRM and Google Ads will need. Add four hidden fields to the form, using these exact names so the tracking script can find and populate them later. The names are case-sensitive and must match the list below character for character, because a mismatch is the most common reason a hidden field arrives empty in the submission record. A quick way to check is to submit a test form and confirm that each field appears in the stored response with a value rather than a blank. If a field is missing entirely, the field name is probably wrong; if it is present but empty, the script is not reaching the form or the visitor did not arrive from an ad click. The four fields are: GCLID, which is the Google Click Identifier attached to the ad click; GBRAID, the Google browser identifier used when a click identifier is unavailable; WBRAID, the Web-to-App or app-to-web identifier for journeys that cross between a browser and an app; and User Agent, the browser and device string that helps Google match the conversion. In FormAssembly, click Add Content, hover over Question, and choose Hidden Field, then name each one to match the list above. Step-by-step instructions for the exact click path are available in the product's help documentation. Once the fields exist, install the tracking snippet on your website. When a visitor arrives from a Google Ad, the snippet captures the identifiers and stores them in the browser. When the visitor submits the form, the values are written into the hidden fields and submitted alongside the lead's name, email, phone number, and other answers.

Carry the identifiers into your CRM

After submission, send the full record to your CRM. FormAssembly's native connectors, such as its Salesforce or HubSpot connectors, can map the hidden fields onto the contact or lead record. A general automation tool like Zapier can do the same job if you prefer a connector-agnostic route.

The goal is to have the identifiers sitting on the CRM record next to the lead's name, email, and phone number. That way, when the lead reaches the milestone you care about — a deal being created, an opportunity being marked qualified, or a customer being won — the identifiers are still available to send back to Google Ads.

Send the conversion to Google Ads

When the chosen milestone occurs, push the conversion to Google Ads. Automation tools such as Zapier and Make can watch your CRM for the trigger event and map the stored identifiers — GCLID, GBRAID, WBRAID, User Agent, and the rest — to the matching fields in Google Ads.

If you are sending from your CRM, attach the deal or opportunity value to the conversion as well. That single step turns a simple conversion count into a revenue signal, which is what makes the reporting in the next section useful.

Three reports worth running once conversions are flowing

Clean conversion data is only useful if you act on it. These three reports cover the most common budget and targeting decisions.

Conversions by keyword. If you bid on several keyword groups across different campaigns, this report shows which terms actually produce conversions rather than just clicks. Shift budget toward the keywords that convert and pause or reduce the ones that do not.

Conversion value by campaign. When you pass deal value from your CRM, you can compare revenue by campaign rather than raw lead count. A construction company, for example, might find that a bathroom-renovation campaign produces many leads but far less revenue than a whole-home-build campaign. Comparing value rather than volume makes the budget decision clearer.

Conversions by geography. Local-service businesses can break conversions down by country, state, city, or postcode. If clicks are coming from areas outside your service radius, use location bid adjustments to bid more aggressively in profitable postcodes and reduce or stop spend where leads never convert.

Implementation checklist

  • Confirm whether you want conversions at form submission or at a later CRM milestone, and write down the trigger event before you build anything, so the setup and the reporting agree on what counts as a conversion. A useful test is to ask whether a form fill and a closed deal should carry the same weight in bidding; if not, plan for the CRM-stage route from the start rather than retrofitting it later. - Add hidden fields for GCLID, GBRAID, WBRAID, and User Agent to every relevant FormAssembly form, naming them exactly as listed so the tracking script can populate them. - Install the tracking snippet site-wide so identifiers are captured before the form is submitted, not only on the pages that host a form. - Map the hidden fields onto the contact or lead record in your CRM, and confirm the values survive any lead-to-contact conversion your CRM performs. - Configure the conversion trigger in Zapier, Make, or your CRM's native Google Ads integration, and decide in advance which record event fires it. - Attach deal value to the conversion if you want revenue-based reporting, since a conversion count alone cannot distinguish a large project from a small one. - Verify that test submissions appear in Google Ads before scaling spend, and check that the identifiers arrive intact rather than blank.

Frequently asked questions

Should I track the conversion when the form is submitted or when the lead becomes a customer?

Track at submission when every form fill is equally valuable to your business. Track at the CRM stage when lead quality varies and you want Google Ads to optimize toward qualified opportunities or closed revenue. The CRM-stage route requires carrying the identifiers through FormAssembly into your CRM.

Which identifiers does Google Ads need from FormAssembly?

The core set is GCLID, GBRAID, WBRAID, and User Agent. These are captured in hidden fields and passed through to your CRM and then to Google Ads. Google uses them to match the conversion back to the original ad click.

Why not just count thank-you page visits?

Thank-you-page counting depends on browser scripts and cookies. Ad blockers, Safari's privacy limits, and cross-device journeys can each break that chain, so a meaningful share of real conversions may never be recorded. Server-side tracking sends the conversion directly to Google and avoids those browser-side gaps.

Can I send conversions from my CRM without writing code?

Yes. FormAssembly's native connectors can move the hidden-field data into Salesforce or HubSpot, and automation tools such as Zapier or Make can trigger the Google Ads conversion when a deal is created or a customer is won. Those tools also provide a mapping interface for the identifier fields.