DataSag guides · Updated 27 October 2026

Track custom events on Ghost

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

Start with the Ghost installation

Add the DataSag script to the site-wide Site Header area of Ghost Code Injection. Replace the example public key, save the change and open the public publication. Keep the active theme's ghost_head helper because that helper outputs header injection. This does not require a DataSag-specific Ghost integration.

Ghost also offers code injection for individual posts. A post-level snippet does not cover the publication, and a theme-level copy can duplicate a global injection. Test a published article and a standalone page outside Ghost Admin.

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 Ghost

  1. Choose an interaction your public theme owns, such as a link to a resource. Add data-datasag-goal to that theme markup or an HTML card and inspect the published element to confirm the attribute remains.
  2. Keep the global loader in Code Injection. If a custom theme script invokes window.datasag.track, call it from the observed success handler and avoid adding a second loader for that one article or card.
  3. Test the link on an article and a standalone page. For Portal or membership completion, first establish an observable success boundary; a subscribe click and an opened overlay alone do not establish that an account was created.

Owned theme interactions produce the agreed event, and membership outcomes are counted only when confirmation is observable.

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' });

For a click goal, use a goal attribute in markup you own in the theme or an HTML card. A Ghost membership or Portal click is not proof of a completed signup; only track success when your integration can observe 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 Ghost

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

Full Ghost setup guide · Search and AI visibility

References

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