Introduction
Tracebix is a multi-tenant customer signal platform for teams that need to understand what people do across websites, product experiences, tracked links, and transactional email—without assembling a second analytics pipeline for every channel.
Start with one event foundation
Every supported producer enters through the same versioned event boundary. Browser activity, server-side events, email pixels, and tracked-link clicks share common project, contact, and attribution rules before they reach timelines or analytics.
That gives teams three practical advantages:
- A consistent customer journey. Activity appears in context instead of as unrelated channel metrics.
- A smaller integration surface. Projects use dedicated credentials and strict schemas rather than bespoke ingestion paths.
- Predictable operations. Idempotency, usage accounting, privacy handling, and tenant isolation apply at the shared boundary.
Understand the journey
Capture
Use the lightweight browser SDK, Event API, or generated tracking links to collect approved behavioral signals. Browser rules can automate common page, click, and form events without granting the browser authority over tenant or contact data.
Connect
Projects, contacts, campaigns, rendered emails, and tracking links provide the business context around each signal. Tracebix can securely continue an identified email journey into a browser session without placing personal information in the URL.
Act
Contact timelines, conversion analytics, notifications, and signed webhooks turn the shared event stream into operational views and downstream actions.
Designed around trust boundaries
Tracebix derives organization and project authority on the server. Public clients never select a tenant, grant a paid plan, change usage, or submit a contact identifier as proof of identity. Credentials are scoped by purpose, sensitive tokens are short-lived, and privacy deletion cuts future identity continuity.
Current production scope
The first production release covers the tracking core: event ingestion, browser tracking, tracked links and pixels, contact activity, analytics, transactional notifications, and secure email-to-web continuity.
Campaign creation and rendered-email tooling are available in the product foundation, but Campaign Sending is not enabled in this release. Sender domains, campaign delivery, unsubscribe operations, and delivery pricing will pass their own independent launch gates.
Where to go next
The public documentation will grow with each approved product gate. Until then, the introduction is the supported overview of the production surface. For privacy and data handling, read the Privacy Policy.