Verify DataSag analytics on WordPress

Start with the WordPress installation

Use a maintained site-wide header injection mechanism, or add a wp_head callback in your own child theme or site plugin. Paste the script into the header field once. Avoid editing a parent theme file that an update can overwrite. Publish and clear the relevant page cache.

Theme header settings, a header plugin and a tag manager can all inject scripts independently. Search each installation location. WordPress.com and managed plans can restrict custom scripts; confirm your plan permits JavaScript before changing themes or plugins.

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 WordPress

1. Identify the one site-wide installation owner: a header injection mechanism, child-theme wp_head callback, or site plugin. Confirm the active theme actually invokes that mechanism and that the tracker is not also in a page builder.
2. Publish and clear the relevant rendered-page cache. Open a logged-out post and a page directly, then inspect the live script and request key. An administrator preview may bypass the cached HTML visitors receive.
3. Check another template such as an archive or custom landing page. Theme templates and builder canvases can produce different documents, so prove coverage on the public page types you intend to measure.

Public WordPress templates contain the intended tracker after caching, rather than only in the administrator editing view.

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 WordPress

The shared installation belongs in a site-wide head injection or the wp_head hook. 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 WordPress 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 WordPress setup guide · Search and AI visibility

References

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