DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Astro

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

Start with the Astro installation

Paste the external script into the head of the .astro layout used by your pages. Keep its src and data attribute on the actual script element. Use is:inline to make the intent explicit and leave the external tracker outside Astro's script bundling.

A layout only covers pages that use it. Check content collection pages and standalone landing pages too. If using client-side transitions, test a full route sequence rather than assuming a fresh document load every time.

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 Astro

  1. Search shared .astro layouts and individual pages for copies of the tracker. A page using a layout does not also need its own installation. Inspect the emitted document rather than counting source files alone.
  2. For ClientRouter sites, inspect is:inline and data-astro-rerun usage. Inline scripts can re-execute during transitions, and the current tracker installs global listeners. Do not force reruns as a generic route-tracking fix.
  3. Test entry, navigation away, and return to the same page. Compare the number of null-name pageviews and subsequent click or scroll events. An initialization that runs twice can leave duplicate listeners even if one script is visible afterward.

The tested Astro navigation sequence does not reinitialize the tracker or accumulate event listeners.

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 Astro

The shared installation belongs in the head of your shared .astro layout. Use this as the installation reference while checking the procedure above.

<script is:inline defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

Related Astro guides

Full Astro setup guide · Search and AI visibility

References

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