DataSag guides · Updated 27 October 2026

Track custom events on Carrd

Use data-datasag-goal for a click goal, or call window.datasag.track after a completed action. Choose a stable event name and distinguish a click from a successful conversion. 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.

Track custom events in Carrd

  1. For custom markup you control, put data-datasag-goal on a real link or button inside a Code Embed. Choose a name that describes click intent, and keep the global tracker in its separate Hidden Head Embed.
  2. If you attach a browser listener through custom code, target an element that survives the published build and bind it once. Inspect the public element rather than assuming the builder's visual label is a DOM identifier.
  3. Test the interaction on the published domain, including any section where it appears. A submit click can precede validation or a network failure; emit a completed-form event only from the success mechanism available to your actual form configuration.

Custom owned markup records click intent once, while successful form events require a verified confirmation boundary.

Complete the collection checks

  1. Write the event definition first. For example, signup_click means a visitor pressed a signup link, while signup_completed means your application confirmed account creation.
  2. For click intent, add data-datasag-goal to the element. The tracker delegates clicks, so you do not also need a JavaScript handler for the same goal.
  3. For a completed action, call the JavaScript API in the success handler. Wait for the tracker to be available. An optional guard avoids a crash but intentionally drops the event if the tracker has not loaded.
  4. Send only the context needed for the report, such as a form or plan name. Do not include email addresses, passwords, payment details or freeform form contents.
  5. Complete one successful and one failed attempt. Inspect /api/track for the exact eventName and properties. Only the successful attempt should emit a completed-action event.
  6. Check the event report available to your plan. Collection and access to reports are separate; review current plan details before depending on a particular report.
<!-- Click intent: use this OR your own click handler -->
<a href="/signup" data-datasag-goal="signup_click">Create account</a>

// JavaScript: inside the confirmed-success handler
window.datasag?.track('signup_completed', { form: 'main_signup' });

For a goal on custom markup you own, use data-datasag-goal in the Code Embed. Track a form completion only through a confirmed success mechanism your Carrd form setup actually provides, rather than a submit-button click.

What a successful check looks like

A controlled successful action produces one event with the agreed name. A validation failure does not emit a success event. Network evidence matches the report definition.

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 goal attribute on a submit button measures clicks, including attempts that fail. Do not report those clicks as completed signups or purchases.

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.