DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Ghost

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

Start with the Ghost installation

Add the DataSag script to the site-wide Site Header area of Ghost Code Injection. Replace the example public key, save the change and open the public publication. Keep the active theme's ghost_head helper because that helper outputs header injection. This does not require a DataSag-specific Ghost integration.

Ghost also offers code injection for individual posts. A post-level snippet does not cover the publication, and a theme-level copy can duplicate a global injection. Test a published article and a standalone page outside Ghost Admin.

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 Ghost

  1. Compare site-wide Site Header and Site Footer injection with post-specific injection. Search the active theme for tracker.js as well. Ghost can output all these sources in the same article document.
  2. Keep one publication-wide installation owner and remove only confirmed redundant copies. Preserve ghost_head and ghost_foot themselves because they output other Ghost functionality and are not analytics-specific duplication.
  3. Reload a signed-out article while inspecting eventName in tracking payloads. Then open another post. Separate actual pageview dispatches from click and scroll activity before concluding that the publication is counting pages twice.

One publication-level tracker remains, with required Ghost helpers intact and non-pageview events distinguished from duplicate loads.

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 Ghost

The shared installation belongs in the site-wide Site Header code injection field. 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 Ghost guides

Full Ghost setup guide · Search and AI visibility

References

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