DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Ruby on Rails

Find the first missing step in the delivery chain: published HTML, executing tracker, tracking request, successful response and project report. Changing several settings at once makes the failure harder to identify. 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.

Fix DataSag analytics not working in Ruby on Rails

  1. Trace the controller action to its selected layout and response format. A Turbo Frame response, JSON action or controller-specific layout can omit the full document head you changed.
  2. Check the published HTML and browser policy errors before editing the asset pipeline. The external tracker has its own absolute source; an absent layout snippet is a different problem from a failed application asset build.
  3. Compare a hard load with the failing Turbo or ordinary navigation sequence. For action events, inspect the actual browser success result. A model callback or successful controller branch does not execute window.datasag in the visitor session.

The missing case is localized to response layout, script delivery or the actual browser navigation and action lifecycle.

Complete the collection checks

  1. Confirm the change reached the public domain. Inspect the live HTML and clear only caches that serve the old document. A saved editor change may still need publishing.
  2. Check that tracker.js exists in the Network panel and that the script contains the public key from the same DataSag project you are viewing.
  3. Check whether your test browser is excluded with datasag_ignore. Restore inclusion with ?datasag_ignore=false only if this browser should count. Respect any consent controls configured on your site.
  4. Inspect the browser Console for Content Security Policy or script errors. Check /api/track request responses: 400 indicates invalid input, 404 can indicate an unknown project key, and a server failure needs investigation rather than repeated snippet changes.
  5. Try a controlled browser profile to identify an extension block. Do not bypass a visitor's privacy preferences. Then check the project's selected date range, path and domain.
  6. Collect the affected public URL, approximate time, request status and installation location for support. Omit account credentials and visitor data from screenshots.
typeof window.datasag?.track
// If undefined, first investigate whether the script executed.

new URL(location.href).searchParams.get('datasag_ignore')
// Also check for a previously saved browser exclusion.

What a successful check looks like

The first failed boundary is identified and corrected, and a new controlled visit reaches the right project. The browser Console and Network panel provide the evidence.

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

Do not replace the public project key with a Supabase, Stripe or provider secret. The browser snippet uses only the project's public tracking key.

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.