DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Squarespace

A script tag alone does not confirm that analytics works. Verify the published document, the request to DataSag and the matching visit in the correct project. This guide applies to Squarespace.

Start with the Squarespace installation

Open the site-wide Code Injection settings and paste the tracker into Header. Save the change, then open the public site outside the editor. Code injection availability depends on your plan; consult the platform documentation for your account.

A page header field or a code block may also contain the tracker. A code block only covers its page and can be removed with the content. Site-wide injection is easier to audit.

Use the public project key from the DataSag project you are inspecting. A test on a preview domain does not confirm that the production domain has the same code or settings.

Verify DataSag analytics in Squarespace

  1. Confirm your Squarespace plan supports code injection, then inspect the site-wide Header entry. Check page header fields and code blocks so the same script is not installed at more than one scope.
  2. Save and open the public site outside the editor. Inspect the outer document for the real script and public key. A code block embedded in one page is not proof of site-wide coverage.
  3. Open a normal page and a content entry directly. Inspect accepted pageview requests for both. Then follow public navigation and compare paths rather than assuming the editor view behaves like the published website.

The public Squarespace document carries a working site-wide installation across the sampled page types.

Complete the collection checks

  1. Open the published website in a normal browser window with the Network panel recording. Use a browser profile where you can control extensions and your consent choice.
  2. Filter network requests for tracker.js. Confirm it returns JavaScript successfully and that the rendered script has the project's data-datasag-key attribute. The example YOUR_PUBLIC_KEY must be replaced.
  3. Filter for /api/track and reload once. Inspect a request with eventName null or absent. Its projectKey and path should match the chosen project and the page you opened.
  4. Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
  5. Navigate to a second path, then use Back. Compare pageview requests with the route changes rather than counting every request as a pageview.
document.querySelectorAll('script[data-datasag-key]').length
// Expected: 1

document.querySelector('script[data-datasag-key]')?.getAttribute('data-datasag-key')
// Expected: your project's public key

typeof window.datasag?.track
// Expected after the script runs: 'function'

What a successful check looks like

One rendered tracker installation, a successful request for the intended page and a corresponding entry in the intended project. Scroll and engagement requests are separate event types.

Record the public path you tested, the browser state, the approximate time and the observed request. Check one direct page load and one later navigation so the result covers more than the homepage.

Common mistake

A successful tracker.js download only proves that a file loaded. It does not validate the project key, consent state or tracking endpoint. Test a real published path before declaring setup complete.

Installation snippet for Squarespace

The shared installation belongs in site-wide Header code injection. Use this as the installation reference while checking the procedure above.

<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

Related Squarespace guides

Full Squarespace setup guide · Search and AI visibility

References

Official Squarespace documentation covers the integration point. For DataSag data handling, read the privacy policy. Use support if a request fails after these checks.