DataSag guides · Updated 27 October 2026

Verify DataSag analytics on HTML websites

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 HTML websites.

Start with the HTML websites installation

Paste the script into head in your shared HTML template. If the site has no shared template, add it to each document you want measured. Replace the example public key, upload the changed files and check a nested page as well as the homepage.

A homepage-only edit misses independent HTML documents. If you later introduce shared includes, remove old per-page copies so the final rendered page has one tracker.

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 HTML websites

  1. If your website has a shared template or include, inspect the final HTML it produces. If documents are independent, check each intended file for one tracker in head with the correct public key.
  2. Upload or publish the changed files and open a nested HTML page directly. Confirm the actual public response contains the snippet; a local file edit does not establish that the server serves the new document.
  3. Follow a link to another independent document and inspect its script and accepted pageview request too. Keep a list of verified files so a homepage-only installation does not masquerade as complete site coverage.

Every sampled independent document or shared-template output carries its own single working installation.

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 HTML websites

The shared installation belongs in the head of every HTML document or shared 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 HTML websites guides

Full HTML websites setup guide · Search and AI visibility

References

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