Build on VeritaMetrics

Tracking API

The client-side tracking API is available on any page that includes the VeritaMetrics snippet. Pageviews are tracked automatically. Use the API to track custom events, revenue, and goals.

Custom Events

Track any user action with a name and optional metadata. Events appear in your dashboard within seconds.

Revenue Tracking

Attach order IDs, amounts, and currency to attribute revenue to traffic sources and campaigns.

No-Code Goals

Add data-verita-event-name="Signup" to any HTML element. Clicks are tracked automatically, no JavaScript required. Attach properties with data-verita-prop-* attributes.

How events appear in your dashboard

Top Events groups your events by name, so form_submit and Signup each appear as their own row with its own total. Open a row to drill in: the panel breaks that event down by the page it fired on, an element label, and the link destination. Any other properties you send are stored and appear in your CSV, JSON, and XLSX exports; they are not charted as a separate breakdown. To split one event by a value (which plan, which card, which button), put that value in the event name, or send it as a text property so it shows under the label breakdown.

Core Web Vitals (optional)

Collect real-user LCP, INP, and CLS by adding data-web-vitals="true" to your tracking script tag (see the code panel). It is off by default and available on every plan, including Free. The tracker reports each metric once per page on hide, and the dashboard shows the p75. See the Web Vitals page for how field data differs from a lab test.

Warm-lead intent signal (optional)

Add data-warm-lead="true" to your script tag and the tracker scores the session cookielessly, then dispatches a veritametrics:intent DOM event (and runs any window.verita("onIntent", cb) callbacks) once the session turns warm or hot on exit intent. The detail is { tier, score, reasons }, with no personal data. Use it to open a form or ping your CRM. See the warm-lead capture guide.

Visitor opt-out

window.verita("optOut") stops collection at once and records the choice in one localStorage key, so later visits to your site load the tracker and it exits before attaching a single listener. window.verita("optIn") clears it. Wire both to a control on your privacy page. The commands are safe to call on a page where the tracker has already opted out, and they do not throw when a browser blocks storage, though in that case the choice lasts only for the current page load. This is separate from Global Privacy Control and Do Not Track, which the tracker honours on its own with no code from you.

// Track a custom event
window.verita("trackEvent", "form_submit", {
  formId: "contact",
  source: "homepage"
});

// Track a purchase with revenue
window.verita("trackRevenue", {
  orderId: "ORD-1234",
  amount: 49.99,
  currency: "USD"
});

// Stop collecting for this visitor, on this
// site, and remember it across visits
window.verita("optOut");

// Undo it
window.verita("optIn");

<!-- No JavaScript needed -->
<button
  data-verita-event-name="Signup"
  data-verita-prop-plan="pro"
>
  Create Account
</button>

// Pass "text" to break the event down by that value
window.verita("trackEvent", "cta_click", {
  text: "Create a free account"
});

// Or encode the value in the event name itself
window.verita("trackEvent", "signup_pro");

<!-- Add data-web-vitals to enable LCP, INP, CLS -->
<script
  defer
  data-site-id="YOUR_SITE_ID"
  data-web-vitals="true"
  src="https://www.veritametrics.com/tracker.js"
></script>

// Enable with data-warm-lead="true" on the tag,
// then listen for the browser event:
document.addEventListener("veritametrics:intent", (e) => {
  // e.detail = { tier, score, reasons } (no PII)
  if (e.detail.tier === "hot") openYourForm();
});

// or a callback:
window.verita("onIntent", (detail) => {
  // detail = { tier, score, reasons }
});