How to track Gravity Forms submissions as Google Ads conversions
Gravity Forms is a capable lead-capture tool, but getting its submissions counted accurately in Google Ads takes more than a thank-you page trigger. This guide explains a server-side approach: capture the identifiers Google Ads needs, pass them through your form and CRM, and send the conversion when it actually matters to your business.
Why server-side conversion tracking is worth the setup
When conversion tracking lives entirely in the visitor's browser, three things tend to go wrong. First, ad blockers stop the Google Tag from loading at all, so whatever the visitor does on your site never reaches Google. Second, browser privacy measures — Safari's tracking prevention is the usual example — shorten the lifespan of tracking cookies, so a click that converts a few days later loses its connection to the ad. Third, the click and the conversion often happen on different machines: someone researches on a work laptop and fills in the form at home, and the browser has no way to join those two sessions.
Server-side tracking changes where the work happens. Rather than hoping a script in the browser fires and survives, you send the conversion details to Google from a server environment that ad blockers and privacy settings cannot reach. Google's own published figures put the typical gain at a 23% average increase in total recorded conversions and a 10% reduction in cost per conversion, attributed to the bidding algorithms receiving more complete data. Those are Google-reported benchmarks, not a promise for any particular account.
Choose when the conversion should fire
There are two sensible moments to send a conversion to Google Ads, and the right one depends on your sales cycle.
At form submission. The conversion fires as soon as the Gravity Form is submitted. This is the simplest option and suits businesses where a lead is the meaningful outcome. A visual workflow tool such as Converly can be configured with a trigger on the form submission and an action that sends the conversion to Google Ads; behind the scenes it hashes the lead's details with SHA-256 and attaches identifiers such as the GCLID, GBRAID, WBRAID, and user agent. That extra context improves the odds Google can match the conversion back to the campaign, ad, and keyword that produced the click.
When a lead becomes a customer. If your Gravity Forms feed a CRM such as Salesforce or Pipedrive, you can delay the conversion until a deal is created or closed. This gives Google Ads a signal tied to revenue rather than raw lead volume, which is more useful when lead quality varies widely.
Use the comparison below to decide.
Form-submit vs CRM-stage conversions
| Consideration | Fire at form submission | Fire at CRM stage |
|---|---|---|
| Setup complexity | Lower — one trigger on the form | Higher — CRM integration plus a trigger on deal stage |
| What Google optimizes toward | Leads | Customers or revenue |
| Best for | Short sales cycles, high lead-to-customer consistency | Long cycles, wide variation in lead value |
| Data needed | GCLID, GBRAID, WBRAID, user agent | Same identifiers plus the CRM record and deal value |
| Main risk | Optimizing toward low-quality leads | Delayed signal and more moving parts to maintain |
The CRM-stage workflow, step by step
1. Install the tracking snippet and add hidden fields. After signing up for the tracking tool, place its snippet on your site. Then add hidden fields to each Gravity Form for GCLID, WBRAID, GBRAID, and User Agent. In the Gravity Forms editor you drag in Hidden fields and give each one the specific name the tool requires; the vendor's help documentation lists the exact names.
2. Let the tool populate the fields. When a visitor arrives from a Google Ad, the snippet captures the identifiers Google Ads needs and stores them in the visitor's browser. On form submission, those values are written into your hidden fields and submitted along with the rest of the form data.
3. Send the data to your CRM. Gravity Forms' native integrations or a connector such as Zapier can pass the captured identifiers to your CRM alongside the lead's name, email, phone number, and other answers. The identifiers then sit on the contact or lead record until you need them.
4. Send the conversion to Google Ads. When the chosen milestone is reached — a deal created, a deal closed, or another stage — a connector such as Zapier or Make can trigger the conversion in Google Ads and map the stored identifiers to the corresponding fields. The same connectors work with most CRMs, so the pattern is portable.
Field and control map
| Field | Where it is captured | Where it ends up | Why it matters |
|---|---|---|---|
| GCLID | Browser, on ad click | Hidden form field → CRM → Google Ads | Primary click identifier for Google Ads |
| GBRAID | Browser, on ad click | Hidden form field → CRM → Google Ads | App-to-web click identifier |
| WBRAID | Browser, on ad click | Hidden form field → CRM → Google Ads | Web-to-app click identifier |
| User Agent | Browser, on ad click | Hidden form field → CRM → Google Ads | Helps Google match the conversion to the original session |
| Deal value | CRM | Conversion value in Google Ads | Enables revenue-weighted reporting |
A useful sanity check: if a hidden field is empty on a submitted entry, the snippet likely did not load or the field name does not match the vendor's required name.
Four reasons this approach outperforms browser tracking
Blocked scripts no longer matter. Anything that runs in the page can be stopped by an ad blocker; a message sent from your server to Google's cannot. The source material cites research suggesting more than 30% of internet users run some form of ad blocker — a dated figure worth re-checking before you quote it.
Cookie expiry stops breaking the chain. Safari's tracking prevention typically clears tracking cookies within a couple of days, which severs the link between click and conversion. With server-side tracking, the lead's email can act as a lasting identifier that ties the conversion back to the original click no matter how much time passed.
Device changes stop losing credit. A prospect who clicks on a phone and converts on a desktop weeks later looks like two unrelated sessions to a browser. Identity data sent from the server lets Google join them.
Counts stop drifting from reality. Page refreshes can double-count a browser event, and slow loads can drop one entirely. A server-side trigger fires once, when the form is genuinely completed, so Google Ads totals track your real lead numbers more closely.
Three reports worth running once conversions are flowing
Conversions by keyword. Most accounts bid on several keyword themes spread across campaigns. This report shows which of those themes actually end in a conversion rather than stopping at impressions and clicks, so you can tell the profitable ones from the rest and move budget toward the winners.
Conversion value by campaign. When deal value travels from your CRM into Google Ads, campaigns can be compared on revenue instead of raw conversion count. A law firm is a good illustration: a customer won through a contract-review campaign and one won through a litigation campaign are rarely worth the same, and this report makes the gap visible so budget decisions reflect it.
Conversions by geography. Results can be viewed at country, state, or city level, and drilled down to individual postcodes. That tells you whether leads are arriving from areas you can serve profitably. From there, location bid adjustments let you raise bids in the postcodes that convert and cut or stop spend in areas that produce clicks but never a completed form.
Getting the data right matters more than the tool
Sending conversions to Google Ads pays off twice: it gives you the numbers to make manual decisions, such as bidding higher on certain keywords or regions, and it gives Google's automated bidding better data to work with. But the benefit depends on accuracy. Thank-you-page tracking and browser-only events leave gaps, and the bidding algorithms learn from incomplete signals as a result. Whichever timing you choose — form submission or CRM milestone — send the conversion server-side and verify that the identifiers arrive intact.
Frequently asked questions
Do I need to write code to track Gravity Forms submissions in Google Ads?
Not necessarily. A tracking tool can capture the identifiers and write them into hidden form fields, and a connector such as Zapier or Make can forward the conversion to Google Ads. Building the same flow by hand in Google Tag Manager would require custom code to listen for submissions, extract and hash lead data, and call the API.
What is the difference between GCLID, GBRAID, and WBRAID?
All three are click identifiers Google Ads uses to match a conversion back to the ad that produced it. GCLID covers standard web clicks, while GBRAID and WBRAID cover app-to-web and web-to-app journeys respectively. Capturing all three, plus the user agent, improves match rates.
Can I send a conversion value with a Gravity Forms submission?
Yes, if you are sending the conversion from your CRM. The deal or opportunity value can be passed as the conversion value, which lets you compare revenue by campaign rather than treating every lead as equally valuable.
Why are my Google Ads conversions lower than my actual form submissions?
Browser-based tracking can miss submissions when ad blockers prevent the tag from firing, when privacy features expire cookies before the conversion, or when the click and the form submission happen on different devices. Server-side tracking with stored identifiers closes many of those gaps.