DataSag guides · Updated 27 October 2026

Track custom events on Hugo

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

Start with the Hugo installation

Add the deferred external script to the shared HTML head partial used by your Hugo theme, or to its applicable base template. Use a project override rather than editing a downloaded theme in place. Preserve Hugo template blocks, partial calls and existing head content, then rebuild and publish the generated files.

Hugo template lookup can select different templates by section, content type, language or output format. A theme may have a documented custom-head extension point. Inspect the rendered HTML for each intended page kind instead of assuming one partial covers all outputs.

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 Hugo

  1. For click intent, add data-datasag-goal in the template, partial or shortcode that emits the control. Inspect the generated HTML to confirm the attribute survives the theme output.
  2. For a dynamic form outcome, use its real browser success callback. Hugo build-time template evaluation cannot observe a later visitor action, and a link to an external service does not establish completion there.
  3. Build, publish and test the actual public interaction. For completion events, include a rejected submission. If a shortcode includes JavaScript, ensure repeated instances do not attach duplicate callbacks for the same action.

The generated Hugo element or dynamic-form integration reports the browser-observable action once.

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 goal attribute in a rendered link or button for click intent. For a dynamic form, use its actual browser success callback. Hugo build-time template evaluation cannot observe a visitor completing an action.

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 Hugo

The shared installation belongs in the shared HTML head partial or base template used by the theme. 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 Hugo guides

Full Hugo setup guide · Search and AI visibility

References

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