Verify DataSag analytics on Express with EJS

Start with the Express with EJS installation

Add the deferred tracker to the shared EJS partial that emits your document head. Include that partial through the existing local include pattern in each intended template. EJS has no built-in universal layout convention, so identify your actual application composition rather than assuming a views/layout.ejs file exists.

A res.send response or a separately rendered error template can bypass your usual partials. Keep the snippet in browser HTML rather than Express middleware that only logs requests. Never include a template path supplied directly by an untrusted visitor.

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 Express with EJS

1. Follow the Express route res.render call to the EJS template and its shared head include. EJS does not impose a layout file, so inspect your actual include chain before choosing an installation location.
2. Deploy and open a nested route directly. Confirm the include emits a real script rather than escaped text, with the intended public key. Only use trusted local template paths for includes.
3. Test a second route, including an error or authentication document if you intend to measure it. A res.send response may not use EJS at all. Check the matching pageview request for each intended HTML route.

The actual Express render paths emit one valid browser tracker through their EJS composition.

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 Express with EJS

The shared installation belongs in a shared EJS head partial included by the intended page templates. 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 Express with EJS 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 Express with EJS setup guide · Search and AI visibility

References

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