DataSag guides · Updated 27 October 2026

Track custom events on Squarespace

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

Start with the Squarespace installation

Open the site-wide Code Injection settings and paste the tracker into Header. Save the change, then open the public site outside the editor. Code injection availability depends on your plan; consult the platform documentation for your account.

A page header field or a code block may also contain the tracker. A code block only covers its page and can be removed with the content. Site-wide injection is easier to audit.

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 Squarespace

  1. Identify a published element you can target reliably through the available template or custom-code mechanism. If custom attributes are supported, use a goal attribute for click intent; otherwise use one browser listener through code injection.
  2. Keep the global tracker in the Header injection. Do not add another copy inside the listener code. Choose a click event name unless your form or integration exposes an actual confirmed success result.
  3. Test outside the editor and repeat after public navigation. Confirm the listener still targets the intended element and fires once. External booking and payment completion require their own observable confirmation, not just a local link click.

The published template records the intended local action once and does not mistake an external handoff for 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' });

If your template supports custom attributes, use data-datasag-goal for a click goal. Otherwise attach one browser listener through code injection. External booking or payment success requires its own observable confirmation.

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 Squarespace

The shared installation belongs in site-wide Header code injection. 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 Squarespace guides

Full Squarespace setup guide · Search and AI visibility

References

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