DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Hugo

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

Start with the Hugo installation

Add the deferred external script to the shared HTML head partial used by your Hugo theme, or to its applicable base template. Use a project override rather than editing a downloaded theme in place. Preserve Hugo template blocks, partial calls and existing head content, then rebuild and publish the generated files.

Hugo template lookup can select different templates by section, content type, language or output format. A theme may have a documented custom-head extension point. Inspect the rendered HTML for each intended page kind instead of assuming one partial covers all outputs.

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 Hugo

  1. Inspect the final HTML produced by theme partials, project overrides and content shortcodes. A shortcode or page-specific fragment can duplicate a tracker already emitted by the base head.
  2. Keep one intended theme extension point or project override. Remove only the redundant loader, preserving other theme head content and any generated asset references.
  3. Rebuild and publish, then test a home page, article and section page. Count actual script elements and null-name pageviews separately from goals. Verify another language template if it uses a different head override.

The built Hugo outputs contain one tracker after theme lookup, overrides and shortcodes are resolved.

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 Hugo

The shared installation belongs in the shared HTML head partial or base template used by the theme. 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 Hugo guides

Full Hugo setup guide · Search and AI visibility

References

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