Fix duplicate analytics pageviews on HTML websites

Start with the HTML websites installation

Paste the script into head in your shared HTML template. If the site has no shared template, add it to each document you want measured. Replace the example public key, upload the changed files and check a nested page as well as the homepage.

A homepage-only edit misses independent HTML documents. If you later introduce shared includes, remove old per-page copies so the final rendered page has one tracker.

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 HTML websites

1. Inspect the generated HTML rather than only the template fragments. A shared head include plus an older per-page snippet can produce two trackers even when each source file appears reasonable alone.
2. Keep one installation owner for each served document. If you moved to a shared include, remove the obsolete per-file copy and rebuild or upload the actual output before testing.
3. Open two independent documents directly and follow a normal link between them. Inspect null-name pageview payloads separately from named events. A new document load should have its own installation, while two scripts in one document are redundant.

Each served HTML document has one tracker, including pages converted from per-file snippets to shared templates.

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 HTML websites

The shared installation belongs in the head of every HTML document or shared template. 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 HTML websites guides

• Verify DataSag analytics
• Fix DataSag analytics not working
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits
• Load analytics without blocking rendering

Full HTML websites setup guide · Search and AI visibility

References

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