DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Ruby on Rails

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 Ruby on Rails.

Start with the Ruby on Rails installation

Add the deferred external script once inside the head of the layout your public Rails views use, commonly app/views/layouts/application.html.erb. Preserve yield, asset tags, CSRF metadata and policy helpers. Inspect controller-specific layouts before assuming the application layout covers every route.

Turbo Drive, Turbo Frames and a full document visit have different lifecycles. The current tracker is a browser script with History API handling, not a native Turbo adapter. Test full-page and Turbo navigation before claiming coverage, and avoid placing the loader in each frame response.

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 Ruby on Rails

  1. Search the application layout, controller-specific layouts and included partials for duplicate snippets. Do not place the global tracker in a Turbo Frame body that can be inserted repeatedly.
  2. Inspect Stimulus controllers, Turbo lifecycle listeners and other browser code for another loader or pageview sender. Removing a DOM script tag does not necessarily remove the listeners registered by its previous execution.
  3. Deploy and test a full load, a real Turbo visit if used, and Back. Inspect pageview and named-event payloads separately, including a later click that can reveal duplicated delegated listeners.

The tested Rails and Turbo sequence does not initialize the global tracker or its listeners more than intended.

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 Ruby on Rails

The shared installation belongs in the head of the applicable ERB application layout. 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 Ruby on Rails guides

Full Ruby on Rails setup guide · Search and AI visibility

References

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