NeuTargetNeuTarget
Feature

Track any interaction - one line of code

NeuTarget auto-tracks pageviews, payment clicks, and app store taps out of the box. But your business has interactions that matter beyond those - CTA clicks, form submissions, video plays, add-to-cart actions, file downloads. Custom events let you track all of them with a single function call: window.__nt.track().

Why this matters for your business

Go beyond pageviews. Track CTA clicks, form submissions, video plays, add-to-cart actions, and any custom interaction with a single function call.

One function call - zero config

After installing the browser SDK, call window.__nt.track('cta_click', { label: 'hero_signup' }) from your frontend. An ordinary custom event does not require prior schema registration.

Full context, automatically

The SDK attaches available session and campaign context to each event. Your code supplies the supported interaction details; privacy settings and browser availability govern the context retained.

Track JS-triggered payments

Razorpay checkout.js, PhonePe SDK, or any modal-based payment flow that doesn't use a standard <a> link - capture them with window.__nt.track('payment_click', { provider: 'razorpay' }).

Measure what moves revenue

Track add-to-cart, wishlist adds, pricing page CTAs, and free-trial signups. Correlate custom events with campaigns to find which traffic source drives action, not just visits.

Privacy-first by default

Custom events follow the website’s collection instructions and use pseudonymous session context. Keep direct identifiers and sensitive information out of event names and properties.

Works with every framework

Plain HTML, React, Next.js, Vue, Shopify - if it runs JavaScript, window.__nt.track() works. Fires via the same beacon/fetch pipeline as auto-tracked events.

How it works

1

Add NeuTarget's tracker script to your site (same Deferred SDK script tag)

2

The tracker exposes window.__nt.track(eventType, data) globally after loading

3

Call it from any click handler, form submit, intersection observer, or custom logic

4

The SDK uses its beacon/fetch delivery path. Navigation and network conditions can still prevent browser event delivery.

5

Events appear in your dashboard alongside auto-tracked pageviews and payment clicks

Frequently asked questions

Do I need to register event types in advance?

No. Call window.__nt.track() with any event name - it's schema-free. Use descriptive snake_case names like cta_click, form_submit, add_to_cart.

What data can I include in the event?

Use the documented event fields for the interaction you need to measure. Keep properties minimal, exclude direct identifiers and secrets, and validate which fields appear in your reports.

Will custom events work on SPAs?

Yes. The tracker persists across SPA navigations. Call window.__nt.track() at any point during the page lifecycle - it uses the current pathname and session context.

What if the tracker hasn't loaded yet?

Guard your call with if (window.__nt) { window.__nt.track(...) }. If the tracker loads with defer, it's typically ready before any user interaction.

How is this different from Mixpanel or Amplitude custom events?

Install the NeuTarget browser SDK once, then call its global track function without registering ordinary event schemas. Review the documented property handling and website collection settings before deployment.

Start with a 14-day analytics trial

Explore cookieless website analytics with limited NeuIntel usage. Paid revenue reporting and connected ad spend have separate plan requirements.