DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on SvelteKit

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

Start with the SvelteKit installation

Add the script to head in src/app.html, preserving %sveltekit.head% and the existing body template. That document template loads the tracker once for the application. Replace the public key before building and deploying.

Putting the tracker in a route component can reinstall it on navigation. Keep browser calls out of server load functions and test both direct entry and client-side navigation.

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 SvelteKit

  1. Confirm the deployed app uses the src/app.html template you edited. Preserve its required placeholders and inspect the delivered HTML on the affected route. A tracker inside one +page component leaves other entry paths uncovered.
  2. If an action event is missing, inspect where the call runs. Server load functions and server form actions cannot access window.datasag. The browser must receive the action result before reporting a confirmed outcome.
  3. Compare a direct load with enhanced navigation and form behavior on production. Check whether the tracker is available at the moment your browser callback runs, then inspect delivery errors before changing the adapter configuration.

The missing behavior is traced to document coverage, server-versus-browser execution, or event timing.

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 SvelteKit

The shared installation belongs in the head of src/app.html. 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 SvelteKit guides

Full SvelteKit setup guide · Search and AI visibility

References

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