Verify DataSag analytics on Webflow

Start with the Webflow installation

Open the site's custom code settings and add the tracker to the site-wide head code field. Save and publish to the intended production domain. Site-wide custom code access depends on the Webflow plan and permissions. Check the published site, not only the Designer canvas.

A page-specific custom code field or Embed can duplicate the site-wide script. Publishing only to the staging domain does not update the custom domain. Review both scopes before testing.

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 Webflow

1. Open the site-wide head custom-code location and confirm it contains the tracker with your public key. Check page-specific code and Embeds for another installation before publishing.
2. Publish to the intended custom domain and open that domain outside Designer. A staging-only publish does not verify the production website. Inspect the real script and accepted pageview request.
3. Open a static page and a published CMS item directly. Confirm both inherit the site-wide snippet and send their own path. Keep the CMS check separate from an editor preview of its template.

The actual custom-domain static and CMS pages both carry one working site-wide 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 Webflow

The shared installation belongs in site-wide head custom code. 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 Webflow 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 Webflow setup guide · Search and AI visibility

References

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