Why can't I just do this myself?

You can — if you have 80–120 hours to learn server-side GTM, debug iOS dedup edge cases, and stress-test EMQ across every conversion event. We do it in 7–10 days because we've done it 300+ times.

What if it doesn't work?

Two protections: (1) 95% tracking accuracy guarantee — we keep working free until your Meta Match Quality hits 8+. (2) You own the entire stack — server, container, runbook — on your accounts from day one.

Will Apple / Google break this in the future?

1st-party server-side tracking is what survives Apple, Mozilla, and Chrome cookie deprecation. The CAPI / Events API endpoints we use are how Meta, Google, and TikTok publicly committed to keeping the channel open.

SquarespaceFor Squarespace Commerce

Get your Squarespace tracking to 95%+ accuracy guaranteed in writing.

Squarespace's native integrations are minimal: no line items, no customer data, no dedup. iOS users disappear. GA4 shows you traffic but no commerce. You're flying blind on every campaign. We add a real server-side CAPI gateway driven by Squarespace order webhooks so the data finally flows.

Get my free conversion tracking audit See what we check

Free30 minutesNo obligation

By Ariful IslamHow Squarespace works ↓

Squarespace · what breaks

What's missing on Squarespace

01
Pixel events lack rich data
Email, phone, value detail all minimal in default integrations.
02
Order webhook reliability
Squarespace order webhooks can fire twice or get retried.
03
GA4 sees only page_view
Without effort, GA4 has zero e-commerce data.

Squarespace · the fix

What we deliver — Squarespace

Server-side CAPI from order webhook
Idempotent, dedup-safe purchase events.
GA4 e-commerce schema
view_item, add_to_cart, purchase with line items.
Enhanced Conversions
Hashed customer data to Google Ads.

Squarespace · architecture

How a Squarespace order should reach the ad platforms

Squarespace gives you code injection but not checkout access, so the shape of a reliable build is decided by that one constraint.

1
Click identifiers captured at first touch
Click IDs are captured in site-wide code injection at landing and written to a first-party cookie, because Squarespace's checkout does not preserve query parameters through to the order confirmation.
2
The browser sends the fast, fragile copy
Code injection fires the browsing and cart events. Squarespace's checkout is hosted and its order confirmation page is the only browser-side purchase hook available.
3
The order itself is the source of truth
The Squarespace order, retrieved via the Orders API or delivered by an order webhook, is the truth. The confirmation page can be refreshed and is not always reached after an external payment redirect.
4
A server container sends the authoritative event
An order webhook posts to a GTM server container on your own subdomain, keyed on the Squarespace order ID.
5
Customer identity raises match quality
The order carries customer email and billing address. Hashed server-side, these are the only route to decent match quality on a platform with no checkout script access.

Squarespace · events

The event set we build on Squarespace, and where each one comes from

Squarespace's constraint is the same one Wix has: everything that matters happens where you cannot put a script, so the webhook carries the load.

Event	Fires when, on Squarespace	Key parameters	Sent from
view_item	A product page renders	item_id, value, currency, event_id	Browser + server, deduped
add_to_cart	The cart update completes	item_id, quantity, value, currency, event_id	Browser + server, deduped
begin_checkout	The hosted checkout is entered	value, currency, num_items, event_id	Browser + server, deduped
purchase	The order webhook fires against a paid order	order_id, value, currency, items[], hashed email/phone/name/address, event_id	Server authoritative
generate_lead	A Squarespace form submits successfully	hashed email/phone, click IDs, event_id	Server preferred

Squarespace · normal or broken

Squarespace boundaries versus actual breakage

Squarespace's restrictions are consistent and documented; most apparent faults are simply those restrictions.

Normal, not a fault

Code injection not running in checkout
Squarespace excludes checkout from site-wide injection. Expected, and the reason server-side matters here.
Squarespace Analytics disagreeing with GA4
Different models, different questions.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.

Actually broken

Purchase tracked only from the order confirmation page
Orders where the customer closes the tab after paying are never counted.
The confirmation page firing again on refresh
Without an order guard, one order becomes several conversions.
Squarespace's built-in pixel fields filled in alongside a code-injected pixel
Two paths, doubled conversions, and the built-in field is easy to overlook.

Squarespace · prove

How we prove the Squarespace build is correct

The tag firing proves the tag fires. These prove the numbers are right.

Source of truth

Squarespace Commerce order records

The order webhook confirmed delivering for a real paid order.
Built-in pixel fields audited and reconciled against injected code so exactly one path remains.
Confirmation page refresh confirmed to produce no second conversion.
Purchase count within a few percent of squarespace commerce order records for a fully closed week, matched on order ID rather than on totals.
No order ID appearing twice in any platform's event log.
Deduplication confirmed at every destination that supports it.
Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.

Squarespace · free audit

What we check in the free audit

Pixel events lack rich data
Order webhook reliability
GA4 sees only page_view

Checked against

Squarespace Commerce order records

Get my free conversion tracking audit

Free30 minutesNo obligation

Squarespace · when not to buy

When a Squarespace rebuild is not what you need

We would rather say this now than three weeks into an engagement.

Your Squarespace site is a portfolio or brochure with no commerce. Standard tags are sufficient.
You spend under about $1,500 a month on ads.
You are replatforming to a store-first platform this quarter.

Squarespace · what we deliver

Deliverables — Squarespace

Webhook gateway
1st-party server-side GTM on your subdomain
Code injection module
Header & footer scripts
Meta CAPI + EC + GA4
All wired and tested
QA + handover
Notion runbook

Written guarantee

95%+ tracking accuracy

Measured against Squarespace Commerce order records. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Foundation pixel install for your Squarespace store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.

One-time fee · zero monthly · zero SaaS lock-in
Squarespace dataLayer (clean spec)
GA4 e-commerce events
Meta Pixel · Google Ads tag
TikTok Pixel · Microsoft UET
Consent Mode v2 banner integration
QA test orders + 7-day support
No CAPI · no iOS recovery

Lock in the one-time price

1st-party server-side

Recommended

$800One-time fee · most popular

The done-for-you package every Squarespace store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.

One-time fee · save vs SaaS subscriptions over 5 years
Fully recovered + built in 2–4 days · accurate data in 7 days
Everything in browser-side starter
1st-party server-side GTM (your subdomain)
Meta CAPI · full advanced matching · 8+ EMQ
Google Enhanced Conversions (Web + Leads)
TikTok Events API · Microsoft UET server
Deterministic browser ↔ server deduplication
Live EMQ verification + screenshots
Notion runbook + 30-day support · zero recurring

Lock in the one-time price

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel running 1st-party server-side, end-to-end. For Squarespace brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.

One-time fee · save 6-figure SaaS subscriptions over 5 years
Everything in 1st-party server-side tier
Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
Klaviyo identity stitching (if used)
BigQuery export (server logs + GA4)
Looker Studio attribution dashboard (branded)
Multi-region / multi-currency / EU residency
GDPR-audit-ready Consent Mode v2 wiring
60-day support · optional retainer · no lock-in

Lock in the one-time price

FAQ

Squarespace questions, answered

Commerce Basic or higher (for order webhooks).

Free · 30 min

Free Squarespace audit

Book a free audit

Free30 minutesNo obligation

Get your Squarespace tracking to 95%+ accuracy guaranteed in writing.

What's missing on Squarespace

Pixel events lack rich data

Order webhook reliability

GA4 sees only page_view

What we deliver — Squarespace

Server-side CAPI from order webhook

GA4 e-commerce schema

Enhanced Conversions

How a Squarespace order should reach the ad platforms

Click identifiers captured at first touch

The browser sends the fast, fragile copy

The order itself is the source of truth

A server container sends the authoritative event

Customer identity raises match quality

The event set we build on Squarespace, and where each one comes from

Squarespace boundaries versus actual breakage

How we prove the Squarespace build is correct

What we check in the free audit

When a Squarespace rebuild is not what you need

Deliverables — Squarespace

Webhook gateway

Code injection module

Meta CAPI + EC + GA4

QA + handover

Pick the package that fits your ad spend

Browser-side starter

1st-party server-side

Full 1st-party stack

Squarespace questions, answered

Squarespace plan needed?−

More on Squarespace

Free Squarespace audit