Track Duda Form Submissions as Google Ads Conversions
A Duda form submission is one of the few moments in a lead's journey where you know exactly what happened: someone filled in your form. The harder question is whether Google Ads ever learns about it. This guide walks through two server side routes — one that fires the moment the form is submitted, and one that waits until the lead becomes a paying customer in your CRM — and explains what each needs to capture along the way.
Why browser-based conversion tracking loses leads
The familiar approaches — a thank you page visit, or a Google Tag Manager event — all depend on scripts running inside the visitor's browser. That dependency is where conversions disappear. Ad blockers stop the Google Tag from loading at all. Browser privacy features, such as Safari's Intelligent Tracking Prevention, clear tracking cookies after a short window, so a Monday ad click that converts on Friday can no longer be tied back. And a lead who clicks on a phone but fills in the form on a laptop creates two sessions that browser tracking cannot join.
Server side tracking sidesteps all three because the conversion data is sent directly to Google's servers rather than through the visitor's browser. The source article, as of its publication date, cites Google figures of a 23% average increase in total recorded conversions and a 10% reduction in cost per conversion. Those are dated captured figures from the original article, not the current publisher's research and not a guarantee for your account; treat them as directional and measure your own results.
Use the table below to check which failure mode you are currently exposed to.
Decision checklist: submit-time or CRM-milestone conversion?
Before touching any settings, decide when the conversion should count. The two routes need different plumbing, and choosing late is expensive.
- Fire at submission if a form fill is a meaningful signal on its own and you want Google's bidding to optimise toward lead volume. This route needs no CRM.
- Fire at a CRM milestone if form fills vary wildly in quality and you want bidding to optimise toward revenue. This route needs the identifiers stored on the contact record and a later send step.
- Check your CRM coverage. Duda's Connect feature covers HubSpot, Mailchimp, ActiveCampaign and Constant Contact natively; anything else needs the Zapier route.
- Confirm you can edit form HTML. Duda's form builder has no dedicated hidden field type, so the four fields are added through the Edit HTML/CSS option.
- Confirm your send tool. Submit-time uses a purpose-built connector; milestone-time uses Zapier or Make.
- Decide what value to send. If you send deal value from the CRM, you unlock conversion value reporting later.
If you cannot answer the CRM-coverage and HTML-editing questions, resolve those first — they determine which route is even available to you.
Route 1: fire the conversion when the Duda form is submitted
This is the shorter path. A connector such as Converly is built for exactly this pattern: you choose a trigger (a Duda form submission on your site) and an action (a conversion sent to Google Ads), and the tool handles the rest.
What the connector does on your behalf matters, because each step is something you would otherwise build: it detects the submission, extracts the lead's name, email and phone number, hashes the personal data with SHA-256 as Google requires, and sends the payload to Google Ads. It also attaches the identifiers and context that improve matching — GCLID, GBRAID, WBRAID, IP address, browser and device among them. The richer that context, the better Google's chance of attributing the conversion to the campaign, ad and keyword that produced the click.
The trade-off is timing. You get clean, code-free server side tracking, but the conversion counts at the moment of submission — before you know whether the lead is worth anything.
Route 2: fire the conversion when the lead becomes a customer
This route captures the same identifiers but holds them until a milestone you define — a deal created, or a deal marked closed won. It has four stages.
Stage 1 — install the {{OWNER_PRODUCT_NAME}} snippet and add hidden fields. Place the {{OWNER_PRODUCT_NAME}} tracking snippet in Duda under Site Settings > Site Wide Code > Header. Then open your form, choose Edit HTML/CSS, and paste the hidden field declarations just before the closing form tag. The four fields you need are GCLID, WBRAID, GBRAID and User Agent. Duda does not offer a hidden field type in its builder, so this HTML step is the workaround; the {{OWNER_PRODUCT_NAME}} help documentation supplies the exact block to paste.
Stage 2 — let the snippet populate the fields. Once installed, the snippet records where each visitor came from. When someone arrives from a Google Ads click, it captures the identifiers Google needs and stores them in the visitor's browser. On submission, those values are written into your hidden fields and travel with the rest of the form data.
Stage 3 — land the data in your CRM. The submission, now including the identifiers, is pushed to your CRM alongside the lead's name, email, phone and other answers. Duda's native Connect integrations cover HubSpot, Mailchimp, ActiveCampaign and Constant Contact; Salesforce, Pipedrive, Zoho and others go through Zapier. The identifiers then sit on the contact or lead record, waiting.
Stage 4 — send the conversion. When the milestone is reached, Zapier or Make reads the stored values and posts the conversion to Google Ads. Both tools provide a visual mapping interface for connecting the captured fields to the corresponding Google Ads fields.
The field map below summarises what each hidden field is for.
Hidden field map for Duda forms
Four fields are added to the form HTML. Each carries a different identifier, and they are not interchangeable — omitting one narrows the set of clicks Google can match.
- GCLID — the Google Click ID attached to a standard ad click. The primary identifier for matching a conversion back to the click.
- GBRAID — the identifier used for app-to-web and similar click flows where a GCLID is not present.
- WBRAID — the web-to-app counterpart identifier, covering the reverse direction.
- User Agent — the browser and device string, which adds matching context alongside the identifiers.
All four are declared together in the same HTML block, immediately before the closing form tag. If a submission arrives with only some of them populated, that is expected: which identifiers exist depends on how the visitor clicked. What matters is that the fields are present so the values can be written when they do exist.
Four reasons the server side route outperforms browser tracking
Ad blockers. Browser-dependent methods need scripts to load. Ad blockers and privacy-focused browsers routinely prevent that, and the affected share of internet users is large — the source article cites recent estimates above 30%. Server side sends bypass the browser entirely, so there is no blocker in the path.
Safari and iOS limits. Apple's Intelligent Tracking Prevention expires tracking cookies within a couple of days. A click on Monday that converts on Friday loses its attribution under cookie-based tracking. Server side instead sends identity data — name, email, phone, Google Click ID, IP address — directly to Google, which can match the conversion regardless of elapsed time.
Cross-device journeys. A lead who researches on a phone and converts on a laptop produces two browser sessions that cannot be joined. Sending identity data directly lets Google stitch the visits together and credit the ad that started the journey.
Duplicate and messy counts. Browser tracking is vulnerable to double counting from page refreshes, missed events from slow loads, and lost events when a connection drops. A server side conversion fires only when a form is genuinely submitted, so Google Ads totals track your CRM lead numbers more closely.
Three Google Ads reports worth running once conversions are clean
Accurate conversion data is only useful if you act on it. These three reports turn the data into decisions.
Conversions by keyword. Most advertisers bid across a spread of keywords, often split by service line. This report shows which keywords actually produce conversions rather than impressions and clicks, so you can shift budget toward the profitable ones.
Conversion value by campaign. If you send deal value from your CRM, you can compare revenue by campaign rather than counting every lead as equal. The source article's example is a dental practice: a checkup is worth a few hundred dollars, while implants run to several thousand per tooth, so treating the two campaigns as equivalent distorts your bidding. Value data lets you see which campaign produced which revenue.
Conversions by geography. For local-service businesses — detailers, pool builders, awning installers, deck builders — this report breaks conversions down by country, state, city or postcode. It reveals whether leads come from areas you can actually serve. Google's location bid adjustments then let you bid more in postcodes that produce customers and pull back in areas that generate clicks but no forms.
What to verify before you go live
Server side conversions give both your manual optimisations and Google's automated bidding better inputs — but only if the data going in is accurate. Before you rely on the numbers, confirm four things: the snippet is loading on every page of the Duda site; the four hidden fields appear in the form HTML; a test submission carries the identifiers into your CRM record; and the send step fires at the milestone you chose, not earlier.
If you are still tracking thank you page visits or firing browser events through Google Tag Manager, the conversion counts will reflect that gap. Either route described above — submit-time or CRM-milestone — closes it, provided the send happens server side.
| Failure mode | What happens with browser tracking | What server side changes |
|---|---|---|
| Ad blocker active | Google Tag does not load; nothing is recorded | Conversion sent from server; blocker not in path |
| Safari / iOS cookie expiry | Cookie cleared after a couple of days; late conversion unattributed | Identity data sent directly; matching not cookie-dependent |
| Click on phone, convert on laptop | Two separate browser sessions; no join | Identity data lets Google stitch the visits |
| Page refresh or slow load | Double counts or missed events | Fires only on genuine form submission |
Failure modes as described in the original article; behaviour of specific browsers and blockers may change.
| Field | Role |
|---|---|
| GCLID | Google Click ID from a standard ad click; primary matching identifier |
| WBRAID | Web-to-app identifier for flows without a GCLID |
| GBRAID | App-to-web identifier for flows without a GCLID |
| User Agent | Browser and device string adding matching context |
Fields are declared together in one HTML block before the closing form tag; which values populate depends on how the visitor clicked.
| Report | Question it answers | Action it supports |
|---|---|---|
| Conversions by keyword | Which keywords produce conversions, not just clicks? | Shift budget toward profitable keywords |
| Conversion value by campaign | Which campaign produced which revenue? | Prioritise campaigns by return, not lead count |
| Conversions by geography | Are leads coming from serviceable areas? | Raise bids in productive postcodes, cut the rest |
Report availability depends on the conversion data you send; value reporting requires deal value from your CRM.
Frequently asked questions
Should the conversion fire at form submission or when the lead becomes a customer?
Fire at submission if a form fill is a meaningful signal and you want bidding to optimise toward lead volume; this route needs no CRM. Fire at a CRM milestone if form-fill quality varies and you want bidding to optimise toward revenue; this route requires the identifiers to be stored on the contact record and a later send step through Zapier or Make.
Why does Duda need an HTML workaround for hidden fields?
Duda's form builder does not include a dedicated hidden field type. The workaround is to open the form settings, choose Edit HTML/CSS, and paste a small block declaring the four hidden fields just before the closing form tag. The Attribution Analytics help documentation provides the exact block.
Which CRMs connect natively to Duda forms?
Duda's Connect feature covers HubSpot, Mailchimp, ActiveCampaign and Constant Contact natively. For Salesforce, Pipedrive, Zoho and others, the Zapier integration is the fallback route.
What if only some of the hidden fields are populated on a submission?
That is expected. Which identifiers exist depends on how the visitor clicked — a standard ad click produces a GCLID, while app-to-web and web-to-app flows produce GBRAID or WBRAID instead. The important thing is that all four fields are declared so values are written whenever they exist.