DataSag guides · Updated 27 October 2026

Track custom events on Webflow

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

Start with the Webflow installation

Open the site's custom code settings and add the tracker to the site-wide head code field. Save and publish to the intended production domain. Site-wide custom code access depends on the Webflow plan and permissions. Check the published site, not only the Designer canvas.

A page-specific custom code field or Embed can duplicate the site-wide script. Publishing only to the staging domain does not update the custom domain. Review both scopes before testing.

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 Webflow

  1. For a click goal, add a custom attribute named data-datasag-goal to the intended Webflow element and set its value to a stable event name. Inspect the published markup to confirm the attribute survived.
  2. Do not put a completed-signup name on a submit button. If completion matters, connect browser code to the actual success state or documented integration used by your form. A visual click alone cannot establish submission success.
  3. Publish to the production domain and test accepted and rejected input. For a click goal, expect one event per intended click. For completion, verify that only the confirmed success path produces the agreed named payload.

The published attribute measures click intent accurately, or a separate success integration records completion without confusing the two.

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 custom attribute named data-datasag-goal on an element for a click goal. A form-success conversion requires a success callback or success-state integration; the submit button attribute measures clicks only.

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 Webflow

The shared installation belongs in site-wide head custom code. 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 Webflow guides

Full Webflow setup guide · Search and AI visibility

References

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