Loading tutorials…
Loading tutorials…
Squarespace has a 'Meta Pixel ID' field that fires base pageviews. The problem: it doesn't fire Purchase events, doesn't support Conversions API, and silently loses 30-50% of iOS attribution. Here's the real install.
Who this is forSquarespace site owners running Meta Ads (Facebook + Instagram) who need accurate conversion tracking. Especially urgent if your ROAS is dropping and you suspect attribution loss.
What you'll need
Step 1
Meta Business Manager → Events Manager → Data Sources. Create a new pixel or use an existing one for this domain.
Go to business.facebook.com → Events Manager → Data Sources.
If you don't have a pixel: click 'Connect Data Sources' → Web → Meta Pixel → name it (your brand name) → enter your Squarespace domain.
Copy the Pixel ID (15-16 digit number). You'll need this.
In Pixel settings → Activity: confirm events ('Last received: never' is normal for a brand-new pixel).
Important: one pixel per domain. Don't share a pixel across multiple unrelated sites — Meta's audience modeling gets confused.
Step 2
Marketing → Pixels & Ads → Meta Pixel → paste the Pixel ID. Easy path; fires PageView only.
Squarespace Admin → Marketing → Pixels & Ads.
Find the 'Meta Pixel' (formerly 'Facebook Pixel') section. Paste your Pixel ID. Save.
Visit your live site in incognito. Click around 4-5 pages.
Meta Events Manager → your pixel → Test events → enter your live URL → wait 60 seconds. Should see PageView events firing.
If you see PageView in Test Events: native install is working for basic pageviews. Move to Step 3 to add ecommerce events.
Note: this is the bare minimum. Custom events (ViewContent, AddToCart, Purchase) do NOT fire from the native install.
Step 3
For real conversion tracking, use GTM. Install the Pixel via GTM with triggers for Purchase, AddToCart, ViewContent.
If you don't have GTM installed on Squarespace yet, install it first (see the GA4 tutorial — same process).
REMOVE the Meta Pixel ID from Marketing → Pixels & Ads → Meta Pixel to avoid duplicate PageView firing.
In GTM: add a new tag → 'Facebook Pixel' (use the official Meta tag template from GTM's Community Gallery) OR Custom HTML with the Meta base code.
Set tag fires on All Pages. Save and publish.
Add an AddToCart tag: Custom HTML with `fbq('track', 'AddToCart', { value: X, currency: 'USD' });`. Trigger on click of Squarespace's add-to-cart button (CSS selector: usually `.sqs-add-to-cart-button-inner` or similar — inspect your site to confirm).
Add a Purchase tag: Custom HTML with `fbq('track', 'Purchase', { value: X, currency: 'USD' });`. Trigger on Page View → Page Path contains '/checkout/thank-you'.
Parse the order value dynamically from the page DOM for accurate value reporting — hardcoded values break value-based bidding.
Step 4
Browser pixels lose 30-50% of conversions to ITP and ad blockers. CAPI sends events server-side. Non-negotiable for any real Meta Ads budget.
Meta Events Manager → your pixel → Settings → Conversions API.
Squarespace does NOT have native CAPI integration. Three workarounds: (1) Zapier (Squarespace order webhook → Zap → Meta CAPI), (2) Pabbly Connect (same pattern, cheaper), (3) a paid Squarespace-to-CAPI connector.
Workflow: Squarespace fires a webhook on order placed → connector receives it → connector calls Meta CAPI Purchase event with hashed customer email + value + currency + event_id.
Critical: include `event_id` matching the browser-side event_id. Meta deduplicates browser + server events using event_id. Without it, every conversion is counted twice.
Validate: Meta Events Manager → Test events → after a real test purchase, both Browser and Server columns should show Purchase.
If only Browser shows: CAPI not connected. If only Server shows: browser pixel not firing on /thank-you. Both needed for full attribution.
Step 5
iOS 14.5+ requires you to configure which 8 events Meta can optimize for, ranked by priority. Set this in Events Manager.
Meta Events Manager → Aggregated Event Measurement → 'Configure Web Events.'
Add your domain. Pick the 8 events you care about most, ranked by priority (1 = highest).
Typical priority for ecommerce: 1. Purchase, 2. InitiateCheckout, 3. AddToCart, 4. ViewContent, 5. AddPaymentInfo, 6. Search, 7. Lead, 8. ViewContent (subcategory).
For lead-gen: 1. Lead, 2. CompleteRegistration, 3. SubmitApplication, 4. Contact, 5. Schedule, 6. ViewContent, 7. PageView, 8. (custom).
Domain verification: required before ranking events. Meta gives you a TXT or meta-tag verification. Add it via Squarespace Settings → Advanced → Code Injection → Header (for meta tag) or via your DNS provider (TXT).
Without verification + ranked events, iOS 14.5+ users contribute zero conversion data to your bidding.
Step 6
Run a real test purchase. Verify PageView + ViewContent + AddToCart + InitiateCheckout + Purchase all fire, browser AND server.
Install the Meta Pixel Helper Chrome extension. Open your site, click 4-5 pages.
Meta Pixel Helper should show: PageView on every page, ViewContent on product pages, AddToCart on cart-add click, InitiateCheckout on checkout entry.
Add a low-price product to cart, proceed to checkout, complete with a real card (refund yourself).
On the Thank You page: Pixel Helper should show Purchase with the correct value and currency.
Meta Events Manager → Test events: see all 5 events with browser + server source.
Wait 24h. Check Events Manager → Overview → events show up with normal frequency. If Purchase is firing way more than orders placed, you have duplicate events (likely event_id mismatch in CAPI).
Step 7
Pixels break silently. Set a weekly review: check Diagnostics, monitor event volume, validate after every Squarespace update.
Meta Events Manager → Diagnostics. Check for errors: missing parameters, invalid event names, low event match quality.
Event match quality should be 'Good' or 'Great' (>6.5/10) for Purchase events. Lower means CAPI is missing customer info (email, phone) — improve by passing hashed customer data.
Event volume: track weekly. A sudden 30%+ drop usually means: ad blocker change, browser update (Safari ITP), CAPI integration broken, or pixel removed by accident.
After every Squarespace theme/template change, re-test in Pixel Helper. Theme changes can break custom CSS selectors used by GTM triggers.
Common mistakes
Using only the native Squarespace Meta Pixel field
What goes wrong: PageView fires but Purchase, AddToCart, ViewContent don't. Meta has no conversion data. Bid strategies optimize for clicks instead of conversions. CPA is 2-3x higher than it should be.
How to avoid: Use GTM with custom event triggers for Purchase, AddToCart, ViewContent. Remove the native field to avoid duplicate PageView.
Skipping Conversions API (CAPI)
What goes wrong: iOS 14.5+, Safari ITP, and ad blockers strip 30-50% of browser pixel conversions. Without CAPI, those conversions are invisible to Meta. CPA inflates over 30-60 days as the bid strategy optimizes against bad data.
How to avoid: Use Zapier, Pabbly, or a connector to send Purchase events server-side to CAPI. Include event_id matching the browser event for deduplication.
Duplicate browser + server events without event_id
What goes wrong: CAPI sends Purchase server-side, browser pixel sends Purchase too. Both lack matching event_id. Meta can't deduplicate. Every purchase is counted twice. ROAS reports look 2x better than reality. Bid targets are set wrong.
How to avoid: Generate a unique event_id per order (use Squarespace order ID). Include it in BOTH the browser pixel fire and the CAPI call. Meta deduplicates automatically.
Not configuring Aggregated Event Measurement
What goes wrong: iOS 14.5+ users contribute zero data to your bidding. If 50-60% of your traffic is iOS (typical for premium DTC), you've lost half your optimization signal. Bid strategies underperform.
How to avoid: Events Manager → Aggregated Event Measurement → configure 8 ranked events. Verify domain via TXT or meta tag. Repeat per pixel.
Hardcoded order value in Purchase event
What goes wrong: Every Purchase event reports the same value (often $0 or $1) instead of the actual order total. Value-based bidding (Target ROAS) has nothing to optimize against. Smart Bidding underperforms vs Maximize Conversions.
How to avoid: Parse the order total from Squarespace's confirmation page DOM in your GTM trigger. Use Custom JavaScript variable to extract `document.querySelector(".total-amount").innerText` (selector varies by template).
Pixel breaks after Squarespace template update
What goes wrong: You updated the template, the CSS selectors GTM uses for AddToCart and Purchase triggers no longer exist. Events stop firing. Discovered 30-60 days later when ad spend reports go sideways.
How to avoid: After every Squarespace theme/template change, run a Pixel Helper test on key flows (add to cart, checkout, purchase). Update GTM selectors if needed.
Recap
Done — what's next
How to install Google Analytics 4 (GA4) on Squarespace
Read the next tutorial
Hand it off
Meta Pixel + CAPI on Squarespace is the single most-broken setup we see when auditing accounts. Most owners install the native pixel, ship paid ads, then watch ROAS drop over months without knowing why. A vetted Squarespace + Meta specialist at $14-16/hr can install the full stack (Pixel + GTM events + CAPI + AEM) in 2-4 hours, typically $80-200 total.
See specialist rates
No. Squarespace's Meta Pixel field handles browser-side PageView only. For Conversions API (server-side), you need a connector: Zapier, Pabbly Connect, or a paid Squarespace-to-CAPI app. Plan for $20-50/mo in connector cost.
Technically yes, practically no. Without CAPI, iOS 14.5+ users (50%+ of premium DTC traffic) contribute almost no conversion data. CPA inflates 30-60% over time. Most Meta optimization budget is wasted. Set up CAPI before scaling paid spend.
Aim for 7.0+ out of 10 on Purchase events. Achieved by passing hashed customer info via CAPI: email, phone, name, address. Native Squarespace pixel doesn't pass any of this — CAPI integration is required for high match quality.
Roughly 50 Purchase events per ad set per week minimum. New ad sets need 30+ conversions before Meta exits 'Learning' phase. Until then, performance is unstable. Don't change bids/budgets daily during Learning.
Meta Pixel covers Facebook + Instagram. Same pixel, same events, same dashboards in Events Manager. You don't need a separate 'Instagram Pixel.'
Squarespace
Squarespace has a 'Google Analytics' field that accepts a Measurement ID. The problem: it doesn't fire enhanced ecommerce or custom events by default. Here's the install that actually gives you usable data.
Squarespace
Squarespace Commerce makes setting up a basic store look easy. The reality: shipping zones, tax compliance, payment methods, abandoned cart, and inventory rules need deliberate configuration or you'll lose 20-40% of CR to friction.
Squarespace
Squarespace's SEO defaults are 'fine' — which means mediocre. Sites built on Squarespace can rank, but only if you actively configure 15-20 things the platform doesn't do for you. Here's the real checklist.
Meta Ads
The browser pixel alone loses 20-30% of conversions on iOS. CAPI sends events from your server to Meta, recovering most of it. Three install paths: Shopify-native, server-side GTM, and direct API. We cover all three.
Wix
Wix has a 'Facebook Pixel' field in Marketing Integrations that fires PageView. It doesn't fire Purchase, doesn't support Conversions API, and silently loses 30-50% of iOS attribution. Here's the real install.