Skip to content

Track WPForms submissions as Google Ads conversions, server-side

A form fill is only useful for Google Ads optimisation if the ad click behind it can be matched reliably. This guide explains two timing choices — firing on submission or firing at a later CRM milestone — and the checklist needed to carry click identifiers from the landing page through to the conversion event.

Why browser-based tracking undercounts form fills

Most Google Ads setups record a conversion when a browser loads a thank-you page or fires a tag. That chain breaks in predictable ways: ad blockers stop the script, Safari and iOS clear tracking cookies within a couple of days, and a click on a phone followed by a form fill on a laptop looks like two unrelated visits. The result is a conversion count that understates real demand, so bidding decisions are made on incomplete evidence.

Server-side tracking changes where the event is created. Instead of depending on the visitor's browser, the conversion is sent from a server to Google Ads together with identifiers captured earlier. Captured Google data reported in the underlying material puts the typical gain at a 23% average increase in recorded conversions and a 10% reduction in cost per conversion, because the bidding system learns from fuller data. Treat those as reported benchmarks to validate against your own account, not as a guarantee.

Two timing choices: on submission or at a CRM milestone

Choose based on what you want Google Ads to optimise for. If a submitted form is a good proxy for value, fire immediately. If only some leads become paying customers, wait for that milestone so the algorithm optimises for revenue rather than volume. The table below compares the two routes.

Checklist for the CRM-milestone route

For the later-milestone route, work through this checklist in order:

  1. Install the attribution snippet on the site so landing visits are captured.
  2. Add four hidden fields to each WPForms form — GCLID, WBRAID, GBRAID and User Agent — using the exact field names the attribution tool expects. Hidden fields are a WPForms Pro feature, so confirm your licence first.
  3. On submission, the captured identifiers are written into those hidden fields and travel with the name, email, phone number and other answers.
  4. Send the submission to your CRM through a native WPForms integration or an automation connector, so the identifiers sit on the lead or contact record.
  5. When the lead reaches your chosen milestone — deal created, deal closed, or paying customer — trigger the Google Ads conversion from the CRM via an automation tool, mapping each captured identifier to the matching Google Ads field.

A common failure point is step 2: fields added with the wrong names stay empty, and the later conversion has nothing to match against. Test with a real ad click, submit a test form, and check the CRM record before going live.

Checklist for the on-submission route

For immediate firing, a visual conversion builder can replace hand-written Tag Manager logic. You select the WPForms submission as the trigger and the Google Ads conversion as the action. The platform then extracts the lead's details, hashes them, and sends them to Google's API along with the click identifiers, so the conversion can be matched to the campaign, ad and keyword that drove the visit. The trade-off is dependency on that platform's connector and field mapping, which should be tested with a sample submission before relying on it for bidding.

What server-side firing fixes

Server-side events are fired only when a form is genuinely submitted, which avoids double-counting from page refreshes, lost events on slow loads, and dropped connections mid-load. Because the event originates from a controlled server environment, ad blockers and browser privacy settings cannot intercept it. Identity data such as email also lets Google connect a phone click to a later laptop conversion, and to link a conversion back to a click that happened days earlier despite cookie deletion.

Three reports to run once conversions flow

Accurate conversions support three practical decisions. Conversions by keyword or search term show which terms produce leads rather than clicks, guiding where to add budget. Conversion value by campaign — possible when deal value is passed back from the CRM — separates high-value customers from low-value ones that look identical in a raw conversion count. Conversions by geography, down to postcode level, reveal whether leads come from areas you can profitably serve, and feed location bid adjustments that raise bids where profitable customers cluster and cut spend where clicks never convert.

Before you switch on bidding changes

Better conversion data improves both manual decisions and automated bidding, but only if the data is complete. If your current setup relies on thank-you page loads or browser-fired tags, audit it against the failure modes above before trusting the numbers. Then pick a timing route, run the checklist with a test submission, and confirm the identifiers appear on the CRM record or in the conversion payload before scaling spend.

Choosing when to fire the conversion
Fire on form submissionFire at CRM milestone
TriggerWPForms submission detected by a conversion platformDeal created, deal closed, or paying customer in the CRM
Identifiers carriedGCLID, WBRAID, GBRAID, User Agent plus lead details, hashed before sendingIdentifiers stored on the CRM record at submission, sent later with conversion value if available
Best forBusinesses where a form fill is a strong value signalBusinesses where only downstream customers represent real value
Main riskOptimising for low-quality form fillsDelay between click and conversion; requires CRM and automation connectors

Comparison of the two timing routes described in the captured workflow; tool availability must be confirmed by the owner.

Frequently asked questions

Why do thank-you page and Tag Manager setups miss WPForms conversions?

Browser-based setups can miss conversions when ad blockers stop scripts, Safari or iOS removes tracking cookies after a short period, or a visitor switches devices between click and form submission. Sending the event from a server, with identifiers captured at form submission, avoids relying on the browser to stay intact.

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

You can fire the conversion immediately when the form is submitted, or wait until a later CRM milestone such as a created deal, a closed deal, or a paying customer. The choice depends on whether you want Google Ads to optimise for form fills or for downstream revenue events.

Which identifiers need to travel with a WPForms submission?

The identifiers named in the workflow are GCLID, WBRAID, GBRAID and User Agent. They are captured on the landing visit, written into hidden fields when the form is completed, and then carried with the lead data to the CRM or conversion platform.

Do I need a particular WPForms plan for hidden fields?

WPForms hidden fields are described as a Pro feature, so a Pro or higher licence is needed for that approach. Check the current WPForms plan details before starting, as plan features can change.

What reports become useful after server-side conversions are flowing?

Once conversions are flowing, useful cuts include conversions by keyword or search term, conversion value by campaign when deal value is passed back, and conversions by geography for local bid adjustments. Each answers a different budget question.