Capture Google Analytics Data in Framer Forms in 4 Steps
Visitor traffic alone does not show which campaigns produce enquiries. Adding attribution fields to a Framer form lets each submission carry its source, so leads can be compared by channel, campaign and landing page instead of being grouped as unknown.
Why form submissions need source data
Google Analytics shows how visitors reached a site, but a form submission on its own usually contains only the details a person typed. An attribution script bridges that gap: it identifies the visitor's source on arrival, groups it into a channel similar to those used in Google Analytics, and writes that information into hidden form fields. When the form is sent, the source data travels with the name, email and other answers, and can then be viewed in Framer, included in a notification, or exported to a CRM or spreadsheet for reporting.
Four-step setup and pre-launch checklist
Work through the setup in order. Each step depends on the previous one, so a missing hidden field will leave a gap in every later report.
- Add hidden fields to the form. Insert six fields that visitors do not see: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Hidden fields let a script add data without asking the visitor for extra work.
- Let the attribution script fill those fields. Once the script is on the site, it populates the fields automatically whenever a visitor completes the form.
- Submit and capture. When a visitor presses Submit, Framer stores the script-supplied source data alongside the answers the lead entered.
- Send the data onward and report. Use Framer's Google Sheets integration or a tool such as Zapier to pass submissions to a CRM or other tools, then build reports from the captured fields.
Checklist before testing: all six hidden fields are present, field names match the script's expected names exactly, a test submission arrives with source values filled in, and the destination CRM or spreadsheet receives those fields rather than only the visible answers.
Worked example: a paid-search enquiry
Consider an accountant advertising tax services through Google Ads. A visitor clicks an ad, lands on a services page and submits an enquiry form. The hidden fields would be filled approximately as follows:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Tax Services Campaign
- Channel Drilldown 3: Accountant
- Landing Page: the initial page the visitor arrived on, for example www.hunteraccounting.com.au/services/tax
- Landing Page Group: the broader section, for example /services
That single submission now shows not only who enquired, but which search engine, campaign, ad group and entry page produced the lead. The same pattern applies to other channels, where drilldowns can carry campaign, ad group or keyword detail.
What the captured fields mean
Two kinds of information are captured. Channel data records the origin, such as Organic Search, Paid Search or Referral, with drilldowns adding campaign, ad group or keyword detail where available. Landing-page data records the exact page that first drew the visitor and the group it belongs to, such as a blog article and its /blog section. Keeping those two families separate matters: channel answers where the lead came from, while landing page answers which content they arrived through.
Three reports to build first
Start with three reports once submissions are flowing into a CRM or spreadsheet:
- Leads by Channel: a monthly view of which channels produce the most leads. If most leads arrive through Organic Search while most budget goes to Paid Search, that mismatch is a prompt to reconsider allocation.
- Opportunities by Google Ads campaign: which campaigns create genuine sales opportunities, so spending can stay with performers and pause or scrap weak campaigns.
- Customers by Facebook Ads network: how many customers came from each placement across Facebook, Instagram, Messenger, WhatsApp and other networks, to guide where ad spend should go.
These reports turn captured form data into decisions about effort, budget and content, rather than leaving every enquiry unattributed.
Wrap up
Attribution fields only help if they are present on every form that matters and survive the journey to the reporting tool. Add the six hidden fields to each Framer form, confirm a test submission carries source values, and check that notifications, exports or CRM records include them. Before committing to a plan, review the current trial length, setup effort and pricing directly with the provider, since these terms can change.