DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on VitePress

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 VitePress.

Start with the VitePress installation

Merge a script tuple into the global VitePress head array. Include the external src, an empty-string defer attribute and the public data-datasag-key. Preserve other head entries, build the documentation and inspect its published HTML. Global config covers ordinary pages generated from that site.

VitePress also supports page-level head entries in frontmatter and custom theme code. A global script plus page or theme insertion can execute twice. Browser APIs belong in browser interaction code, not the Node-evaluated site configuration or an SSR render.

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 VitePress

  1. Inventory the global config head array, Markdown frontmatter head entries and custom theme setup. A reusable theme component that inserts the tracker can duplicate the script already emitted into the global document head.
  2. Inspect theme route hooks and mounted effects for manual pageview sending or repeated loader insertion. Keep a single installation owner and verify the current tracker's History API coverage before retaining additional route dispatch logic.
  3. Rebuild and test a direct document entry, sidebar navigation and Back. Keep heading-anchor interactions separate from pathname transitions, and inspect eventName so automatic engagement updates are not mistaken for another pageview.

The global loader remains singular and custom theme behavior does not double-dispatch the same documentation pathname transition.

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 VitePress

The shared installation belongs in the head array in .vitepress/config.ts or its configured equivalent. Use this as the installation reference while checking the procedure above.

// Merge into the existing .vitepress config.
export default {
  head: [["script", {
    src: "https://www.datasag.com/tracker.js",
    defer: "",
    "data-datasag-key": "YOUR_PUBLIC_KEY"
  }]]
};

Related VitePress guides

Full VitePress setup guide · Search and AI visibility

References

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