Track Elementor form submissions as Google Ads conversions with server-side tracking
Browser-based conversion tags often miss real leads. A server-side setup captures the original Google Ads click identifiers on the Elementor form, stores them with the lead, and sends the conversion to Google Ads either immediately or at a later CRM milestone.
Why browser tracking misses conversions
Standard browser tracking can lose conversions in three common situations. Ad blockers can stop the tag from loading, browser privacy controls can delete tracking cookies within days, and a person who clicks on a phone but submits on a laptop appears as two unrelated visits. Thank-you-page hits can also duplicate on refresh or fail if the tab closes quickly.
Server-side tracking sends the event directly between servers instead of relying on the visitor's browser. In the captured evidence, Google data was cited for an average 23% increase in recorded conversions and around a 10% reduction in cost per conversion, because bidding receives more complete conversion signals. Treat those figures as directional, dated evidence rather than a promised result for every account.
Decide when the conversion should count
Choose the trigger that matches the value of the lead. Fire on submission when the form itself signals strong intent, such as a demo request. Wait for a CRM milestone when the form is top-of-funnel and only qualified, deal-created or closed-won leads should count. Sending both can be valid, but label them as separate conversion actions so bidding is not trained on duplicate or mixed-quality events.
Setup checklist: capture, store, then send
Install the capture script in the site head, then add hidden fields to the Elementor Form widget: select the form, open Form Fields in the Content panel, add each item, and set its type to Hidden using the exact field names required by the capture tool. Capture GCLID, WBRAID, GBRAID and User Agent. When a visitor arrives from a Google Ads click, the script stores those identifiers; on submission it writes them into the hidden fields alongside name, email and phone.
Next, connect Actions After Submit to the CRM directly, through Zapier, or through a webhook. Keep the identifiers on the contact or lead record. Later, use Zapier, Make or a similar connector to listen for the chosen CRM milestone and map the stored identifiers, plus hashed lead details where required, to the Google Ads offline conversion endpoint. Verify one test lead end-to-end: click identifier present on the CRM record, conversion recorded once in Google Ads, and the correct campaign and keyword credited.
Reports to run after setup
Once conversions flow reliably, three reports become useful. Conversions by keyword show which search terms produce leads rather than only clicks, helping you cut unproductive keywords and bid more on profitable ones. Conversion value by campaign, passed from the CRM deal value, separates a small job from a large one that would otherwise look like equal conversions. Conversions by geography show which countries, states, cities or postcodes generate leads, supporting location bid adjustments for service areas that convert and tighter bids where clicks do not.
| Field | Purpose | Where it is captured |
|---|---|---|
| GCLID | Links the lead to the original Google Ads click | Hidden field on the Elementor form |
| WBRAID | Supports attribution for web-to-app and related click contexts | Hidden field on the Elementor form |
| GBRAID | Supports attribution for iOS and related click contexts | Hidden field on the Elementor form |
| User Agent | Provides device and browser context for the click | Hidden field on the Elementor form |
| Helps match the conversion across devices and delayed submissions | Standard form field, stored on the CRM record |
Field names must match the capture tool's documented names exactly; values are populated automatically, not typed by the visitor.
Frequently asked questions
Why do thank-you-page conversions miss leads?
A browser tag can be blocked, a cookie can expire before a delayed submission, and phone and desktop visits may not be linked. Sending the event from a server, using the stored click identifiers and the lead's email, avoids those browser-side breaks.
Should the conversion fire on form submission or later in the CRM?
Use form submission for high-intent requests such as a demo booking. Use a later CRM milestone, such as a qualified deal or closed-won stage, when early form fills should not all count as conversions.
Which values need to be captured on the form?
Add one hidden field for each identifier: GCLID, WBRAID, GBRAID and User Agent. The capture script populates them when the form is submitted, so they travel with the lead data into the CRM.