V4 Vectr4
Menu
Try Demo

Event tracking

Self-hosted event tracking for product teams that want control.

Capture pageviews, custom product events, and useful properties with a Vectr4 deployment running on your own infrastructure.

What you can capture

Record the product actions that explain how people use your app.

Pageviews

See which product and marketing pages users visit

Capture page URLs and referrers so page activity can be reviewed alongside product behavior.

Custom product events

Track actions that matter to activation

Send events for signups, demo starts, projects created, checkout steps, feature use, or other meaningful product actions.

Useful properties

Add context without changing the event name

Attach relevant properties to distinguish plans, product areas, workflow steps, or other context your team needs to interpret an event.

How tracking reaches Vectr4

Use the browser SDK and Event ingestion API with your deployment.

Use the SDK to capture product events and send them to the Vectr4 services you deploy. The dashboard then gives those events a practical place in your wider product analytics workflow.

  1. 01Deploy Vectr4.

    Run the analytics stack on your VPS with your own domain and deployment configuration.

  2. 02Connect your product.

    Initialize tracking and send pageviews, named events, identify calls, and relevant properties.

  3. 03Review behavior.

    Use captured events as inputs for activity views, funnels, session summaries, and user journeys.

Read the Docker deployment docs

Focused feature page

Event tracking is the input layer.

Events describe what happened. Continue to analyze product events with properties, identity, funnels, sessions, and user journeys.

Implementation sequence

Initialize, identify, track, and verify.

Use stable event names, send only necessary properties, and validate the payload in Vectr4 before building funnels or behavior analysis on top of it.

import vectra from '@vectr4/sdk';

const publicProjectKey = String(import.meta.env.PUBLIC_VECTRA_API_KEY);

vectra.init({
  apiKey: publicProjectKey,
  apiHost: 'https://analytics.example.com',
});

vectra.identify('user_123');
vectra.track('workspace_created', { plan: 'starter' });

Evaluate before deploying

See event tracking in the demo, then deploy Vectr4 on your VPS.

Inspect the event and product analytics workflow first. Purchase only when the dashboard and deployment model fit your product.

FAQ

Event tracking questions

What is event tracking?

Event tracking is the implementation layer that records page activity and named product actions with useful context.

What can the Vectr4 browser SDK capture?

The SDK supports pageviews, custom events, identify calls, properties, click and form autocapture, behavioral interaction signals, batching, and retries.

How is event tracking different from event analytics?

Tracking captures and sends events. Event analytics interprets those events with identity, properties, funnels, sessions, and user paths.

Should event properties include sensitive data?

No. Keep payloads deliberately small and exclude passwords, tokens, payment details, and unnecessary personal or free-form sensitive data.