DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Remix v2

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 Remix v2.

Start with the Remix v2 installation

For a Remix v2 application, add one deferred external script to the existing document head in app/root.tsx. Preserve Meta, Links, Outlet, ScrollRestoration and Scripts in their established locations. Keep the tracker outside nested route components. This guide targets Remix v2 conventions; inspect different framework versions before copying their root shape.

An action or loader runs on the server and cannot use the browser window. Root error handling can render a different document. Test direct entries, client navigation and your relevant error route without adding another script to every nested route.

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 Remix v2

  1. Check that the affected Remix v2 route renders under the root document you edited. A custom error document or response returned outside the normal UI can omit the root head.
  2. Inspect the deployed script and browser errors before changing the adapter. If only a named action is missing, locate the browser code that handles successful action data rather than a server loader or action.
  3. Compare a hard load, a Remix Link transition and the actual Form or fetcher workflow. Confirm the tracker exists when the browser handler runs, and inspect accepted or rejected event responses before adding another root script.

The missing behavior is identified as document coverage, script execution or successful action-result handling.

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 Remix v2

The shared installation belongs in the head of the existing document in app/root.tsx. 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 Remix v2 guides

Full Remix v2 setup guide · Search and AI visibility

References

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