DataSag guides · Updated 27 October 2026

Track custom events on Django templates

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 Django templates.

Start with the Django templates installation

Add the external deferred script once to the base template used by your public views. Keep existing Django template blocks and static references. Place the snippet outside a block that child templates completely replace, or deliberately retain it in each override. The remote tracker needs no Django static-file copy.

Django admin, authentication templates and another template backend can have independent document structures. A successful base.html edit does not prove those routes inherit it. Check the actual view and template chain for each intended page.

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 Django templates

  1. Place a click goal attribute in the template element that the public view actually renders. If an included component emits the button, pass the attribute through that component rather than adding an unrelated wrapper click handler.
  2. For completion, invoke the tracker in browser code after the form request confirms success. Django view logic and model signals run on the server. A server-side success response needs a browser handler or a deliberately designed confirmation page.
  3. Test a validation failure and a successful form response through the production flow. Confirm the chosen event name appears only at its defined outcome and survives any partial template updates used by the frontend.

The public Django form integration reports a browser-observable success rather than every submission or server-side signal.

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 data-datasag-goal for a click or a browser success callback for a confirmed action. A Django view or model signal cannot invoke window.datasag in the visitor browser.

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 Django templates

The shared installation belongs in the head of the inherited base 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 Django templates guides

Full Django templates setup guide · Search and AI visibility

References

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