Configure a cloud-streaming activation destination

Configuring a cloud-streaming activation destination produces a live, authenticated connection between a CDP platform and a real-time event-streaming service. The key decisions involve selecting the appropriate protocol and authentication mechanism required by the target system (shared-access signatures, API keys, OAuth tokens, etc.), naming the connection clearly for operational visibility, and scoping which event hub, topic, or stream partition will receive segment payloads.

The primary output is a reusable destination connection object that can be referenced by multiple activation flows. Once the connection is saved, any authorized segment can be mapped to it without re-entering credentials. Teams should evaluate latency requirements, throughput limits, and cost models of the target streaming service before committing — different cloud providers have substantially different pricing for high-volume segment activations.

This task is highly parallel across CDPs. Any platform with a streaming activation capability (Snowflake Dynamic Tables with Fivetran Activations, Hightouch, Rudderstack, etc.) can target Azure Event Hubs, AWS Kinesis, or Confluent Kafka by configuring the appropriate connector with the same authentication parameters. The configuration steps are platform-specific, but the underlying decision framework — identifying the namespace, authentication scope, and stream name — is identical.