DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Carrd

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

Start with the Carrd installation

On a Carrd plan that supports custom code, add an Embed element and set its type to Code. Paste the tracker, choose Hidden style and Head location, then publish. Carrd's documentation currently requires Pro Standard or higher for this mechanism. Use the published URL to verify the result.

An Inline Embed appears at its position in the document; a Hidden Head Embed is the intended shared loader. Carrd sections often use fragment navigation on one document. The current DataSag tracker counts pathname changes, so section switches should not be assumed to be separate pageviews.

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 Carrd

  1. Inspect all Embed elements for tracker.js, including Hidden Head, Body Top and Body End placements. A hidden element can remain out of sight in the design while still executing on every document load.
  2. Choose one Hidden Head installation and remove only verified duplicates. Check whether copied site sections or earlier experiments brought additional Embed elements into the same published document when you duplicated design content.
  3. Republish, open a clean public visit and inspect payload eventName. Section changes may generate click events but do not necessarily change the pathname. Do not count those records as duplicate pageviews without checking their type.

One hidden site-level loader remains, and section clicks are interpreted separately from pageview dispatches.

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 Carrd

The shared installation belongs in a Code Embed with Hidden style and Head location. 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 Carrd guides

Full Carrd setup guide · Search and AI visibility

References

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