Verify DataSag analytics 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.

Verify DataSag analytics in Django templates

1. Trace the Django view to its selected template and extends chain. Put the script in the shared head and inspect any child block that replaces head content. An inherited base is only useful if the affected template uses it.
2. Deploy the template release and request a nested public page. Inspect its actual HTML for the public key and the external source. The remote script does not need collectstatic to copy it into STATIC_ROOT.
3. Check a second public view with another template, and follow the real form or navigation flow. Verify the pageview requests in the intended project. Keep Django admin and unrelated response types outside your coverage claim.

The tested public view inheritance chains render one correct external tracker and deliver the expected pageviews.

Complete the collection checks

1. Open the published website in a normal browser window with the Network panel recording. Use a browser profile where you can control extensions and your consent choice.
2. Filter network requests for tracker.js. Confirm it returns JavaScript successfully and that the rendered script has the project's data-datasag-key attribute. The example YOUR_PUBLIC_KEY must be replaced.
3. Filter for /api/track and reload once. Inspect a request with eventName null or absent. Its projectKey and path should match the chosen project and the page you opened.
4. Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
5. Navigate to a second path, then use Back. Compare pageview requests with the route changes rather than counting every request as a pageview.

document.querySelectorAll('script[data-datasag-key]').length
// Expected: 1

document.querySelector('script[data-datasag-key]')?.getAttribute('data-datasag-key')
// Expected: your project's public key

typeof window.datasag?.track
// Expected after the script runs: 'function'

What a successful check looks like

One rendered tracker installation, a successful request for the intended page and a corresponding entry in the intended project. Scroll and engagement requests are separate event types.

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

A successful tracker.js download only proves that a file loaded. It does not validate the project key, consent state or tracking endpoint. Test a real published path before declaring setup complete.

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

• Fix DataSag analytics not working
• 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.