September 30, 2026

Choose what each source collects, users and events or events only, and stream high-volume raw events to Kafka with the new Raw events trigger.

Highlights

Choose What Each Source Collects

When you create a source, you now pick what it collects. Users and events, the recommended choice, builds a profile for every person, which journeys, experiences, recommendations and segments need. Events only keeps raw events without building profiles, for high-volume events you send straight to destinations. The choice is offered on JavaScript, Node.js, Python, PHP, iOS, Android and React Native sources, and it's set once per source. See What a source collects.

Stream Raw Events With the Raw Events Trigger

A new workflow trigger starts a run on every event from the Events only sources you pick. Pair it with Publish to Kafka to forward clickstream or telemetry to your own topic as it arrives. See Streaming raw events.

Two Event Meters, Each With Its Own Retention Window

Events are now billed on two meters: Identified events from users and events sources, and Events from events only sources. Each meter keeps data for the window you choose in Settings > Billing > Data retention. See Data retention, and the pricing page for rates.

Data & Sources

Every source panel asks the same two things: A connection name and what the source collects, before the source is created.
React Native is documented alongside the other sources: Creating a Source now covers connecting a React Native source.
Raw events are marked where they can't be used: The segment event picker flags events that come only from an Events only source, since a segment needs users.
Raw events show in Live data feed and event analytics: They add nothing to user analytics, which needs a user behind each event.

Workflows

The Raw events trigger has its own rules: Only True/false branch, Delay and Publish to Kafka can follow it, it can't share a workflow with other triggers, and its Kafka messages can't use user, account or attribute variables.
Clear errors before you publish: A raw events workflow names what's wrong on the node, such as a source that isn't Events only, and Publish stays off until it's fixed. See Publishing and versions.