Squarespace
Check your Squarespace site's Meta tracking
Paste your Squarespace URL to see the Pixel and helpers in your public HTML. Squarespace allows header code injection on Business plans and above, but checkout can run on Squarespace's own domain where injected code does not follow — the classic reason Purchase events go missing.
Real browser. Pro and Team from a workspace. Static scan stays free, no login.
Header injection stops at checkout
Code Injection covers your site's pages. On plans where checkout is hosted on a Squarespace domain, your injected Pixel never sees the order confirmation — the scan can look green while Purchase is dark.
The native Meta Pixel field is PageView-deep
Squarespace's built-in Pixel setting fires basic events but gives you no control over Purchase parameters, event_id deduplication, or server-side delivery.
Send the money event from a server
Caply sends Purchase from managed servers using order data, hashed before Meta sees it. The browser snippet covers what it can; the server covers what Squarespace's checkout hides.
Squarespace tracking questions
- Why is my Squarespace Purchase event missing in Events Manager?
- Most often the checkout ran on a Squarespace-hosted domain where header code injection does not execute. The Pixel fires on the storefront, but the conversion page never loads your code.
- Do I need a Squarespace plugin for CAPI?
- Squarespace has no plugin system for server-side tracking. You need an external sender — a tagging server you host, or a managed service like Caply.
- Which Squarespace plan do I need for tracking code?
- Code Injection requires Business plan or higher. Commerce plans include it.
After the scan
Send Squarespace sales from the server. Count each one once.
Caply sends Purchase and Lead from managed servers with hashed customer data, deduplicated against your Pixel by event_id. Pro $29 or Team $99, 14-day trial (card required).
Other platforms: Shopify · WooCommerce · Wix · Webflow · Framer · Next.js · Full scanner