If you advertise a Squarespace site with Google Ads, you need conversion events Smart Bidding and reporting can trust. Squarespace’s form builder is opinionated—you don’t always get clean server-side confirmations—so advertisers usually land on one of three patterns that still work reliably in production.
This guide lays out Method 1 (thank-you URL), Method 2 (Google Tag Manager form submission tracking when you can’t or won’t redirect), and Method 3 (tracking submit-button clicks when nothing else sticks). Pick based on UX constraints, duplicate-risk tolerance, and how much access you have to Squarespace’s redirects and injected scripts.
Method 1: Thank You Page
Redirecting verified visitors to a single confirmation URL is still the simplest path: one page load equals one intentional conversion boundary, debugging is painless, and you can fire either the Google Ads tag directly or a GA4 purchase-style event keyed on URL.
- Create or reuse a lightweight confirmation URL on Squarespace (for example
/contact-confirmed) with a short reassurance message—not indexed for SEO if needed (no-index or draft depending on workflow). - Point each lead form “post-submit behavior” to redirect to that path. Squarespace’s community documents how to toggle redirect-after-success (redirect after successful form submission).
- Ensure the Google Ads tag fires sitewide via Google Tag Manager in Code Injection Header or Ads’ snippet if you deliberately keep installs minimal—but avoid double-firing GA4 if you bundle both routes.
- In Google Ads, create (or reuse) a Website conversion using Page load / URL matching the thank-you slug. Label it clearly (“Lead – Contact TY”) so imported GA4 cousins don’t collide.
- Optional GA4 path: mark the thank-you route as an event or key conversion in GA4, then import that conversion into Ads if you normalize reporting there first—mirror the Ads setup documented in our thank-you page conversion tracking in GA4 walkthrough.
- QA: submit production forms in an incognito window, confirm Ads Tag Assistant detects the conversion tag (or Preview mode in GA4 Debugger), verify only successful redirects increment.
Method 2: GTM Form Submission Tracking
When stakeholders refuse a splash thank-you route, AJAX-style Squarespace confirmations still expose DOM events—but you instrument them with listeners instead of another navigation.
That’s precisely what Method 2 covers: expose GTM globally (Header injection), isolate your form selectors, and latch onto successful submissions:
- Start from the step-by-step in Track form submissions as conversions without a thank you page — variable boxes, Submission trigger nuances, staging with Preview.
- Running multiple unrelated forms under one banner? Separate triggers by form ID rules so each conversion feeds the right KPI; Conversion tracking for multiple forms without thank you pages shows wiring patterns.
- Remember false positives whenever success isn’t unmistakable validation—prefer thank-you redirects when UX allows.
After GTM emits a GA4 event (or pushes to dataLayer wired to Ads), mirror that measurement into Ads via GA4 imports or Conversion Action linked to Tag Manager conversions—matching naming between platforms saves monthly audits.
Method 3: Button Click Tracking
Sometimes redirects break, AJAX listeners miss because Squarespace rewrote selectors, but you still need a proxy signal—you can intentionally log clicks against the canonical submit button. This is knowingly “softer”: partial submissions or double clicks may skew totals, and button caption edits may break selectors until you QA.
Reserve Method 3 for exit destinations you can’t wrap (booking widgets, outbound apps) following the playbook in our Track button clicks with Google Tag Manager for GA4 primer, complemented by Squarespace quirks in Squarespace GA4 button click tracking where markup limitations prohibit custom HTML attributes native Squarespace forbids.
For caveats contrasting click triggers vs true submission confirmations, skim why button-click conversions can inflate before signing off internally.
Which Method Should You Use?
| Method | Strongest when … | Signal quality | Maintenance | Gotchas |
|---|---|---|---|---|
| Thank-you URL redirect | Marketing approves routing; you manage only one choke URL per funnel. | High fidelity | Low ongoing effort | Visitors may bookmark confirmation pages—but volume is negligible. |
| GTM form submits | Modal confirmations, multi-page mini flows, SPA-like behavior preventing navigation. | Strong if validations align | Moderate—you must babysit selectors + theme updates. | Add unit tests visually after template pushes; duplication if both thank-you AND listener fire. |
| Button clicks | Third-party embeds leap off-site instantly; AJAX never bubbles success. | Approximate KPI | Medium—requires creative governance on copy changes. | Spam clicks, abandonment after click, renaming buttons—all classic drift. |
FAQ
Can Squarespace Commerce share data straight into Ads without touching GTM?
For storefront conversions the native GA4 connector often skips revenue payloads—audit Squarespace sales conversion values in GA4 rather than trusting defaults.
If I bolt GTM everywhere, could I triple-count?
Yes—duplicate tags are common when Squarespace GA4 fields stay populated while simultaneous GTM tags fire GA4 Ads conversions. Normalize to one ingestion path.
Do abandoned partial fills collide with conversions?
Audience building for abandonment (Squarespace abandon tracking) layers on top Method 2/3—you still want completed-submit conversions isolated for bidding.
Google Ads insists on Enhanced Conversions—is that compatible?
Depends on hashed first-party payloads you capture in forms plus tag configuration; TY pages usually collect email phone easier for hashing after consent versus click-only setups.
How often validate after Squarespace publishes?
Treat releases like regressions tests—submit each active form quarterly, reconcile Ads diagnostics vs CRM lead logs.