Analytics pipeline

Tenant-scoped event ingestion, attribution, aggregation, and diagnostics for link and mobile journeys.

Event lifecycle#

Validate

Events are authenticated, size-limited, and validated before acceptance.

Deduplicate

A stable event identifier prevents duplicate processing.

Attribute

Eligible outcomes can be connected to a prior human link decision.

Aggregate

Dashboards use scoped rollups without exposing cross-tenant data.

Submit events#

Send custom product events or supported retention events through the SDK analytics endpoints. Include a stable event identifier, event type, occurrence time, and the available journey context.

http

POST /api/v1/sdk/analytics/events
Authorization: Bearer <sdk-key>
Content-Type: application/json

Note

Retry only requests that return a retryable status, and reuse the same event identifier.

Privacy and isolation#

Every accepted event is scoped to the authenticated tenant and environment. Attribution rejects mismatched or expired journey context, and analytics output never combines tenants.

Delivery behavior#

Accepted events are processed asynchronously. Temporary processing failures are retried; exhausted deliveries are isolated for operator review without blocking unrelated events.