DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on SvelteKit

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

Start with the SvelteKit installation

Add the script to head in src/app.html, preserving %sveltekit.head% and the existing body template. That document template loads the tracker once for the application. Replace the public key before building and deploying.

Putting the tracker in a route component can reinstall it on navigation. Keep browser calls out of server load functions and test both direct entry and client-side navigation.

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 SvelteKit

  1. Search src/app.html, +layout.svelte, and +page.svelte for tracker insertion. Keep the shared installation once, and remove a route-mounted loader only after confirming that it duplicates the document script.
  2. Inspect afterNavigate callbacks and custom route listeners for another pageview implementation. The tracker already observes History API transitions. Preserve callbacks used for unrelated interface work while removing only redundant analytics dispatch.
  3. Test the published app through an initial load, internal link, and Back. Classify eventName before counting pageviews. Re-enter the route to check whether component lifecycle code has accumulated script elements or action listeners.

One template script handles the tested route sequence without an overlapping SvelteKit navigation sender.

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 SvelteKit

The shared installation belongs in the head of src/app.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 SvelteKit guides

Full SvelteKit setup guide · Search and AI visibility

References

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