Squarespace analytics

What Squarespace analytics shows

Squarespace counts visits, pageviews and unique visitors on every site it hosts and shows them in the Analytics panel, with no code from you. Its documentation states that the platform “records visitor activity via JavaScript in the browser”, and that which panels you see “depends on your setup and the billing plan you signed up on”.

Three published definitions decide how the figures read. A visit is “a single browsing session, and can encompass multiple pageviews”, tracked with a cookie that expires after 30 minutes; every session also ends at midnight, so a late evening visit that crosses that line registers again the next day. Unique visitors are “an estimate”, tracked with a cookie that lasts two years, so clearing cookies or switching browser starts the count again. Pageviews cover full page loads only: requests for image URLs, other scripts and 404 pages “aren’t included in this number”. Five analytics cookies carry all of it, among them ss_cid at two years and ss_cvisit at 30 minutes.

The panels fall into three groups. Traffic holds the visit and pageview charts with splits by device type, source, browser and operating system, next to Traffic sources, Search keywords and Geography. Engagement holds Site content, Site search keywords, RSS Subscribers, Form & button conversions, and the Activity log, “a searchable list of every time a visitor accessed a URL on your site in the past seven days” that, in Squarespace’s words, “Includes IP addresses”. Sales holds the store reports for sites with payments connected.

Your plan decides how much of that you see, and Squarespace publishes the table. Traffic, Geography, Search keywords, Activity log and Site content run on Basic through Advanced; Sales, Purchase funnel, Form & button conversions and traffic alerts start at Core; Traffic sources on Basic is marked “restricted sources and channels”. Collection continues either way: “We track data for all sites, regardless of plan”, so an upgrade reveals history rather than starting it.

Where the built-in panels stop

The first limit is scope. Nothing in the panels lets you define an event. Form & button conversions reads the platform’s own blocks, form and newsletter blocks on one side, button blocks and pop-up buttons on the other, and reports a rate calculated as “(Converted unique views ÷ unique views) x 100”. A click on a PDF link, a video played, a phone number tapped, none of those have a panel.

Export is the second, and it is absolute: “It’s not possible to export analytics data at this time.” Numbers stay where they are drawn. Freshness is the third: “Data in analytics can take up to three hours to refresh”, which rules the panels out for watching a campaign as it runs.

Time is the fourth. Reporting periods follow the site’s language and region settings, “not your visitors’ time zones”, and “Changes to language and region settings aren’t retroactive”. Set the wrong zone early and old days stay where they landed.

The Activity log is the fifth, because its detail is also its ceiling: 50 rows at a time, seven days back, one page visit per row. It is a log rather than a report, and “It’s not possible to block specific IP addresses from your site”.

The sixth is the one most owners meet by surprise: a consent banner changes Squarespace’s own numbers, and not in the direction you would expect. When visitors do not accept analytics and performance cookies, the documentation says, “Squarespace analytics may inflate visitor numbers because we can’t track those visitors’ behaviors. For example, Squarespace analytics will count one visitor who views ten pages as ten separate visitors.” Two tools on the same site will disagree, and Squarespace explains the reasons rather than denying them: different bot filters, its habit of ignoring your own visits while you are logged in, estimates from a sample on the Google side, and location read from addresses in different ways.

How to add an analytics tool to a Squarespace site

There are two doors, and they are not equal. The first is the built-in field for Google Analytics: Developer tools, then External API keys, then the Google Analytics account number, where a measurement ID beginning with G- goes. Squarespace calls it a built-in integration and states that “If you use this option, you don’t need to add separate script code”. The same note draws the boundary around it: “Other code-based solutions, like Google Tag Manager, fall outside the scope of our support.”

The second door is the Code Injection panel, and it is how every other tool arrives. Code placed in the Header field is injected into the head of every page in the site, as the documentation puts it; the Footer field lands before the closing body tag. This is the route the vendors document, among them Plausible, Fathom, Simple Analytics and Matomo. Page settings carry their own injection fields, and blog pages add one that runs on every post.

The plan gate sits on this second door only. “Code injection is available in the Core, Plus, Advanced, and some legacy billing plans”, and it is listed among the premium features that “aren’t available on the Basic plan”. On a site that drops to Basic the panel turns into a display case: the code “stays in the Code injection panel for your reference, but it won’t affect your site and it’s not possible to edit it”. Script in a code block behaves the same way. A Basic site can run Google’s tag and nothing else.

Checkout is closed to everyone: “Checkout pages don’t support code.” What you get instead are separate injection fields for the order confirmation and order status pages, plus tags that fill in order details, among them {orderId}, {orderGrandTotal} and {customerEmailAddress}. Because a customer can reopen the order status page, Squarespace documents a guard: an if-first-page-view tag around the tracking code and an end tag after it, so a purchase is recorded once.

Version 7.0 sites carry two more traps that Squarespace names: injected code “won’t appear on Index landing pages”, and where a template uses Ajax loading, “Ajax interferes with site analytics, only logging the first page a visitor lands on”.

Consent works through the cookie banner setting, where the opt in and out style gives visitors an accept and a decline button and injected code can read the choice before it runs. What applies to your site depends on where your visitors are, on what else your pages load and on how the tool is set up, and this page is not legal advice; vendors who state that their tool stores nothing in the browser are listed on the cookieless tools page.

Of the 44 tools in the table, 18 publish a Squarespace route of their own, meaning an installation guide written for the platform; 4 more name it without publishing one and point at the general snippet. Google Analytics 4 is the outlier, since Squarespace hosts a field for it. The full set, with the date each value was checked, is in the table.

What to count on a Squarespace site

Pageviews arrive with the snippet, so the work is the handful of actions the panels cannot name.

Form submissions come first, and there are two routes. Edit Post-Submit on a form block offers Redirect, which sends visitors to a page you create in the Not linked section and turns a submission into a pageview any tool can count; the same screen offers a post-submit message that can carry HTML, which suits tools that fire an event instead. One line in the documentation saves an afternoon: “Post-submit redirects won’t work while logged into your site”, so test in a private window.

Button and link clicks come second. Squarespace counts clicks on its own button blocks from Core upwards; outbound links, file downloads and mail or phone links are yours to send.

Stores add the purchase. The order confirmation and order status fields are the only place an outside tool learns that money changed hands, and the order tags the only place it learns how much. Send the grand total if you want revenue in reports, keep the guard so a reload does not count twice, and settle on one currency first.

Two habits keep the numbers usable: name events once and keep the names, since a rename splits one metric in two, and check the injected code after any template or plan change.

Questions and answers

Does Squarespace have analytics of its own?

Yes, on every plan, though not the same amount on each. Visits, pageviews, unique visitors, geography, search keywords and the Activity log come with the site and need no code; sales reporting, the purchase funnel and the form and button conversion rate start at Core. Data is collected for every site regardless of plan, so upgrading reveals history rather than starting it.

Do I need a paid plan to add an analytics tool to Squarespace?

For anything other than Google Analytics, yes. The measurement ID field under Developer tools and External API keys needs no code. Every other tool goes through code injection, which Squarespace lists as available on “the Core, Plus, Advanced, and some legacy billing plans” and excludes from Basic, where saved code stays visible but stops working and cannot be edited.

Why do Squarespace and an outside tool disagree about visitors?

Because each counts by its own rules, and Squarespace publishes its own. Its visit ends after 30 minutes of inactivity and again at midnight, while another tool sets its own window and day boundary; it ignores your visits while you are logged in and the other does not; bot filters differ; and when visitors decline analytics cookies Squarespace says its own visitor count inflates. Decide which of the two answers which question, and stop comparing the totals.

Can an analytics tool track the Squarespace checkout?

Not the checkout pages themselves: “Checkout pages don’t support code”, so a snippet in the Header field never loads there. The supported route is the injection field for the order confirmation and order status pages, where tags such as {orderId} and {orderGrandTotal} pass the details through, wrapped in the first-page-view guard so a customer who reopens the page is not counted twice.

Do I need a consent banner on a Squarespace site?

That depends on where your visitors are, what your pages load and how your tools are configured, and it is not a question this directory answers for you. Squarespace provides the mechanics: a banner with accept and decline buttons, a setting that restricts non-essential cookies, and a way for injected code to read the choice. Some vendors state that a banner is not needed for their tool; that is the vendor’s position, and the privacy-friendly tools page sets out the conditions each applies. A site usually loads more than analytics, and the answer covers all of it.