DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Angular

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

Start with the Angular installation

Inspect the Angular workspace project configuration to identify its index document, commonly src/index.html. Add the deferred external script once to the existing head and preserve the root element and build-managed assets. Build the intended application project and inspect its deployed output rather than a library package.

A workspace can contain several applications with different index files and build targets. Component templates and services should not repeatedly insert the global loader. For server rendering, keep browser API calls out of server execution.

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 Angular

  1. Search the selected index document, root component, services and route components for script insertion. A service that appends the tracker can duplicate the document installation even if dependency injection creates only one service instance.
  2. Inspect Router event subscriptions and manual pageview calls. Keep one supported pageview owner and ensure subscriptions or listeners created in destroyed components are cleaned up.
  3. Test the published app with direct entry, Router navigation and Back. Classify payloads by eventName and revisit a route to expose retained subscriptions. Keep hash-only changes separate from actual pathname transitions.

The Angular app has one tracker installation and no overlapping Router subscription reporting the same supported pageview.

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 Angular

The shared installation belongs in the head of the application index document selected by the build configuration. 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 Angular guides

Full Angular setup guide · Search and AI visibility

References

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