DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on WordPress

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

Start with the WordPress installation

Use a maintained site-wide header injection mechanism, or add a wp_head callback in your own child theme or site plugin. Paste the script into the header field once. Avoid editing a parent theme file that an update can overwrite. Publish and clear the relevant page cache.

Theme header settings, a header plugin and a tag manager can all inject scripts independently. Search each installation location. WordPress.com and managed plans can restrict custom scripts; confirm your plan permits JavaScript before changing themes or plugins.

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 WordPress

  1. Inventory the theme header settings, header injection plugin, child theme, page builder, and tag manager. WordPress can publish all these script sources at once, so a single saved snippet does not prove a single rendered installation.
  2. Keep one site-wide owner and remove only the duplicate snippet. Clear rendered-page caches after the change; otherwise a public visitor may still receive the previous document even when the dashboard configuration looks correct.
  3. Test a logged-out post and a builder-created landing page. Inspect pageview payloads separately from scroll and heatmap events, then repeat after navigating between page types to detect template-specific duplication.

The cached public documents contain one installation across both theme and builder templates.

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 WordPress

The shared installation belongs in a site-wide head injection or the wp_head hook. 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 WordPress guides

Full WordPress setup guide · Search and AI visibility

References

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