Google Ads and GA4 tracking for Squarespace
The Google problem on Squarespace is the same as on every AJAX-form platform: a conversion bound to a thank-you page that never loads. For commerce, the order confirmation is more reliable but still a page a customer can refresh.
Free30 minutesNo obligation
Squarespace + Google · what breaks
What goes wrong on Squarespace
- 01
Code injection needs a paid plan
On lower plans you cannot add a container at all, which decides the whole approach.
- 02
Forms submit without reliable navigation
So URL-based conversion triggers don't fire.
- 03
Commerce checkout is Squarespace's flow
Limited access to what happens inside it.
- 04
Built-in pixel field plus injected pixel
The standard duplication pattern here.
Squarespace + Google · the fix
What changes — Squarespace + Google
Conversions bound to real events
Form success state or order confirmation.
One pixel path
Built-in field or injection, not both.
Counts reconciled
Against Squarespace's own records.
Squarespace + Google · architecture
How the Google destinations behave on Squarespace
Same AJAX-form story, plus a refreshable order confirmation.
- 1
Conversion bound to the form's success state
Not a URL change.
- 2
Order confirmation guarded against refresh
Or sourced from a webhook where possible.
- 3
Counting per conversion type
One for forms, every for commerce.
- 4
Click IDs captured in injected code
All four, into form fields.
- 5
One source per conversion action
Built-in field and container both sending is a double-feed.
Squarespace + Google · diagnose
Where Squarespace tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Confirm the plan allows code injection
On lower plans this changes everything.
- 02
Submit a form and watch the URL
It usually doesn't change.
- 03
Check the built-in pixel fields and injection
For the same pixel twice.
- 04
Refresh an order confirmation
Watch whether anything fires again.
- 05
Reconcile against Squarespace records
For a closed month.
Squarespace + Google · prove
The QA evidence — Squarespace + Google
Run on Squarespace specifically, on a live conversion rather than in preview mode.
Source of truth
your Squarespace order or form records
- Conversion confirmed firing on a real submission or order.
- Only one pixel path active across built-in fields and injection.
- Order confirmation refreshed with no additional event.
- Click identifiers confirmed present in the submitted data.
- Counts reconciled against Squarespace's own records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Squarespace + Google · free audit
What we check in the free audit
- Confirm the plan allows code injection
- Submit a form and watch the URL
- Check the built-in pixel fields and injection
- Refresh an order confirmation
- Reconcile against Squarespace records
Checked against
your Squarespace order or form records
Free30 minutesNo obligation
Squarespace + Google · when not to buy
When you don't need this on Squarespace
Worth reading before you buy anything, from us or anyone.
- If you're on a plan without code injection, most of this isn't available to you and the built-in fields are your setup. That's a real constraint, not a sales objection.
- For a small Squarespace site with one destination, the built-in pixel fields are free and adequate.
- Squarespace is one of the weaker platforms for server-side. If someone is selling you a container here, ask what specifically it fixes on this platform.
- Reconcile a closed month against your Squarespace records before buying anything.
Squarespace + Google · what we deliver
What gets built for Google on Squarespace
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
Written guarantee
95%+ tracking accuracy
Measured against your Squarespace order or form records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Squarespace + Google questions, answered
Usually a form conversion that never fires, or an order confirmation being refreshed and counted twice.
One for lead forms, every for commerce orders.
They can, and it double-feeds. Pick one source per conversion action.
Injected code on landing, writing into form fields. Squarespace does nothing here automatically.
Free · 30 min
Get Google Ads and GA4 right on Squarespace
Free30 minutesNo obligation
