Your Facebook Pixel is not working on Squarespace because you pasted the full script tag into the header, your cookie banner is blocking the tracker, or your domain is unverified. Squarespace has a native integration that breaks if you try to install the code manually. You need to strip out the custom code and use the built-in field.
Why is my facebook pixel not working on squarespace?
Squarespace is a closed ecosystem. The platform controls the checkout process and the page routing to keep the software stable. When you try to force raw JavaScript into the header, it clashes with the platform architecture. Your Facebook Pixel is not working on Squarespace because the platform requires a highly specific setup method. You cannot follow the generic instructions provided by Meta. Meta tells you to copy a block of code and paste it between the head tags of your website. If you do this on Squarespace, the tracking fails. You must use the native tools provided by the platform.
Check if your Meta Pixel is loading at all
Before you change any settings, you must verify the current state of your tracking. Run your website address through a free pixel checker to see exactly which standard events fire when a page loads. This tells you if the script is present on the page. You can also use the Meta Ads Data Advisor extension for Chrome. Install the extension, open your website, and click the icon in your browser toolbar. If the extension shows no pixels found, the code is missing or blocked by a consent banner. If the extension shows a red error icon, the code is present but broken. You need this baseline information to know which fix to apply.
You pasted the full script instead of the Pixel ID
This is the most common reason your Facebook Pixel is not working on Squarespace. You followed the default Meta setup wizard. The wizard gave you a large block of JavaScript. You opened your Squarespace dashboard, navigated to Settings, clicked Developer Tools, opened Code Injection, and pasted the script into the Header section. This breaks your tracking.
Squarespace has a built-in integration for Meta. If you use the raw script, you cause duplicate event triggers. The raw script also cannot track purchases because Squarespace restricts custom code on the checkout page for security reasons. The raw script simply stops working the moment your customer tries to pay.
To fix this, you must remove the raw code. Go to Settings, click Developer Tools, and open Code Injection. Delete the entire Meta Pixel script from the Header box. Save your changes.
Next, you need to use the correct method. According to the official Meta documentation, you must only use your numeric Pixel ID. Open the Meta Pixel and Ads panel in your Squarespace Marketing settings. Paste your Pixel ID into the designated field. Click Save. This native integration automatically adds the base code to every page, including the secure checkout.
Your Squarespace cookie banner is blocking the tracker
Privacy laws require websites to ask for user consent before loading tracking scripts. Squarespace includes a built-in cookie banner to handle this requirement. If you configure this banner to require an explicit opt-in, Squarespace blocks all non-essential scripts until the visitor clicks the accept button.
The Meta Pixel is categorised as a non-essential marketing script. When you test your own website, you likely ignore the cookie banner because you are focused on the tracking setup. If you do not click accept, the pixel script never loads. The Meta Events Manager will show zero activity.
To confirm this is the issue, open a new incognito window in Chrome. Navigate to your website. The cookie banner will appear. Click the accept button. Click through a few pages and add a product to your cart. Return to your Meta Events Manager. If the events now appear, your tracking is working perfectly. The cookie banner is simply doing its job.
You have ad blockers running in your own browser
Your tracking setup might be flawless, but your testing environment is broken. As a business owner, you likely use tools to block advertisements and protect your privacy online. Chrome extensions like UBlock Origin and Ghostery block Meta tracking scripts at the network level. The Brave browser blocks these scripts by default using built-in shields.
If you have an ad blocker active while you test your website, the script never executes. The data never leaves your computer. Meta Events Manager stays completely blank.
Do not change your Squarespace settings until you rule this out. Turn off all ad blockers in your browser. Disable the Brave shields. The best approach is to create a dedicated Chrome profile with zero extensions installed. Use this clean profile exclusively for testing your tracking setups.
Your domain is not verified in Meta Business Manager
Apple iOS privacy updates forced Meta to change how they process web conversion events. Adding the Pixel ID to your Squarespace dashboard is no longer sufficient. You must prove to Meta that you actually own the domain sending the data. If your domain is unverified, Meta restricts your event data and your ad campaigns will underperform.
You verify your domain by adding a specific record to your domain name system settings. Here are the exact steps to complete this process:
- Log into Meta Business Manager and open the Business Settings.
- Navigate to the Brand Safety menu and select Domains.
- Click the Add button and type your exact Squarespace domain name.
- Select the DNS TXT record verification option from the dropdown menu.
- Copy the unique string of text provided by Meta.
- Open your Squarespace dashboard and navigate to Settings.
- Click Domains, select your primary domain, and open the DNS Settings.
- Add a new record, select TXT as the record type, and paste the unique string into the value field.
- Save the DNS record in Squarespace.
- Wait ten minutes for the DNS changes to propagate across the internet, then click the verify button in Meta Business Manager.
You are testing too soon after setup
Tracking data is not strictly real-time. When you connect your Meta Pixel to Squarespace, the system requires time to initialise. If you paste your Pixel ID and immediately check Meta Events Manager, the dashboard will likely be empty.
You must use the Test Events tool correctly. Open Meta Events Manager, select your data source, and click the Test Events tab. Enter your website URL and click the Open Website button. Perform specific actions on your site. View a product page, add an item to your cart, and initiate the checkout process.
Wait at least twenty minutes before you conclude that the setup has failed. Sometimes the data pipeline experiences delays. If the dashboard remains empty after an hour, you need to troubleshoot your test events to identify the exact point of failure.
Your Advantage+ catalog events lack product parameters
If you run Advantage+ catalog ads, your tracking requirements are much stricter. A standard page view is not enough. Meta needs to know exactly which product the user viewed so it can show that exact product in a dynamic advertisement.
To do this, the Meta Pixel must send specific product parameters alongside the standard event. The events must include the content_ids or contents parameters. These parameters contain the unique stock keeping unit for the product.
If your Facebook Pixel is not working on Squarespace for dynamic ads, the product IDs in your Squarespace store likely do not match the product IDs in your Meta catalog. The native integration sends the data, but Meta cannot map the website event to the catalog item. You must open your Catalog Manager in Meta and verify that the product IDs perfectly match the SKUs in your Squarespace inventory.
Move your tracking to the server
Browser tracking is becoming less reliable every month. Safari blocks third-party cookies by default. iOS restricts app tracking. Ad blockers prevent scripts from firing. The Meta Pixel relies entirely on the visitor browser to send data. When the browser blocks the script, you lose the conversion data.
The permanent solution is to move your tracking away from the browser. Upgrading to server side tracking sends your conversion data directly from your server to the Meta Conversions API. This bypasses the browser entirely. Ad blockers cannot stop server requests. Your data accuracy increases, which gives the Meta algorithm more signals to optimise your ad campaigns.
Setting up a server container requires technical infrastructure. If you need an expert to build this system for your business, reach out to us to map out the exact architecture you need.