DataSag guides · Updated 27 October 2026

Track custom events on WordPress

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

Start with the WordPress installation

Use a maintained site-wide header injection mechanism, or add a wp_head callback in your own child theme or site plugin. Paste the script into the header field once. Avoid editing a parent theme file that an update can overwrite. Publish and clear the relevant page cache.

Theme header settings, a header plugin and a tag manager can all inject scripts independently. Search each installation location. WordPress.com and managed plans can restrict custom scripts; confirm your plan permits JavaScript before changing themes or plugins.

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 WordPress

  1. For click intent, add data-datasag-goal through markup or an editor attribute mechanism that preserves the attribute. Inspect the published element because editors and sanitizers may remove custom attributes.
  2. For a completed form action, use the particular form plugin documented browser success hook. An HTML submit or a submit-button goal fires before the plugin knows whether validation and delivery succeeded.
  3. Test the public form logged out with accepted and rejected input. Recheck after any page-cache or script-optimization change. Inspect one named event for success and confirm both a goal attribute and a custom listener are not reporting the same click.

The published WordPress element or form integration reports the intended outcome once, after any editor and plugin transformations.

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

Add data-datasag-goal to the button markup if your editor preserves custom attributes. For a successful form conversion, use your form plugin's documented success hook instead of counting every submit attempt.

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 WordPress

The shared installation belongs in a site-wide head injection or the wp_head hook. 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 WordPress guides

Full WordPress setup guide · Search and AI visibility

References

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