Capture Google Ads Data in Squarespace Forms: A Practical Setup Guide
If you run Google Ads to a Squarespace site, clicks alone do not tell you which campaigns, ad groups or keywords produced a lead or customer. This guide explains how to attach campaign information to ad URLs, carry it through a visitor's browsing session, and store it with each form submission so reporting can start from the enquiry itself.
Why form submissions need campaign context
Google Ads can show clicks and conversions inside the advertising platform, but a Squarespace enquiry normally arrives with only the details a visitor typed into the form. Without campaign context, it is hard to connect that enquiry to the ad that prompted the visit.
The approach in this guide adds UTM parameters to advertising URLs, stores the resulting attribution information in the browser, writes it into hidden fields on lead forms, and then keeps it alongside the submitted contact details. Once captured, the same information can be reviewed in Squarespace, included in notifications, or passed onward to a CRM or spreadsheet for reporting.
Step 1: Tag Google Ads URLs with UTM parameters
UTM parameters are additional text appended to a destination URL. They can identify the medium, source, campaign, ad group or keyword associated with a visit.
For example, a destination page URL can be followed by parameters indicating paid search, Google as the source, and a named brand campaign. Decide on a consistent naming convention before adding parameters, because the values entered in the URL become the values available for later reporting.
A practical mapping is:
- UTM Medium: the traffic type, such as paid search
- UTM Source: the platform, such as Google
- UTM Campaign: the campaign name
- UTM Term: the ad group or keyword grouping used for the visit
- UTM Content: the specific ad or keyword detail
Free URL-building tools can help construct tagged links, and a consistent internal guide for recommended parameter values can prevent spelling and naming variations from fragmenting reports.
Step 3: Carry attribution through the browsing session
After setup, an attribution tool can read the UTM parameters from the landing URL, store them in a browser cookie, and populate the hidden fields before submission. Storing the information in a cookie matters when the visitor does not submit a form on the first page they visit.
Consider a visitor who clicks a brand campaign ad, lands on the homepage, follows a Contact Us link, and completes the form on a separate page. A method that reads parameters only from the current page URL would lose the original campaign information. Cookie-based storage preserves it across pages.
In one illustrative example, a brand-campaign visit could produce these hidden-field values:
- Channel: Paid search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand campaign
- Channel Drilldown 3: Free account ad
The tool can also record the first landing page and its page group, such as a features page grouped under features. That adds content context to the campaign context.
Step 4: Use the captured data after submission
When the form is submitted, the populated hidden fields are stored with the visitor's name, email, phone number and other form answers. From there, the data can be used in several ways:
- Reviewed in the Contacts section of the Squarespace account
- Included in new lead notification emails
- Sent to a CRM such as Salesforce, Pipedrive, Zoho CRM or HubSpot for lead and customer reporting
- Sent to a spreadsheet and analysed there or through a connected reporting tool such as Microsoft Power BI or Google Data Studio
Before relying on the data, submit a test enquiry from a tagged URL, browse to a different page, complete the form, and confirm that every hidden field contains the expected value.
Capture other channels and landing pages too
An attribution setup can cover more than paid search. The same hidden-field structure can also record information from organic search, paid social, organic social and other channels. That makes it possible to compare all leads and customers in one view instead of reporting only on Google Ads traffic.
Landing-page capture adds another useful dimension. Recording both the exact first page and its group lets you compare broad site sections, such as a blog, with individual pages or posts inside that section.
Three useful starting reports
Three starting reports can turn captured form data into budget and optimisation decisions:
- Leads by Channel: Compare monthly lead volume across organic search, paid search, organic social and other channels. If most leads come from organic search while most spending goes to paid search, the budget balance deserves review.
- Customers by Google Ads Campaign: Compare new customers by campaign each month to identify which campaigns produce customers rather than only clicks or enquiries.
- Revenue by Keyword: Compare revenue across keywords to see which terms produce valuable customers and where higher bids or larger budgets may be justified.
Start with one report, check that its values reconcile with form submissions, and only then expand to more detailed campaign, keyword and landing-page breakdowns.
Setup checklist
A reliable setup checklist is:
- Confirm every Google Ads destination URL uses consistent UTM values
- Add the same six hidden fields to every lead form
- Test a visit that starts on one page and submits on another
- Verify the submitted record contains channel, drilldown, landing page and landing page group values
- Confirm notifications, CRM records or spreadsheets receive the fields correctly
- Build one channel report before adding campaign and keyword reports
With those checks in place, each Squarespace submission can carry the campaign and landing-page context needed to judge which advertising activity is producing enquiries and customers.