DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Carrd

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 Carrd.

Start with the Carrd installation

On a Carrd plan that supports custom code, add an Embed element and set its type to Code. Paste the tracker, choose Hidden style and Head location, then publish. Carrd's documentation currently requires Pro Standard or higher for this mechanism. Use the published URL to verify the result.

An Inline Embed appears at its position in the document; a Hidden Head Embed is the intended shared loader. Carrd sections often use fragment navigation on one document. The current DataSag tracker counts pathname changes, so section switches should not be assumed to be separate pageviews.

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 Carrd

  1. Check that your Carrd plan supports Code Embeds before looking for the missing setting. A text element containing a script example does not execute JavaScript and is not a replacement for a Code Embed.
  2. Inspect the Embed's type, Hidden placement and saved public key, then republish to the domain you are testing. Compare the live HTML with the builder; an unpublished change cannot affect public visits.
  3. If the homepage records visits but section changes do not, inspect whether only the URL fragment changes. The current tracker does not treat those changes as new pathnames. Define a separate section goal if you need that behavior.

The diagnosis distinguishes plan access, an unpublished Embed and expected single-document section behavior.

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 Carrd

The shared installation belongs in a Code Embed with Hidden style and Head location. 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 Carrd guides

Full Carrd setup guide · Search and AI visibility

References

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