DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Pelican

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

Start with the Pelican installation

Find the Pelican theme selected by THEME or the build command's theme option. Add the deferred tracker to its shared templates/base.html head, preserving existing Jinja blocks and inherited content. Use a maintained theme copy or supported override, then build and deploy the generated site.

Pelican can use a different configuration for publication and a different theme for one build. Verify the command and settings used by deployment. Page and article templates must inherit the shared base for a base-template installation to cover them.

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 Pelican

  1. Search the active theme base template, child templates, includes and content HTML for tracker.js. Inherited Jinja blocks can output both a parent installation and a child copy when the child also calls super().
  2. Inspect generation plugins or theme analytics settings for another injected loader. Choose one installation owner, but preserve Jinja parent content needed for other resources rather than deleting an entire block to remove one duplicate.
  3. Build publication output and inspect the final article HTML. Reload it while comparing pageview event types, then repeat on a static page. Scroll and engagement updates should remain distinguishable from independent script initializations.

Final Jinja output has one tracker while unrelated inherited head and theme content remain available.

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 Pelican

The shared installation belongs in the head of the active theme templates/base.html. 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 Pelican guides

Full Pelican setup guide · Search and AI visibility

References

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