Meta Conversions API setup for Squarespace
Squarespace's built-in Meta pixel field plus a pixel in code injection is the standard duplication here. Two fields, two pixels, one conversion counted twice.
Free30 minutesNo obligation
Squarespace + Meta CAPI · 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 + Meta CAPI · the fix
What changes — Squarespace + Meta CAPI
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 + Meta CAPI · architecture
How Meta tracking behaves on Squarespace
Two fields, one pixel — pick which.
- 1
Audit the built-in field and code injection
The two places a pixel lives.
- 2
Conversion events bound to real states
Not page views.
- 3
Order or form ID as event_id
Where a server event is also sent.
- 4
fbclid captured on landing
Into a form field.
- 5
Customer data normalized before hashing
From the Squarespace record.
Squarespace + Meta CAPI · 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 + Meta CAPI · prove
The QA evidence — Squarespace + Meta CAPI
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 + Meta CAPI · 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 + Meta CAPI · 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 + Meta CAPI · what we deliver
What gets built for Meta on Squarespace
A shared event ID on both paths
The Squarespace order or form submission ID, from Squarespace's own record.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
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 + Meta CAPI questions, answered
It's in the built-in marketing field and in code injection. Two places, both active.
Bind it to the form's success state rather than to a navigation.
Capture fbclid on landing in injected code and write it into a form field.
Only if you're losing events, and the server-side route is more constrained on Squarespace than elsewhere. Fix the browser event first.
Free · 30 min
Get Pixel and CAPI counting once on Squarespace
WhatsAppFree30 minutesNo obligation
