Skip to content

Track Typeform submissions as Google Ads conversions with server-side tracking

A Typeform submission is only useful for advertising optimisation if Google Ads can connect it back to the click that produced it. This guide explains how to capture Google Ads identifiers at submission, send the event server-side, and choose whether to optimise for leads or for paying customers.

Why browser tracking loses Typeform conversions

Thank-you page visits and browser events depend on scripts loading in the visitor's browser at the right moment. Ad blockers can stop those scripts, Safari and iOS privacy controls can clear tracking cookies after a day or two, and a person may click on a phone but submit later on a laptop. Each gap breaks the link between click and conversion, so bidding learns from incomplete data.

What server-side tracking changes

Server-side tracking sends the conversion directly to Google's servers instead of waiting for a browser event. The source cites Google data indicating a 23% average increase in recorded conversions and a 10% reduction in cost per conversion when this approach is used, because the platform receives more complete signals for automated bidding.

Option 1: Fire the conversion when the form is submitted

Decide first what success means. If every qualified form submission should count, fire the conversion at submission. A purpose-built tool such as Converly can detect the submission, collect contact details, hash them with SHA-256, and send the event with click context including GCLID, GBRAID, WBRAID and User Agent. Without such a tool, the alternative is custom JavaScript in Google Tag Manager to listen for submission, extract and hash details, and post to Google's API.

Option 2: Fire the conversion when the lead becomes a customer

If revenue matters more than raw lead volume, wait for a later CRM milestone. Install the attribution snippet in the page head, add hidden fields in Typeform's Logic tab under Personalise with data for GCLID, WBRAID, GBRAID and User Agent, and update the embed code for the embed type in use so values can pass through. When a visitor arrives from a Google Ads click, the tool stores those identifiers in the browser; on submission they are written into the hidden fields and saved with the answers. Send the submission to your CRM, where the identifiers sit on the lead record, then use a tool such as Zapier or Make to send the conversion when a deal is created, an opportunity is won, or another chosen milestone occurs, mapping each captured field to the Google Ads side.

Four practical advantages over client-side tracking

Server-side events overcome ad blockers because they do not depend on browser scripts. They survive short cookie lifetimes by using stable identity data such as email to reconnect a click with a later conversion. They can stitch together phone and laptop sessions, and they trigger only on a successful submission rather than a page load, reducing duplicates from refreshes, slow loads or dropped connections. The result should align more closely with actual lead numbers in the CRM.

Reports to run after setup

Once conversions return reliably, three views help allocate budget. Conversions by keyword show which terms produce results rather than only clicks. Conversion value by campaign, using deal or opportunity value from the CRM, separates high-value campaigns from low-value ones. Conversions by geography, down to postcode where relevant, shows whether leads cluster in profitable service areas and informs location bid adjustments. Use these reports to shift budget toward keywords, campaigns and places that produce paying customers, and to give automated bidding cleaner signals.

Pre-launch checklist

Checklist: confirm the conversion milestone, add the four hidden fields, update the embed, test a submission from a tagged click, verify identifiers land on the Typeform response or CRM record, map fields in the sending tool, and compare Google Ads conversions with CRM leads before scaling bids.

Submission vs customer timing
SituationRecommended timingWhat to send
Lead volume is the goalOn form submissionContact details plus GCLID, GBRAID, WBRAID and User Agent
Revenue quality is the goalOn CRM milestone such as deal created or wonStored identifiers plus conversion value from the CRM

Choice depends on whether the business optimises for lead volume or revenue quality.

Frequently asked questions

Why can thank-you page tracking miss Typeform conversions?

Browser-based methods can miss conversions when scripts are blocked, cookies expire quickly, or the click and submission happen on different devices. Sending the event from a server avoids relying on the browser at submission time.

What must be captured with a Typeform submission for later Google Ads reporting?

Add hidden fields for GCLID, WBRAID, GBRAID and User Agent, update the embed so values can be passed through, and ensure those values are stored with the submission or lead record for later use.

Should the conversion fire on submission or on becoming a customer?

Fire on submission when lead volume is the goal. Wait for a CRM milestone such as a created deal or won opportunity when revenue quality matters more than immediate lead count.

Which reports become useful once conversions return to Google Ads?

Use conversions by keyword to find profitable terms, conversion value by campaign to compare revenue quality, and conversions by geography to adjust bids by service area.