DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Carrd

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

Verify DataSag analytics in Carrd

  1. Confirm your Carrd plan exposes custom Code Embeds, then inspect the tracker Embed. Its type should be Code, its style Hidden and its location Head. Replace the public key and publish the site.
  2. Open the published domain outside the builder. Inspect the actual head script and its first pageview request. A code label in the builder helps identify the Embed but does not prove the external script executed.
  3. Follow any section navigation and inspect the resulting URL. Fragment-only movement normally retains one pathname, so check section interaction goals separately. Reload a direct section link to confirm the initial document still receives analytics.

The published Carrd document loads one tracker, with fragment sections distinguished from separate pathname-based pages.

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