DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on React with Vite

Multiple tracking requests do not necessarily mean duplicate pageviews. DataSag sends pageviews, scroll milestones, engagement updates and custom events. Inspect eventName before removing code. 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.

Fix duplicate analytics pageviews in React with Vite

  1. Search both index.html and React components for tracker insertion. A script in the HTML plus an effect-created script gives two independent initializations. Check tag managers or reusable analytics components as additional sources.
  2. Inspect whether a development-only Strict Mode effect cycle is involved. Move ownership to the single document installation instead of adding flags to every component. Keep unrelated React effect behavior intact.
  3. Build and publish, then test one initial load and one router transition. Inspect null-name pageview payloads separately from named events. If duplicates persist, inspect route listeners that send their own pageview event alongside the tracker.

The production document owns the tracker once, and React mount behavior no longer creates additional installations.

Complete the collection checks

  1. Open Network and filter /api/track. Reload once without clicking or scrolling. Inspect eventName in each payload: null identifies a pageview; scroll, click_heatmap and __datasag_engagement are other records.
  2. Count rendered script elements with data-datasag-key. There should be one intended installation for this project. Search your code, site header settings, embeds and tag manager for additional copies.
  3. Remove redundant script insertion mechanisms, keeping the site-wide installation. Two copies execute independently even when their browser download is cached.
  4. Check for custom router listeners that manually send pageviews. The current tracker handles pushState, replaceState and popstate and ignores a repeated pathname. Do not add a second pageview implementation without a demonstrated gap.
  5. Repeat a direct load, a second route and browser Back. Correlate pageview records with actual path changes. A query-only change on the same pathname is not a new pageview in the current tracker.
[...document.querySelectorAll('script[data-datasag-key]')]
  .map(script => ({
    src: script.src,
    key: script.getAttribute('data-datasag-key')
  }));

What a successful check looks like

A single installation and one pageview dispatch for each actual pathname change in the tested sequence. Additional engagement records remain available.

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

Comparing the total number of events with the number of pageviews produces a false duplicate diagnosis. Keep the event categories separate throughout the check.

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.