DataSag guides · Updated 27 October 2026

Track custom events on HTML websites

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

Start with the HTML websites installation

Paste the script into head in your shared HTML template. If the site has no shared template, add it to each document you want measured. Replace the example public key, upload the changed files and check a nested page as well as the homepage.

A homepage-only edit misses independent HTML documents. If you later introduce shared includes, remove old per-page copies so the final rendered page has one tracker.

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 HTML websites

  1. For a click goal, add data-datasag-goal to the actual link or button in the served HTML. Keep one ownership path for the action, rather than adding both the goal attribute and another click listener.
  2. For an asynchronous form, call the browser API after the successful response. If completion is represented by a separate confirmed page, ensure that page is actually reached only after success and contains the tracker.
  3. Publish the changed files and test accepted and rejected input. Confirm the goal name in the request and make sure a static success-looking page or a submit-button click is not being reported as a verified business outcome.

The published HTML action reports click intent or a confirmed success accurately, without duplicate callbacks.

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

Add data-datasag-goal to a link or button for click intent. For form completion, invoke the JavaScript API only after receiving a successful response or rendering a confirmed success page.

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 HTML websites

The shared installation belongs in the head of every HTML document or shared template. 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 HTML websites guides

Full HTML websites setup guide · Search and AI visibility

References

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