Skip to content

Track Formidable Forms submissions as Google Ads conversions

If Google Ads shows fewer conversions than your CRM shows leads, the gap is often a tracking problem rather than a demand problem. This guide explains how to capture Google Ads click identifiers on a Formidable Forms submission and return them to Google Ads server-side, either immediately or when a lead reaches a later revenue milestone.

Why browser tracking misses conversions

Many sites lose roughly a fifth to a third of conversions between the ad click and the recorded conversion. Three common causes explain most of the gap: ad blockers stop browser scripts, Safari and Firefox privacy systems clear tracking cookies after a few days, and people often click on a phone but submit on a laptop. A server-side event avoids all three because it is sent directly between systems rather than through the visitor's browser. Captured evidence cited in the research reports a typical lift of about 23% in recorded conversions and about 10% lower cost per conversion after switching, but your result will depend on your traffic mix and sales cycle.

Choose your conversion timing

Decide when the conversion should count. Option 1 fires on submission: a conversion tool listens for the Formidable submission, hashes contact details in the format Google requires, bundles them with the stored click identifiers, and sends the event to Google Ads and any other platforms you select. This suits teams that optimise for lead volume. Option 2 fires later: identifiers are stored on the CRM record and sent when a deal opens or a customer pays. This suits teams that optimise for revenue, because deal value can travel with the conversion. The checklist below works for both options; only the final trigger differs.

Capture the click identifiers on the form

Install the capture script in the site head, then add four hidden fields to the form: GCLID, WBRAID, GBRAID, and User Agent. In the Formidable builder, drag Hidden Field from the Miscellaneous section for each identifier. Hidden fields are available in the free Lite version. Note that Formidable assigns numeric IDs to hidden inputs, so follow the tool's Formidable-specific guidance to ensure values are written correctly. When a visitor arrives from a Google Ad, the script reads the click parameters from the URL and the User Agent, stores them in browser cookies, and writes them into the hidden fields at submission alongside the lead's name, email and other answers.

Move the identifiers to your CRM and on to Google Ads

Send the submission to your CRM through a direct Formidable integration or a connector such as Zapier. The identifiers should land on the contact or lead record, not just in a notification email, so they remain available at a later milestone. For Option 2, connect your CRM to Google Ads through Zapier or Make: listen for the chosen milestone, map GCLID, GBRAID, WBRAID and User Agent plus name and email into the offline conversion fields, and attach deal value where available. For Option 1, verify the conversion tool is receiving the submission trigger and that test submissions appear in Google Ads.

Validate one event per real submission

Server-side sending also fixes quieter browser failures: page refreshes firing twice, slow connections losing the pixel, and tabs closed before a script runs. One genuine submission should produce one event, so dashboard conversions start aligning with CRM lead counts. Before scaling spend, run a short validation: submit test forms with and without ad parameters, confirm each identifier appears on the CRM record, confirm one conversion per submission in Google Ads, and check that a later-milestone conversion carries the correct value.

Use the data to improve campaigns

With trustworthy conversion data, three reports become practical. Conversions by keyword shows which search terms produce leads rather than only clicks, helping you shift budget away from non-converting terms. Conversion value by campaign attaches deal revenue so a campaign winning a few hundred dollars per tax return can be compared fairly with one winning a multi-year advisory engagement. Conversions by geography shows which countries, states, cities or postcodes generate leads, letting you raise bids where profitable customers live and reduce spend where clicks never become forms. Accurate server-side data also feeds automated bidding, whereas thank-you-page or browser-only events can mislead both manual and automated decisions.

Browser-based vs server-side conversion tracking
Failure modeBrowser-based trackingServer-side tracking
Ad blockersScripts blocked before they fireEvent sent outside the browser
Safari / Firefox privacy clearingCookies deleted within days, breaking later attributionIdentifiers stored first-party and sent with the event
Click on phone, convert on laptopTreated as two unrelated visitorsEmail can match the conversion to the original click
Refresh, slow load, closed tabDuplicate or missing eventsOne submission produces one event

Comparison summarises failure modes described in the research; outcome figures are dated captured evidence, not guarantees.

Choosing when to send the conversion
DecisionFire on submissionFire at CRM milestone
Best forLead-volume optimisation and fast feedbackRevenue optimisation and longer sales cycles
Identifiers neededGCLID, WBRAID, GBRAID, User AgentSame four, stored on the CRM record
Value dataUsually lead onlyDeal or customer value can be attached
Typical connectorConversion tool listening for form submissionZapier or Make listening for a CRM event

Choose based on sales cycle and optimisation goal; both require the same four captured identifiers.

Frequently asked questions

Why do browser-based Google Ads conversions miss Formidable Forms submissions?

Browser-based tags depend on scripts loading in the visitor's browser at the moment of conversion. Ad blockers can stop those scripts, privacy controls can delete the cookies linking click to conversion within days, and a click on one device followed by a form on another looks like two unrelated visits. Sending the event from the server removes the browser from that chain.

Which identifiers must be captured from the ad click?

Four values are needed for the later server-side match: GCLID, WBRAID, GBRAID, and User Agent. They are captured when the visitor arrives from a Google Ad, stored in the browser, and written into hidden fields when the form is submitted so they travel with the lead record.

Should the conversion fire on form submission or later in the CRM?

Choose the timing that matches your sales cycle. Sending on submission gives immediate feedback for lead volume. Waiting until a deal is created or a customer pays lets you attach revenue value, but requires the identifiers to survive in your CRM until that later milestone.

Do I need a paid Formidable Forms licence for hidden fields?

Hidden fields are available in Formidable Forms Lite, so a paid Formidable licence is not required for this step. Because Formidable uses numeric IDs for hidden field inputs, the capture tool needs its specific Formidable guidance to write values correctly.

What reporting becomes possible after server-side tracking is working?

Once reliable conversions return to Google Ads, you can compare keywords by conversions, campaigns by conversion value, and regions by conversions. Those views support keyword budget decisions, value-based campaign funding, and location bid adjustments.