DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Squarespace

Find the first missing step in the delivery chain: published HTML, executing tracker, tracking request, successful response and project report. Changing several settings at once makes the failure harder to identify. 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.

Fix DataSag analytics not working in Squarespace

  1. Check plan availability before looking for a missing Code Injection setting. If the plan restricts custom JavaScript, copying the script into an unrelated content block is not an equivalent site-wide installation.
  2. Inspect the saved Header entry and the affected public page outside the editor. Compare any page-specific header code or code block with a working page to identify scope or document differences.
  3. If the external script appears correctly, inspect execution and endpoint errors and verify the public project key. Record the template and published URL before changing template settings or duplicating the snippet.

The investigation separates account capability, injection scope, public document output, and tracking delivery.

Complete the collection checks

  1. Confirm the change reached the public domain. Inspect the live HTML and clear only caches that serve the old document. A saved editor change may still need publishing.
  2. Check that tracker.js exists in the Network panel and that the script contains the public key from the same DataSag project you are viewing.
  3. Check whether your test browser is excluded with datasag_ignore. Restore inclusion with ?datasag_ignore=false only if this browser should count. Respect any consent controls configured on your site.
  4. Inspect the browser Console for Content Security Policy or script errors. Check /api/track request responses: 400 indicates invalid input, 404 can indicate an unknown project key, and a server failure needs investigation rather than repeated snippet changes.
  5. Try a controlled browser profile to identify an extension block. Do not bypass a visitor's privacy preferences. Then check the project's selected date range, path and domain.
  6. Collect the affected public URL, approximate time, request status and installation location for support. Omit account credentials and visitor data from screenshots.
typeof window.datasag?.track
// If undefined, first investigate whether the script executed.

new URL(location.href).searchParams.get('datasag_ignore')
// Also check for a previously saved browser exclusion.

What a successful check looks like

The first failed boundary is identified and corrected, and a new controlled visit reaches the right project. The browser Console and Network panel provide the evidence.

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

Do not replace the public project key with a Supabase, Stripe or provider secret. The browser snippet uses only the project's public tracking key.

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.