Fix DataSag analytics not working 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 DataSag analytics not working in Django templates

1. Confirm the affected Django view returns HTML using the template you edited. Inspect template selection, inheritance and alternative template backends. A redirect or JSON response does not run a browser tracking script.
2. Check the deployed rendered source before troubleshooting static files. The DataSag tracker uses an absolute external URL, so an absent snippet is usually a template or release issue rather than a missing collected static asset.
3. If the snippet is present, inspect browser policy and endpoint responses. For missing actions, trace the browser callback rather than adding window calls to a view, signal or task. Record the view URL and response that reproduce the issue.

The diagnosis distinguishes template coverage, deployed output and browser delivery without misdirecting the repair into static-file collection.

Complete the collection checks

1. Confirm the change reached the public domain. Inspect the live HTML and clear only caches that serve the old document. A saved editor change may still need publishing.
2. Check that tracker.js exists in the Network panel and that the script contains the public key from the same DataSag project you are viewing.
3. Check whether your test browser is excluded with datasag_ignore. Restore inclusion with ?datasag_ignore=false only if this browser should count. Respect any consent controls configured on your site.
4. Inspect the browser Console for Content Security Policy or script errors. Check /api/track request responses: 400 indicates invalid input, 404 can indicate an unknown project key, and a server failure needs investigation rather than repeated snippet changes.
5. Try a controlled browser profile to identify an extension block. Do not bypass a visitor's privacy preferences. Then check the project's selected date range, path and domain.
6. Collect the affected public URL, approximate time, request status and installation location for support. Omit account credentials and visitor data from screenshots.

typeof window.datasag?.track
// If undefined, first investigate whether the script executed.

new URL(location.href).searchParams.get('datasag_ignore')
// Also check for a previously saved browser exclusion.

What a successful check looks like

The first failed boundary is identified and corrected, and a new controlled visit reaches the right project. The browser Console and Network panel provide the evidence.

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

Do not replace the public project key with a Supabase, Stripe or provider secret. The browser snippet uses only the project's public tracking key.

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 duplicate analytics pageviews
• 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.