DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Webflow

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

Start with the Webflow installation

Open the site's custom code settings and add the tracker to the site-wide head code field. Save and publish to the intended production domain. Site-wide custom code access depends on the Webflow plan and permissions. Check the published site, not only the Designer canvas.

A page-specific custom code field or Embed can duplicate the site-wide script. Publishing only to the staging domain does not update the custom domain. Review both scopes before testing.

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 Webflow

  1. Check that your plan and permissions expose the custom-code mechanism. Confirm the snippet was saved at site level and published to the custom domain where you are testing, rather than only to staging.
  2. Inspect the published page instead of Designer. If one page is missing tracking, compare its page custom code and any Embed with a working page. A sandboxed or isolated Embed is not the same document as the website.
  3. If the script is present, inspect browser policy and network errors and compare the key with the DataSag project. Record the published domain and page type before changing layouts or republishing unrelated content.

The investigation locates the problem in publishing scope, document placement, or delivery on the public Webflow website.

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 Webflow

The shared installation belongs in site-wide head custom code. 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 Webflow guides

Full Webflow setup guide · Search and AI visibility

References

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