DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Framer

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 Framer.

Start with the Framer installation

Add the tracker to the site custom code area with placement in head and scope covering the pages you want to measure. Choose the Once execution option for the tracker, rather than Run on every page visit. Publish and inspect the actual public site.

An embed or code component can run in a different document from the site. Avoid placing your only tracker inside a sandboxed embed. Route-level repeat execution can create duplicate installations.

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 Framer

  1. Inspect the Custom Code entry page scope and placement. A snippet restricted to one page cannot measure every entry. A script inside an embed may run in an isolated document instead of the published website.
  2. Check the public domain after publishing, not the design canvas. Compare the rendered element and key on a working page and the missing page before adding another code component.
  3. If navigation is the only missing case, test it with the Once setting and inspect path requests. Do not change to repeated code execution before checking whether it would add duplicate global tracker listeners.

The failing case is traced to Framer page scope, embedded-document isolation, publication, or browser 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 Framer

The shared installation belongs in site settings custom code for the head. 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 Framer guides

Full Framer setup guide · Search and AI visibility

References

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