Track Unbounce form submissions as Google Ads conversions
Send Unbounce form activity to Google Ads server-side so conversions are matched to the original click even when browser tracking would fail. You can record the conversion at submission, or wait for a CRM milestone such as a created deal or a new customer.
Why browser tracking is fragile
Unbounce pages work well for Google Ads traffic because the message can mirror the ad and search term. The weak point is measurement: thank-you-page and browser-event setups depend on a tag loading in the visitor's browser. Ad blockers, Safari privacy limits, device switching and slow or refreshed pages can break or duplicate that signal. Sending the conversion server-side moves the handoff to a controlled channel and includes lead details that help Google match the event to the original campaign, ad and keyword.
Choose when the conversion should count
Pick the timing that matches the value you want Google Ads to optimise for. Submission-time sending gives faster feedback for lead volume. CRM-milestone sending gives cleaner feedback when only deals or customers should count. Either route should pass the click identifiers and, where appropriate, hashed lead details rather than relying on a browser event alone.
Two practical setups
For submission-time tracking, a conversion builder can listen for the Unbounce form event, collect name, email and phone, hash those details with SHA-256, and forward them with GCLID, GBRAID, WBRAID, User Agent and session detail. That combination is what improves matching back to the exact click. For CRM-milestone tracking, install the capture snippet through Unbounce Script Manager, add hidden fields named GCLID, WBRAID, GBRAID and User Agent, let the tool populate them on arrival, send the submission through a native integration, webhook or connector such as Zapier or Make, store the identifiers on the CRM record, and trigger the Google Ads conversion when the deal or customer milestone occurs.
What server-side sending fixes
Server-side sending helps in four distinct ways. It bypasses ad blockers because the event does not depend on a browser tag. It survives short Safari tracking windows because lead details can be matched to the click instead of a cookie. It joins cross-device journeys because identity data can stitch a phone click to a later laptop form. It reduces messy counts because a conversion is logged on an actual submission or CRM milestone, not on a thank-you-page load that might refresh or fail.
Reports to run after setup
Once conversions are tied to clicks, three views become decision-ready. Conversions by keyword show which terms produce leads rather than clicks. Conversion value by campaign, when CRM deal size is passed back, shows revenue contribution instead of treating every lead equally. Conversions by geography show whether leads come from areas you serve, supporting location bid adjustments for local businesses.
Pre-launch checklist
Before launch, confirm the hidden-field names match the capture tool, test a submission from a Google Ads click, check that identifiers land on the CRM record, verify the conversion fires only at the chosen milestone, and compare Google Ads totals with CRM lead counts. If totals diverge, inspect duplicate triggers, missing identifiers and mismatched field mapping first.
| Situation | Better timing | Why |
|---|---|---|
| You optimise for lead volume | At form submission | Fastest feedback for bidding |
| Only deals or customers count as success | At CRM milestone | Avoids optimising for low-value leads |
| Leads move through a long sales cycle | At CRM milestone | Identifiers are stored until value is known |
Decision aid based on the two workflows described; tool availability requires owner confirmation.
| Failure mode | Browser tracking | Server-side sending |
|---|---|---|
| Ad blocker active | Tag may never load | Event sent outside the browser |
| Safari tracking window expires | Click link can be lost after a day or two | Lead details support matching |
| Phone click, laptop form | Sessions cannot be joined | Identity data can stitch sessions |
| Thank-you page refresh | Possible duplicate count | Logged on submission or milestone |
Comparative summary of the failure modes described in the captured material.
Frequently asked questions
Why can browser tracking miss Unbounce conversions?
Browser-based setups can miss conversions when an ad blocker stops the tag, Safari limits tracking after a day or two, a visitor switches device, or a page refresh creates duplicate or lost events. Server-side sending avoids relying on the browser for that step.
Should the conversion be sent at form submission or later?
Choose form submission when you want Google Ads to learn from every qualified lead immediately. Choose a later CRM milestone when a deal or customer outcome is a better measure of value than a form fill.
Which identifiers travel with the lead?
The workflow captures GCLID, GBRAID, WBRAID and User Agent in hidden fields, carries them with the lead into the CRM, then maps them when a connector sends the conversion back to Google Ads.
What reports become more useful after this setup?
Useful views include conversions by keyword, conversion value by campaign when CRM value is passed back, and conversions by geography for location bid adjustments.