DataSag guides · Updated 27 October 2026

Verify DataSag analytics on React with Vite

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 React with Vite.

Start with the React with Vite installation

Open the root index.html that Vite uses as its entry point. Paste the script into head once, outside the React component tree. Build and deploy the app, then inspect the deployed HTML. The tracker is a browser script and needs no npm package.

A React effect can run more than once during development or component remounts. Avoid inserting the tracker from useEffect when index.html already contains it. Development activity is not a substitute for checking the production build.

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 React with Vite

  1. Open the root index.html beside the Vite configuration. Add or inspect the single tracker in head, outside React components. Build and publish the app so you test the generated HTML served to visitors.
  2. Open the deployed index page and a deep route directly. Confirm the host serves the application document on each route and that both documents expose the intended script and public key.
  3. Use your actual React router to change pathnames, then use Back. Inspect pageview paths and delivery responses. Keep the tracker outside useEffect so component remounts do not become part of the installation.

Published direct entries and router transitions are measurable from the static document installation.

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 React with Vite

The shared installation belongs in the head of the root index.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 React with Vite guides

Full React with Vite setup guide · Search and AI visibility

References

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