DataSag guides · Updated 27 October 2026

Track custom events on Framer

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

Start with the Framer installation

Add the tracker to the site custom code area with placement in head and scope covering the pages you want to measure. Choose the Once execution option for the tracker, rather than Run on every page visit. Publish and inspect the actual public site.

An embed or code component can run in a different document from the site. Avoid placing your only tracker inside a sandboxed embed. Route-level repeat execution can create duplicate installations.

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 Framer

  1. For a browser action in a code component, invoke the existing tracker from that component handler. A code override can also attach action behavior where appropriate; neither integration should install the global tracker again.
  2. Name the event for what Framer can observe. A click to an external signup or payment page is click intent, not proof that the remote action completed. Use a separately verified integration for the remote outcome.
  3. Test the published component directly and after navigating back to its page. Confirm one event with the chosen name. Keep scope and execution settings stable while checking for duplicate handler execution.

The published Framer action records the observable event once and makes no unsupported claim about an external completion.

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 code override or code component handler for browser events. Keep click intent separate from a successful external signup or payment that Framer cannot observe directly.

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 Framer

The shared installation belongs in site settings custom code for the head. 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 Framer guides

Full Framer setup guide · Search and AI visibility

References

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