Capture UTM Parameters in Squarespace Forms
A Squarespace form can collect a name and email without telling you whether the visitor arrived from a paid search ad, an organic article, or a direct visit. This guide shows a practical four-step setup for writing campaign and landing-page attribution into Squarespace hidden fields, then passing that data to a CRM or other tool. It also explains what the approach captures beyond raw UTM strings and where simpler URL-based capture tends to fall short.
Four-step setup for Squarespace form attribution
The workflow has four parts: install the attribution script on the site, create hidden fields in each form, let the script fill those fields, and submit the form so the data travels with the lead. The steps below follow that order.
Step 1 — Add the script to your Squarespace site. After starting the trial, you receive a small code snippet. In Squarespace, open Settings, then Advanced, and paste the snippet into the Code Injection area. If your site already loads scripts through Google Tag Manager, that route is also available.
Step 2 — Create six hidden fields. Squarespace lets you drag a Hidden field type into a form. Add one for each of these names: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. The names matter because the script writes to matching fields.
Step 3 — Let the script populate the fields. Once the hidden fields exist, the script fills them automatically when a visitor completes a form. The values depend on the UTM parameters and referrer information available for that visitor.
Step 4 — Submit and route the data. When the visitor presses submit, the hidden-field values go with the form submission. From there, Squarespace's built-in integrations or a connector such as Zapier can send the record to Salesforce, HubSpot, Zoho CRM, or another sales and marketing tool.
What each hidden field represents
The six fields split attribution into two groups. The Channel and Channel Drilldown fields describe how the visitor found the site. The Landing Page fields describe where the visitor entered.
- Channel — the broad category, such as Paid Search, Organic Search, Organic Social, Referral, or Direct.
- Channel Drilldown 1 — the next level down, often the platform or network, such as Google.
- Channel Drilldown 2 — a campaign-level label, such as a brand campaign.
- Channel Drilldown 3 — a further detail such as an ad or keyword label.
- Landing Page — the full path of the page where the visitor first arrived.
- Landing Page Group — the subdirectory or section of that landing page.
A useful way to remember the split: the Channel fields answer "how did they get here?" and the Landing Page fields answer "where did they land?" Keeping both lets you compare campaign performance against content performance in the same CRM record.
Worked example: from ad click to form submission
Suppose a visitor searches for a file-sharing solution, clicks a paid ad at the top of the results, and lands on a product features page. They browse to a demo request form and submit it.
If the ad URL carried UTM parameters, the hidden fields could end up with values like these:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = the advertiser name used in the campaign
- Landing Page = the full features-page path
- Landing Page Group = Features
The exact values depend on the UTM parameters present in the ad URL. The point of the example is the structure: one record now shows both the campaign path and the entry page, so a sales team can see which ad and which page produced the lead.
Why persistent attribution beats raw UTM capture
Reading tags straight off the current address bar is the least durable option. Tags describe the page the visitor first opened, not the page they are on now. Someone who clicks an ad, lands on a homepage, then follows a "Get A Quote" button to a separate form page has already left the tagged URL behind. At submit time there is nothing in the address bar to read. A method that parks the attribution values in the visitor's browser keeps them available for the form, whichever page it sits on.
Tagged campaigns are also only part of the picture. Plenty of leads never touch a UTM link: they find the site through a search result, a social post, a bookmark, or a link from another site. A capture method that classifies every visit — not just the tagged ones — can still label those arrivals as Organic Search, Organic Social, Direct, or Referral and attach the label to the submission.
Click identifiers form a third layer. Values such as Google Click ID (GCLID), Microsoft Click ID (MSCLKID), and Facebook Click ID (FBCLID) can ride along with the lead into the CRM. Later, when that lead reaches a milestone like a signed contract, the stored identifier can be returned to the ad platform as an offline conversion. Optimization then has a customer signal to work with, not just a form-completion count.
Finally, entry-page context is worth keeping. Recording both the full landing page and its parent section lets a report separate one article from an entire content area. A team comparing a single blog post against a whole /blog directory, or a specific feature page against a broader /features section, can see which content earns attention and which earns revenue — and shift budget on that evidence rather than on pageviews alone.
Decision checklist before you build
Use this checklist to confirm the setup fits your reporting goal.
- Do you need attribution on leads that arrive without UTM tags? If yes, choose a method that categorizes all traffic, not only tagged campaigns.
- Do visitors often submit forms on a different page from the one they landed on? If yes, confirm the method stores attribution in the browser rather than reading only the current URL.
- Will you send click IDs to an ad platform for offline conversion matching? If yes, verify that GCLID, MSCLKID, or FBCLID can be captured and passed through your CRM.
- Do you want to compare content sections, not just campaigns? If yes, include both the full landing page and the landing page group in your field set.
- Can your form tool and CRM accept the six field names without renaming them? If not, map them deliberately before launch so the data does not arrive in the wrong place.
Three reports to build once the data is flowing
Attribution data becomes useful when it is grouped into reports a team can act on. Three common views are:
- Leads by channel. Tally new leads each month under each channel label. The result is a volume comparison across paid search, organic search, organic social, and the rest — a quick check on whether spending tracks where leads actually originate.
- Opportunities by Google Ads campaign. Attribute each sales opportunity back to the campaign that first brought the lead in. Campaigns that pile up raw leads but rarely reach a qualified conversation stand out next to those that convert, which is the signal for moving budget.
- Customers by Facebook ads network. A Meta campaign can surface on Facebook, Instagram, Messenger, or WhatsApp, and each placement behaves differently. Counting closed customers per network shows which placement is worth funding.
Each report depends on the same underlying field values, so the setup work pays off across multiple views rather than a single dashboard.
Trial and plan details
Commercial terms vary by provider and by the date a reader signs up, so this page does not state a trial length, price, support arrangement, or service guarantee as a commitment. Treat those as questions to settle before you build: how long an evaluation period lasts, what a paid plan costs at your expected form volume, what response times or channels are included, and whether any uptime or outcome promise applies. Confirm the answers directly with the provider you choose, and record the agreed wording wherever your team keeps vendor terms. A short internal note covering evaluation period, pricing basis, support scope, and any guarantee is usually enough to keep the setup decision auditable.
Frequently asked questions
What data can a Squarespace form capture beyond UTM parameters?
The setup described here can also capture the landing page path, the landing page group, and click identifiers such as GCLID, MSCLKID, and FBCLID. It can categorize visitors from organic search, organic social, direct traffic, and referrals even when no UTM parameters are present.
Why do UTM parameters disappear when the form is on a different page?
UTM parameters live in the URL of the page where the visitor landed. If the visitor navigates to another page before submitting a form, the original parameters are no longer in the address bar. A method that stores attribution in the browser avoids that gap.
How are click IDs used after the form submission?
The click ID travels with the lead into the CRM. When that lead reaches a meaningful sales milestone, such as becoming a paying customer, the identifier can be sent back to the ad platform as an offline conversion. That lets the platform optimize for customers rather than form views.
Do the hidden field names have to match exactly?
Yes. The script writes to fields by name, so Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group should be created with those exact labels. If your CRM uses different field names, map them during the integration step rather than renaming the Squarespace fields.