DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Webflow

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

Start with the Webflow installation

Open the site's custom code settings and add the tracker to the site-wide head code field. Save and publish to the intended production domain. Site-wide custom code access depends on the Webflow plan and permissions. Check the published site, not only the Designer canvas.

A page-specific custom code field or Embed can duplicate the site-wide script. Publishing only to the staging domain does not update the custom domain. Review both scopes before testing.

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 Webflow

  1. Search the site-wide head code, page-specific code, and Embed elements for DataSag. A CMS template can add a copy on every item even when the global setting already installs the tracker.
  2. Remove the redundant installation at its owning scope and publish the affected site to the custom domain. Keep the global copy if it is the intended owner so other pages retain measurement.
  3. Test one ordinary page and one CMS item on the public domain. Count rendered scripts and inspect null-name pageview payloads. Named click or scroll events should stay separate from the duplication diagnosis.

The published global and CMS scopes no longer inject overlapping trackers.

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 Webflow

The shared installation belongs in site-wide head custom code. 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 Webflow guides

Full Webflow setup guide · Search and AI visibility

References

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