How to track Framer form submissions as Google Ads conversions
Framer makes it easy to publish a site and collect leads, but Google Ads conversion tracking for those forms is where many setups break down. Browser-based methods can miss submissions because of ad blockers, privacy restrictions or cross-device journeys. This guide explains how to capture the identifiers Google Ads needs, pass them through your form and CRM, and send conversions server-side so your reporting reflects the leads you actually receive.
Why server-side tracking matters for Framer forms
The common alternatives are to count visits to a thank-you page or to fire an event through Google Tag Manager. Both depend on scripts running in the visitor's browser, and that environment is not fully under your control. The practical consequence is a gap between the clicks you pay for and the conversions Google can see.
Server-side tracking changes the path. Instead of hoping a browser event is observed, you send Google a direct message containing the lead's details and the identifiers from the original ad click. That message is not blocked by ad blockers or browser privacy settings in the same way. Google has reported that server-side tracking typically produces a 23% average increase in total recorded conversions and a 10% reduction in cost per conversion, because its algorithms learn from more complete conversion data. Those figures are Google's own reported averages, not a guarantee for every account.
A useful way to think about the difference: browser tracking asks whether a page loaded; server-side tracking asks whether a known person submitted a form and, later, whether that person became a customer.
Choose when the conversion should reach Google Ads
There are two practical moments to send a conversion, and the right choice depends on your sales cycle and how your team qualifies leads. A useful way to decide is to sketch both routes on paper and compare which one matches how your business actually earns revenue. The worked example below is hypothetical and is meant to show the decision logic, not a measured result from any account. Suppose a Framer site collects enquiries for a service business, and the team typically speaks to a lead before quoting. In that case, a submission-time conversion would overstate success, because many enquiries never become customers. A milestone-time conversion would better reflect the outcome Google should optimise toward. If, by contrast, the form itself books a paid appointment, submission-time tracking is the closer match to the real value event. Either way, the identifiers Google Ads needs must travel with the form data, and the automation that sends the conversion must map them correctly. A dedicated conversion tool can handle the submission-time route without custom code: you choose the Framer form submission as the trigger and a Google Ads conversion as the action. The tool collects the visitor's name, email and phone, hashes the personal data with SHA-256, and sends the conversion along with identifiers such as GCLID, GBRAID, WBRAID and User Agent. That extra data improves the chance Google can match the conversion back to the campaign, ad and keyword that produced the click. Converly is one example of a tool built for this kind of visual conversion flow, and its documentation is the place to confirm current capabilities before relying on it. For the milestone route, capture the Google Ads identifiers with the form submission, store them on the CRM record, and send the conversion only when a meaningful event occurs, such as a deal being created or marked won. This keeps Google's optimisation focused on qualified outcomes rather than raw lead count. Use this checklist to decide: Is a form submission itself a sale or a booked appointment? If yes, submission-time tracking is usually sufficient. Does your team qualify leads before they become customers? If yes, send the conversion from the CRM at the qualification or won stage. Do you want to optimise bids toward revenue rather than lead volume? If yes, include conversion value from the CRM. Can your CRM and automation tool pass the captured identifiers back to Google Ads? If not, fix that handoff before switching to milestone tracking.
Step-by-step: capture Google Ads data in a Framer form
The CRM-milestone route has four stages. The exact field names and control configuration are supplied in the accompanying form-controls contract; the steps below explain the workflow around them. As a hypothetical walkthrough, imagine a Framer site with a contact form and a CRM that stores each lead as a record. The goal is for the identifiers from the original ad click to end up on that record, so a later automation can send the conversion to Google Ads. 1. Install the tracking snippet and add hidden fields. After signing up for the free trial of the tracking product you choose, place the snippet you receive on your site. In Framer, add an input to your form, switch it to Hidden in the right-hand panel, and give it the required name. Repeat for each identifier the contract specifies, including GCLID, WBRAID, GBRAID and User Agent. Field-by-field instructions are available in the product's help documentation. 2. Let the snippet write the values. When a visitor arrives from a Google Ad, the snippet captures the identifiers Google Ads needs and stores them in the visitor's browser. When the visitor submits the Framer form, those values are written into the hidden fields and saved with the submission. 3. Send the submission to your CRM. Framer's native integrations or a third-party connector such as Zapier can pass the form data, including the hidden-field values, into your CRM alongside the lead's name, email and phone. The identifiers then sit on the contact or lead record. 4. Send the conversion to Google Ads. When the chosen milestone occurs, an automation tool such as Zapier or Make sends the stored identifiers and conversion details back to Google Ads as a server-side conversion. Map each captured identifier to the corresponding field in the Google Ads conversion action. A field/control map helps here: keep the hidden-field names exactly as the contract specifies, confirm that the CRM stores each identifier on the record rather than in a note, and check that the automation passes the same values without truncation or renaming. Before going live, test the full path with a sample submission and confirm that each identifier arrives intact at the final step.
What server-side tracking fixes, and what it does not
The core mechanism is identity matching. Instead of relying on a cookie that lives in one browser, you send Google a stable identifier tied to the person who submitted the form. That single change resolves several distinct problems at once.
Blocked scripts. If the Google tag never loads because an extension or browser setting stops it, no browser-side event can fire. A server-side message travels a different path and is not subject to that block.
Short-lived cookies. Safari's Intelligent Tracking Prevention can clear tracking cookies within a day or two. When that happens, a click and a later conversion are no longer linked. An email-based identifier survives that window, so a delayed conversion can still be credited.
Device switches. A lead who clicks on a phone and submits on a desktop produces two separate browser sessions. Identity data sent server-side lets Google join them.
Duplicate and messy data. Browser tracking can double-count on page refreshes or lose events when connections drop. Server-side tracking records a conversion when the form is actually completed, which keeps Google Ads counts closer to real lead numbers.
It does not remove the need for accurate identifiers. If the hidden fields are missing, misnamed or not carried into the CRM, the conversion cannot be matched reliably. It also does not make every conversion attributable; consent, identifier availability and CRM data quality still affect match rates.
Three reports that become useful once conversions are accurate
Accurate conversion data is only useful if you act on it. These three reports are a practical starting point.
Conversions by keyword. If you bid on several keyword groups across campaigns, this report shows which terms produce real conversions rather than impressions and clicks alone. It helps you decide where to increase budget and where to pause spending.
Conversion value by campaign. When you send conversion value from your CRM, you can compare revenue rather than lead count. A renovation company, for example, may find that a bathroom-remodel campaign produces more leads but a whole-home renovation campaign produces far more revenue per customer. Treating those campaigns as equal would misallocate budget; attaching deal value makes the difference visible.
Conversions by geography. For local businesses such as contractors, dental practices or accounting firms, this report breaks conversions down by country, state, city or postcode. You can then use location bid adjustments to bid more in profitable areas and reduce or stop spending in areas that generate clicks but no forms.
These reports depend on the conversion data being complete. If you continue to rely on thank-you-page visits or browser events, the reports will understate performance and may point budget in the wrong direction.
Frequently asked questions
Do I need Google Tag Manager to track Framer form submissions in Google Ads?
No. The server-side approach described here uses a snippet to capture identifiers and a hidden-field setup in Framer, then sends the conversion through an automation tool or a dedicated conversion tool. Google Tag Manager is one alternative, but it requires custom triggers and tags and still runs in the browser, so it is subject to the same blocking and privacy limits.
Which identifiers should I capture in the hidden fields?
The core set is GCLID, WBRAID, GBRAID and User Agent. The exact field names and required configuration are defined in the accompanying form-controls contract. Keep those names unchanged so the snippet and the downstream automation can read the values correctly.
Can I send a conversion only when a lead becomes a customer?
Yes. Capture the identifiers with the Framer form submission, store them on the CRM record, and trigger the Google Ads conversion from the CRM when the relevant milestone occurs, such as a deal being created or marked won. This is usually better when your sales team qualifies leads before they become customers.
What does the 23% increase in recorded conversions refer to?
It is Google's reported average increase in total recorded conversions when advertisers use server-side tracking, alongside a reported 10% reduction in cost per conversion. It is an average reported by Google, not a promise that every account will see the same result.
Why does browser-based tracking miss conversions?
Ad blockers can stop the Google tag from loading. Safari's privacy features can limit tracking to a short window. A visitor may click on one device and convert on another. Page refreshes and dropped connections can also create duplicate or missing events. Server-side tracking avoids the browser dependency by sending the conversion directly to Google.