DataSag guides · Updated 27 October 2026

Track custom events on Remix v2

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

Start with the Remix v2 installation

For a Remix v2 application, add one deferred external script to the existing document head in app/root.tsx. Preserve Meta, Links, Outlet, ScrollRestoration and Scripts in their established locations. Keep the tracker outside nested route components. This guide targets Remix v2 conventions; inspect different framework versions before copying their root shape.

An action or loader runs on the server and cannot use the browser window. Root error handling can render a different document. Test direct entries, client navigation and your relevant error route without adding another script to every nested route.

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 Remix v2

  1. Identify the browser state that actually confirms a Remix action succeeded. A fetcher becoming idle alone is not proof; inspect the returned action data and your defined success result.
  2. Invoke the typed optional browser API from that confirmed outcome. Keep the server action and loader free of window calls, and retain the global loader in app/root.tsx.
  3. Test accepted and rejected submissions and a later return to the route. Make the success handler distinguish a newly completed action from old retained action data so navigation or rerendering does not emit the same conversion again.

The Remix browser integration reports each new successful action once rather than every fetcher-state change or render.

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

Use a client handler after a successful action result. A fetcher changing state or a Form submission beginning does not itself prove completion. Keep event definitions aligned with actual action data.

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 Remix v2

The shared installation belongs in the head of the existing document in app/root.tsx. 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 Remix v2 guides

Full Remix v2 setup guide · Search and AI visibility

References

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