Capture Google Ads Data in Framer Forms
Visitor counts and form totals alone do not show which paid campaign produced a customer or revenue. This guide explains how to attach campaign information to a Framer form submission, preserve it while a visitor browses, and use it in reports by channel, campaign, and keyword.
Why downstream attribution changes budget decisions
A kitchen-appliance seller runs two campaigns with equal spend. The blender campaign brings 200 visitors and 20 leads; the oven campaign brings 100 visitors and 10 leads. On those numbers alone, the blender campaign looks stronger. Once downstream results are attached, the picture reverses: blenders produce 2 customers and $8,000 revenue, while ovens produce 5 customers and $25,000 revenue. That is a 50% lead-to-customer rate for ovens versus 10% for blenders, $5,000 average customer value versus $4,000, $400 cost per acquisition versus $1,000, and roughly three times the return on ad spend. The lesson is to carry campaign identity through to customer and revenue outcomes, not to stop at clicks or submissions.
Step 1: Tag ad URLs consistently
First, tag every Google Ads destination URL with UTM parameters. UTM values are text appended to a URL that identify where a visitor came from. A consistent Google Ads convention is: UTM Medium = Paid search; UTM Source = Google; UTM Campaign = the campaign name; UTM Term = the ad group name; UTM Content = the specific ad. For example, a destination can carry utm_medium=paidsearch, utm_source=google, and utm_campaign=brand-campaign. Keep capitalisation and naming consistent from the start, because later reporting inherits whatever variation is entered here.
Step 2: Add six hidden fields to Framer forms
Second, add six hidden fields to each lead-capture form: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; and Landing Page Group. Hidden fields are not filled in by the visitor; they are containers for attribution values that are added automatically at submission. Check that every form that should report campaign performance has the same six fields, otherwise some submissions will arrive without attribution context. The form-controls-contract module governs the exact field behaviour for implementation.
Step 3: Populate the fields and preserve them across pages
Third, the attribution tool reads the UTM values from the landing URL and writes normalised values into the hidden fields. In a real-estate example, a visitor arriving from a brand campaign in Paid Search would produce Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign, and Channel Drilldown 3 = Luxury Homes Ad. The tool also records the first landing page, such as apexhomes.com/properties/luxury, and its group, such as properties. Because the values are stored in the browser, they remain available if the visitor moves from the homepage to a Contact Us page before submitting.
Step 4: Capture the data with the submission
Fourth, when the visitor submits the form, the attribution values are captured alongside the details they entered, such as name, company, and email. From there the combined record can be viewed in a spreadsheet through the built-in Google Sheets integration, included in a lead notification email, or sent to a CRM such as Salesforce, HubSpot, or Pipedrive for reporting and dashboards. A practical check before launch: submit a test form from a tagged ad URL, confirm all six hidden fields are populated, then submit from a different page on the same site to confirm the values persist.
What normalisation and all-channel capture add
Raw UTM capture has three common weaknesses. It only covers the tagged channel, it fails when the form is completed on a different page from the landing page, and inconsistent tagging fragments reporting. For instance, UTM_Source values of Google.com, google, and adwords would appear as three separate sources unless they are manually stitched together. Normalising those variants to Paid Search avoids that cleanup. Capturing all channels, not only Google Ads, also matters: if paid social produces more customers than paid search, that comparison is only visible when every channel uses the same fields. Landing-page and landing-page-group data add a further view of which content, such as a blog, actually generates leads and customers.
Three reports to build from the captured data
Three reports make the captured data actionable. Leads by Channel shows monthly lead volume per channel, revealing whether budget matches where leads actually originate. Customers by Google Ads Campaign shows monthly customers per campaign, separating campaigns that generate customers from those that only generate clicks. Revenue by Keyword, available when sales outcomes are tracked in the CRM, shows revenue per keyword so budget can shift toward the terms producing the most valuable customers. Together these reports move the question from which campaign got traffic to which campaign, keyword, and landing page produced customers and revenue.
| Field | Value for Google Ads |
|---|---|
| UTM Medium | Paid search |
| UTM Source | |
| UTM Campaign | Campaign name |
| UTM Term | Ad group name |
| UTM Content | Specific ad |
Use one consistent convention across all campaigns; normalise variants before reporting.
| Hidden field | Example value |
|---|---|
| Channel | Paid Search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Brand Campaign |
| Channel Drilldown 3 | Luxury Homes Ad |
| Landing Page | apexhomes.com/properties/luxury |
| Landing Page Group | properties |
Example from a brand campaign in Paid Search; landing page and group are recorded separately.
Frequently asked questions
What are the four steps to capture Google Ads data in a Framer form?
Add UTM parameters to the ad URL, add six hidden fields to the form, let the attribution tool populate those fields from the UTM values, and submit the form so the attribution values travel with the visitor's details.
Which hidden fields should a Framer form include?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
Does the data survive if a visitor browses before submitting?
Yes. Storing UTM values in the browser means a visitor who lands on the homepage and later submits a Contact Us form can still pass the original campaign data, whereas same-page-only tools would lose it.
Why normalise UTM values instead of reporting raw UTMs?
Raw values such as Google.com, google, and adwords can split one source into several report rows. Normalising them to a single channel such as Paid Search keeps reporting cleaner.
| Commercial Blenders | High-efficiency ovens | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Commercial Blenders Campaign | High-Efficiency Ovens Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |