Fix duplicate analytics pageviews on Django templates

Start with the Django templates installation

Add the external deferred script once to the base template used by your public views. Keep existing Django template blocks and static references. Place the snippet outside a block that child templates completely replace, or deliberately retain it in each override. The remote tracker needs no Django static-file copy.

Django admin, authentication templates and another template backend can have independent document structures. A successful base.html edit does not prove those routes inherit it. Check the actual view and template chain for each intended page.

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 Django templates

1. Inspect the base template, head blocks and included fragments together. A child using block.super plus a repeated local snippet can render the same tracker twice even though the template inheritance itself works.
2. Search JavaScript used for progressive page updates for another loader or pageview sender. Retain one intended shared installation and preserve unrelated template blocks and asset references.
3. Deploy and test two public views, including one with an overridden head block. Count null-name pageview payloads separately from named events. Inspect the final HTML to prove the compiled or cached response no longer contains duplicate scripts.

The relevant Django templates render one tracker after inheritance, includes and head overrides are applied.

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 Django templates

The shared installation belongs in the head of the inherited base template. 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 Django templates guides

• Verify DataSag analytics
• Fix DataSag analytics not working
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits
• Load analytics without blocking rendering

Full Django templates setup guide · Search and AI visibility

References

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