Skip to content

Track ClickFunnels form submissions as Google Ads conversions with server-side tracking

If a visitor submits a ClickFunnels form after clicking a Google ad, you need that submission — not just a thank-you page view — returned to Google Ads. Server-side tracking does this by sending lead details and the Google Click ID (GCLID) directly to Google, so the conversion can be tied to the campaign, ad and keyword that produced it even when browser tracking fails.

Why browser tracking loses conversions

Browser-based methods share three weaknesses. Ad blockers can prevent the Google Tag loading at all. Safari and other privacy features can clear tracking cookies after a day or so, breaking the link if the lead converts days later. Cross-device journeys also break: a click on a phone followed by a form submission on a laptop cannot be joined by browser data alone. Research cited in the captured evidence suggests browser methods can miss up to 30% of conversions. Counting thank-you page visits or submit-button clicks adds another error: a failed submission can be counted, then counted again when the visitor corrects it and resubmits.

What server-side tracking changes

Server-side tracking sends the conversion from your systems to Google rather than relying on a script in the visitor's browser. For a form submission, the payload can include the lead's name, email and phone number hashed with SHA-256, plus the GCLID and other attribution signals. Google can then match the lead to the original click without depending on cookies surviving in the browser. The captured evidence cites Google data showing an average 23% increase in recorded conversions and a 10% reduction in cost per conversion with server-side tracking, because the bidding algorithms receive more complete conversion data.

Decide when the conversion should fire

Choose the timing that matches the business event you want Google Ads to optimise for. If a submitted lead is the goal, trigger the conversion at submission. If only paying customers count, store the GCLID on the contact record and send the conversion later when the deal or customer milestone occurs. The second route needs the GCLID captured at form time, even though the conversion is sent afterwards.

Option 1: Send the conversion at form submission

Use a visual builder rather than custom tag code. Create a workflow with a trigger for a new ClickFunnels form submission and an action to record a conversion in Google Ads. Map the respondent's name, email and phone number, hash them with SHA-256, and include the GCLID and attribution signals. This avoids building the trigger, variable and tag logic manually in Google Tag Manager and avoids handling the hashing and API details yourself.

Option 2: Store the GCLID and send the conversion when the lead becomes a customer

Add the capture snippet to the funnel's Header Code section. In the ClickFunnels Editor, add an Input element below the last visible field, set its Input Type to Custom Type, and give it a custom identifier such as gclid. That hidden field is where the click ID will be stored. When a visitor arrives from a Google ad, the capture tool stores the GCLID in the browser so it remains available if they browse or return later. On submission, it writes the GCLID into the hidden field, so the value is saved with the lead's name, email, phone and other form data. Send that record through ClickFunnels integrations or a tool such as Zapier into your CRM and keep the GCLID on the contact record. Later, when a deal is created, closed or the lead becomes a customer, use a connector such as Zapier or Make to send the stored GCLID to Google Ads and log the conversion at that milestone. Most CRMs do not offer a native Google Ads integration, so the connector's field-mapping screen is where the captured GCLID is matched to the correct Google Ads API field.

Checklist: what good server-side tracking should survive

Server-side sending removes the main causes of under-counting. Because the message goes directly to Google's servers, ad blockers and privacy restrictions cannot block it. Because the lead details and GCLID travel with the conversion, the click-to-conversion link survives cookie deletion in Safari and iOS. Because matching uses lead information rather than a single browser session, a phone click and a later laptop submission can be credited to the same ad. And because the conversion is logged only on a genuine submission, duplicate counts from button clicks or failed attempts are avoided.

Three reports to run once conversions flow back

Conversions by keyword shows which search terms produce leads rather than only impressions and clicks, helping you shift budget toward keywords that work. Conversion value by campaign, using deal value from the CRM, shows revenue per campaign — for example, one campaign producing $1,000 and another $10,000 — so budget follows customer value, not lead volume alone. Conversions by geography breaks results down by country, state, city or postcode, which is useful for local services; Location Bid Adjustments can then increase bids where leads convert and reduce or stop spend where clicks never become customers. Accurate conversion data supports both manual bidding changes and automated bidding.