DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Pelican

A script tag alone does not confirm that analytics works. Verify the published document, the request to DataSag and the matching visit in the correct project. This guide applies to Pelican.

Start with the Pelican installation

Find the Pelican theme selected by THEME or the build command's theme option. Add the deferred tracker to its shared templates/base.html head, preserving existing Jinja blocks and inherited content. Use a maintained theme copy or supported override, then build and deploy the generated site.

Pelican can use a different configuration for publication and a different theme for one build. Verify the command and settings used by deployment. Page and article templates must inherit the shared base for a base-template installation to cover them.

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 Pelican

  1. Inspect the production build command and THEME setting to find the actual theme directory. Trace article and page templates to its base.html so the tracker is placed in the shared head that those templates inherit.
  2. Generate output with the publication settings and inspect a full article, static page and archive. Confirm the external script retains its public key while existing Jinja blocks, metadata and content remain intact.
  3. Deploy that generated output and open the published documents directly. Compare their tracked paths with the URLs you requested. A preview built with another configuration does not establish that the production theme contains the same installation.

The selected publishing theme emits one keyed tracker across the intended article, page and archive output.

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 Pelican

The shared installation belongs in the head of the active theme templates/base.html. 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 Pelican guides

Full Pelican setup guide · Search and AI visibility

References

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