Track custom events - Documentation

Page views are collected automatically. Custom events cover everything else worth measuring — signups, purchases, form submissions, or any action specific to your site. What you need to provide:

Event names for the actions you care about (e.g., “Signed Up”, “Started Checkout”, “Booked Demo”)

client.track({
  event_name: 'Started Checkout',
  properties: { plan: 'pro' }
});

Every event automatically includes the visitor’s context: referrer, referring domain, device type, browser, operating system, and screen size. You only need to add properties specific to the action itself.

Events are tracked from the very first page view, before a visitor is identified. Once you identify a user, their anonymous events are merged into their record — nothing is lost.

Naming events

Pick names that read naturally in a report: a short verb phrase in past tense (“Signed Up”, “Submitted Contact Form”) works well. Keep names consistent — “Signed Up” and “signup_completed” become two separate events.

What you unlock

Custom events show up everywhere in Bigdelta:

On each user’s Activities timeline, alongside their page views
In the site-wide Events stream
As steps in Funnels, to measure conversion through key flows
As triggers for Workflows, to act on visitor behavior automatically