Track Squarespace form submissions as Google Ads conversions
Squarespace forms can become reliable Google Ads conversion signals when the ad-click identifiers are captured with the lead and sent server-side. This guide explains the two timing choices, the data to preserve, and the reports that become useful once conversions are matched back to campaigns.
Why browser tracking loses conversions
Browser-based tracking asks the visitor's browser to report the conversion. That chain breaks when scripts are blocked, tracking storage expires quickly, or the person finishes on a different device. Basic approaches such as tracking thank-you page visits can miss up to 30% of your conversions, and the source article cites recent estimates putting ad-blocker use at over 30% of internet users. A server-side send moves the event from your system directly to Google, so the browser does not need to stay available for the conversion to be recorded. The result is more complete conversion data for bidding decisions; the source article cites Google data showing a typical 23% increase in recorded conversions and a 10% reduction in cost per conversion.
Two timing choices for sending the conversion
Option one sends the conversion as soon as the form is submitted. A trigger watches for the submission, extracts contact details, hashes them as Google requires, and forwards the event with click context such as GCLID, GBRAID, WBRAID, IP address and device information. Option two waits for a later CRM milestone. Click identifiers are stored on the lead record at submission, then sent when a deal is created, closed, or another chosen outcome occurs. Use the first route for lead volume; use the second when downstream revenue should influence optimisation.
CRM route: preserve identifiers from click to customer
For the CRM route, install the capture snippet on the site (in Squarespace, the code goes in Website Tools > Code Injection > Header), add hidden fields for GCLID, WBRAID, GBRAID and User Agent to the form, and populate them by inserting a small block of custom code beneath the form using the exact snippet from the help docs. When a visitor arrives from a Google ad, those values are stored in the browser and written into the fields at submission. Push the submission to a CRM such as Salesforce, HubSpot, Pipedrive, ActiveCampaign or Zoho via an integration tool, keeping the identifiers on the contact record. At the chosen milestone, map the stored values to the Google Ads conversion fields.
Four failure modes server-side sending avoids
Server-side sending helps in four distinct ways. It is not interrupted by ad blockers because the event does not rely on a browser script. It does not depend on a cookie surviving for days, so a click on Monday can still be credited for a Friday conversion. Identity and click data let Google connect sessions across devices. And because the event fires on a successful submission rather than a page load, refreshes, slow loads and dropped connections are less likely to create duplicates or gaps.
Pre-launch checklist
Before launch, check that each hidden field label matches what the capture tool expects, submit a test form from a tagged ad click, confirm the identifiers appear on the CRM record, trigger the milestone, and verify the conversion appears in Google Ads. Also confirm hashed contact fields are present and that conversion value is included only when the CRM route supplies a real deal value. To read the geography report, start at country or state level, then drill to postcode and compare conversion counts against your service area; a postcode with clicks but no recorded conversions is a candidate for a lower location bid, while one that consistently produces paying customers justifies a higher bid.
| Timing | Trigger | Data needed | Best for |
|---|---|---|---|
| At submission | Squarespace form submitted | Contact details, hashed fields, GCLID, GBRAID, WBRAID, IP and device context | Lead-volume optimisation |
| At CRM milestone | Deal created, closed, or customer becomes paying | Stored click identifiers plus deal value where available | Revenue-weighted optimisation |
Comparison summarises the two routes described in the source; tool availability requires owner confirmation.
| Report | Question it answers | Action it supports |
|---|---|---|
| Conversions by keyword | Which keywords produce conversions, not just clicks? | Shift budget toward profitable keywords |
| Conversion value by campaign | Which campaigns produce higher-value customers? | Prioritise campaigns with stronger revenue |
| Conversions by geography | Which regions produce leads in service areas? | Adjust location bids by postcode or region |
Reports depend on conversions being matched back to clicks; value report requires CRM deal value. Read geography from country or state down to postcode, then compare against your service area before adjusting location bids.
Frequently asked questions
Why do thank-you page and browser events miss conversions?
Browser-based methods depend on scripts loading in the visitor's browser. Ad blockers, short-lived Safari tracking limits, and switching devices between click and form submission can break the link to the original click. Sending the event from a server avoids those browser interruptions.
Should I send the conversion at form submission or later in the sales cycle?
Choose the milestone that matches the value you want Google Ads to optimise for. Send at submission for lead volume, or wait for a CRM milestone such as a created or closed deal when you want downstream value to drive bidding.
What data needs to travel with a Squarespace lead for later server-side sending?
The workflow described captures GCLID, WBRAID, GBRAID and User Agent in hidden fields, stores them with the lead in a CRM, then maps those values when sending the conversion from the CRM milestone.