DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Vue 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 Vue with Vite.

Start with the Vue with Vite installation

Add one deferred external script to the root index.html used by the Vue Vite app. Keep it outside single-file components and preserve the application mount element and module entry. Build and publish the correct Vite application so the HTML visitors receive contains the project key.

An onMounted loader inside a route component can execute again when that component is recreated. Keep loading in the document rather than adding a new tracker through watchEffect or a route watcher. Inspect SSR-specific execution separately if your app adds server rendering.

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

  1. Search index.html and Vue components for onMounted script loaders. A route component can mount repeatedly, so document installation plus a component loader can produce repeated global initialization.
  2. Inspect route watchers and watchEffect callbacks for manual pageviews or named events that repeat as reactive dependencies change. Keep one installation and one intentional owner for each event definition.
  3. Test the production app on initial entry, route navigation and return. Inspect pageview payloads separately from named actions. If listeners are registered manually, verify onUnmounted cleanup for the component that owns them.

The Vue app avoids repeated global initialization and reactive callbacks no longer duplicate the same defined event.

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

The shared installation belongs in the head of the Vite application 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 Vue with Vite guides

Full Vue with Vite setup guide · Search and AI visibility

References

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