DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Hexo

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

Start with the Hexo installation

Find the active Hexo theme and its shared layout, such as themes/YOUR_THEME/layout/layout.ejs, or the head partial that layout includes. Add the deferred script once in head, preserving the body placeholder and the theme's template language. Regenerate and deploy the public files before testing.

Hexo templates can choose another layout or disable layout in front matter. Theme updates can overwrite direct edits, so maintain the customization through your theme's supported override or source-control workflow. An unused theme directory cannot affect the current build.

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 Hexo

  1. Search the theme's layout, head partial, post templates and raw content for DataSag. A shared partial and a copied script inside article content can both appear in the same generated HTML document.
  2. Inspect plugins or theme analytics settings that inject scripts during generation. Keep one confirmed installation owner and preserve other head resources; removing an entire shared partial can break metadata or theme styling.
  3. Regenerate the site and inspect final output before deployment. Then reload an article and an archive while reviewing eventName. If the theme includes client-navigation callbacks, verify they do not reinstall the global tracker on every content swap.

Generated theme output contains one loader and any navigation callbacks leave global initialization separate from page content.

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 Hexo

The shared installation belongs in the head of the active theme layout or its shared head partial. 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 Hexo guides

Full Hexo setup guide · Search and AI visibility

References

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