Verify DataSag analytics on Angular

Start with the Angular installation

Inspect the Angular workspace project configuration to identify its index document, commonly src/index.html. Add the deferred external script once to the existing head and preserve the root element and build-managed assets. Build the intended application project and inspect its deployed output rather than a library package.

A workspace can contain several applications with different index files and build targets. Component templates and services should not repeatedly insert the global loader. For server rendering, keep browser API calls out of server execution.

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 Angular

1. Find the Angular application project and index entry in the workspace build configuration. Confirm the tracker is in that selected document, not another app or library template in the same workspace.
2. Build and deploy the intended application target. Open a nested public route directly and inspect the final script and pageview. Confirm the host returns the Angular document rather than a deep-link 404.
3. Navigate through Router links and Back. Check pageview paths while the single host document remains loaded. If your router uses hash locations, do not assume fragment changes produce new tracker pathname pageviews.

The chosen Angular build target records direct entries and supported pathname navigation from one host document.

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 Angular

The shared installation belongs in the head of the application index document selected by the build configuration. 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 Angular 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 Angular setup guide · Search and AI visibility

References

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