DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Remix v2

A script tag alone does not confirm that analytics works. Verify the published document, the request to DataSag and the matching visit in the correct project. 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.

Verify DataSag analytics in Remix v2

  1. Inspect the existing document structure in Remix v2 app/root.tsx. Confirm one deferred script in head while preserving Meta, Links, Outlet, ScrollRestoration and Scripts. Do not replace the root with an incomplete snippet.
  2. Build and deploy with your actual adapter, then open a nested route directly. Confirm the browser receives the script and sends a pageview with the expected key and path.
  3. Use a Remix Link to another pathname and use Back. Check the pageview requests without inserting a script in the nested route. If your root error document differs, inspect that document separately before claiming its coverage.

The Remix root document records direct entries and tested client navigation while preserving framework document behavior.

Complete the collection checks

  1. Open the published website in a normal browser window with the Network panel recording. Use a browser profile where you can control extensions and your consent choice.
  2. Filter network requests for tracker.js. Confirm it returns JavaScript successfully and that the rendered script has the project's data-datasag-key attribute. The example YOUR_PUBLIC_KEY must be replaced.
  3. Filter for /api/track and reload once. Inspect a request with eventName null or absent. Its projectKey and path should match the chosen project and the page you opened.
  4. Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
  5. Navigate to a second path, then use Back. Compare pageview requests with the route changes rather than counting every request as a pageview.
document.querySelectorAll('script[data-datasag-key]').length
// Expected: 1

document.querySelector('script[data-datasag-key]')?.getAttribute('data-datasag-key')
// Expected: your project's public key

typeof window.datasag?.track
// Expected after the script runs: 'function'

What a successful check looks like

One rendered tracker installation, a successful request for the intended page and a corresponding entry in the intended project. Scroll and engagement requests are separate event types.

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

A successful tracker.js download only proves that a file loaded. It does not validate the project key, consent state or tracking endpoint. Test a real published path before declaring setup complete.

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.