DataSag guides · Updated 27 October 2026

Track custom events on SvelteKit

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

Start with the SvelteKit installation

Add the script to head in src/app.html, preserving %sveltekit.head% and the existing body template. That document template loads the tracker once for the application. Replace the public key before building and deploying.

Putting the tracker in a route component can reinstall it on navigation. Keep browser calls out of server load functions and test both direct entry and client-side navigation.

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 SvelteKit

  1. Identify the successful result in your browser form workflow. For an enhanced SvelteKit form, use its confirmed success result rather than the initial submit event, which may still return validation errors.
  2. Call the optional typed browser API from that success path. Keep server actions focused on the server result and leave tracker loading in src/app.html. Do not add a server-side window shim to make tracking compile.
  3. Test success, invalid input, and navigation back to the form. Inspect the event payload and verify that a repeated enhancement setup has not attached multiple callbacks to the same action.

Only the confirmed browser-side success path emits the completion event, including after client navigation.

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' });

Call the API in the browser after your form action succeeds. For an enhanced form, use its success result; an initial submit can still fail validation.

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 SvelteKit

The shared installation belongs in the head of src/app.html. 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 SvelteKit guides

Full SvelteKit setup guide · Search and AI visibility

References

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