DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Ruby on Rails

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 Ruby on Rails.

Start with the Ruby on Rails installation

Add the deferred external script once inside the head of the layout your public Rails views use, commonly app/views/layouts/application.html.erb. Preserve yield, asset tags, CSRF metadata and policy helpers. Inspect controller-specific layouts before assuming the application layout covers every route.

Turbo Drive, Turbo Frames and a full document visit have different lifecycles. The current tracker is a browser script with History API handling, not a native Turbo adapter. Test full-page and Turbo navigation before claiming coverage, and avoid placing the loader in each frame response.

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 Ruby on Rails

  1. Find the Rails layout selected by the public controller. Inspect its head for one tracker, preserving yield, CSRF metadata and asset tags. Check controller-specific layouts rather than assuming application.html.erb owns every page.
  2. Deploy and open a nested route directly. Confirm the script key and accepted pageview request in the real document. Then follow an ordinary navigation using the frontend behavior actually enabled on your app.
  3. If Turbo is enabled, test a Turbo visit and any relevant frame flow explicitly. A frame update is not necessarily a new pathname, and the tracker is not a native Turbo adapter. Record which navigation cases you verified.

The selected Rails layouts record full entries, with Turbo-specific coverage documented only where it was actually checked.

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 Ruby on Rails

The shared installation belongs in the head of the applicable ERB application layout. 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 Ruby on Rails guides

Full Ruby on Rails setup guide · Search and AI visibility

References

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