DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Remix v2

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 Remix v2.

Start with the Remix v2 installation

For a Remix v2 application, add one deferred external script to the existing document head in app/root.tsx. Preserve Meta, Links, Outlet, ScrollRestoration and Scripts in their established locations. Keep the tracker outside nested route components. This guide targets Remix v2 conventions; inspect different framework versions before copying their root shape.

An action or loader runs on the server and cannot use the browser window. Root error handling can render a different document. Test direct entries, client navigation and your relevant error route without adding another script to every nested route.

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 Remix v2

  1. Search app/root.tsx, nested routes and browser effects for tracker insertion. A persistent root script does not also need a copy in every route component.
  2. Inspect useLocation effects and custom navigation code for manual pageview dispatch. The tracker already observes its supported History API transitions, so keep another sender only for a verified unmet case.
  3. Test a production direct route, Remix Link transition and Back. Separate null-name pageviews from engagement and goal events. Revisit a route to detect a route-level effect that executes the script again.

The Remix route tree retains one root installation without an overlapping location-effect pageview mechanism.

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 Remix v2

The shared installation belongs in the head of the existing document in app/root.tsx. 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 Remix v2 guides

Full Remix v2 setup guide · Search and AI visibility

References

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