DataSag guides · Updated 27 October 2026
Verify DataSag analytics on Hugo
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 Hugo.
Start with the Hugo installation
Add the deferred external script to the shared HTML head partial used by your Hugo theme, or to its applicable base template. Use a project override rather than editing a downloaded theme in place. Preserve Hugo template blocks, partial calls and existing head content, then rebuild and publish the generated files.
Hugo template lookup can select different templates by section, content type, language or output format. A theme may have a documented custom-head extension point. Inspect the rendered HTML for each intended page kind instead of assuming one partial covers all outputs.
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 Hugo
- Find the theme head partial or base template that actually renders the intended HTML page. Use its documented project override or extension point and preserve the surrounding Hugo blocks and partial calls.
- Build and publish the generated files, then open a nested article directly. Confirm the script and public key appear in the actual output rather than only in a theme source file.
- Check the homepage, a section page and a translated page if present. Hugo lookup rules can select another template by page kind or language. Verify pageview delivery for the HTML outputs you intend to measure.
The sampled Hugo page kinds and language templates render one working tracker in the published HTML.
Complete the collection checks
- 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.
- 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.
- 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.
- Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
- 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 Hugo
The shared installation belongs in the shared HTML head partial or base template used by the theme. 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 Hugo guides
References
Official Hugo documentation covers the integration point. For DataSag data handling, read the privacy policy. Use support if a request fails after these checks.