DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Nuxt

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

Start with the Nuxt installation

Add one external script entry to app.head.script in nuxt.config.ts. Merge it into existing head settings rather than replacing them. The public project key is intended for the browser; it is not a server credential.

Check whether a plugin or useHead call already installs the same tracker. A server route cannot access window.datasag. Use browser handlers and retain your app's existing consent controls.

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 Nuxt

  1. Search nuxt.config.ts, plugins, layouts, and useHead calls for the tracker source. A global head entry plus a client plugin that inserts the same script creates overlapping ownership.
  2. Inspect route watchers or router hooks for manual pageview dispatch. Keep the current tracker as the owner of its supported History API transitions unless an actual missing route case requires another integration.
  3. Test a published direct route, internal Nuxt navigation, and Back. Inspect null-name payloads and listener behavior after revisiting a route. A cached script request does not prevent the same script from executing twice.

The tested Nuxt route sequence has one shared script and no second route watcher sending the same measurement.

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 Nuxt

The shared installation belongs in the app head configuration in nuxt.config.ts. Use this as the installation reference while checking the procedure above.

export default defineNuxtConfig({
  app: {
    head: {
      script: [{
        src: "https://www.datasag.com/tracker.js",
        "data-datasag-key": "YOUR_PUBLIC_KEY",
        defer: true
      }]
    }
  }
});

Related Nuxt guides

Full Nuxt setup guide · Search and AI visibility

References

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