DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Framer

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

Start with the Framer installation

Add the tracker to the site custom code area with placement in head and scope covering the pages you want to measure. Choose the Once execution option for the tracker, rather than Run on every page visit. Publish and inspect the actual public site.

An embed or code component can run in a different document from the site. Avoid placing your only tracker inside a sandboxed embed. Route-level repeat execution can create duplicate installations.

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 Framer

  1. Inspect every matching Custom Code entry, its page scope, and its execution option. Keep one intended tracker entry using Once. Run on every page visit can execute initialization again during client navigation.
  2. Check code components and embeds for another copy, especially if you first tested analytics in a component and later added it globally. Remove only the redundant owner and publish the updated site.
  3. Open the production site, navigate away, and return to a page. Inspect both pageviews and subsequent click events for repeated listeners. A single script visible after navigation does not prove it executed only once.

The public Framer route sequence uses one initialization and does not accumulate another set of tracking listeners.

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 Framer

The shared installation belongs in site settings custom code for the head. 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 Framer guides

Full Framer setup guide · Search and AI visibility

References

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