Understanding Bizzkit Tracking

Bizzkit Tracking (also known as Bizzkit Event Tracker, or BET) is a multi-tenant event tracking service designed to capture user behavior data from webshops in real time. It ingests events at high volume, processes them asynchronously, and stores them in an analytics-optimized format for downstream consumption.

What is it used for?

Bizzkit Tracking enables data-driven features across the Bizzkit platform:

• Product analytics — Understand which products are clicked, added to cart, and purchased.
• Search analytics — Measure search relevance by correlating search queries with user actions.
• Personalization — Feed behavioral signals into ranking and recommendation models.
• Commercial insights — Track order values and product performance over time.

How it works

The system follows an event-driven architecture:

1. Event submission — Webshops (via a frontend JavaScript SDK or a backend .NET SDK) submit events to the Event Receiver API.
2. Buffering — Events are buffered for reliable, high-throughput processing.
3. Processing — An Event Processor consumes events and stores them in an analytics-optimized format.
4. Consumption — Other Bizzkit services consume the processed event data to power features like personalization and commercial insights.

Multi-tenancy and instrumentation keys

Bizzkit Tracking is deployed as a single shared instance per environment. All customers share the same infrastructure, but data is fully isolated by tenant.

Events are routed to the correct tenant and segment using instrumentation keys — opaque identifiers that map to a specific (tenantId, segmentId) pair. This design supports:

• Key rotation — A compromised key can be revoked without affecting historical data.
• Multiple keys per segment — Different applications can use separate keys that all map to the same segment.

Event types

The following event types are supported: