Configure a cloud-streaming activation destination
Define and authenticate a real-time streaming endpoint in a CDP platform so that audience segment qualifications can be delivered continuously to downstream consumers.
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.
Side-by-side implementations
In AEP Real-Time CDP, navigate to Destinations → Catalog and select the target streaming cloud destination (e.g., Azure Event Hubs under Cloud Storage). Supply the required authentication credentials — for Azure Event Hubs these are the SAS Key Name, SAS Key Value, Event Hubs Namespace, and Event Hub name, all retrievable from the Azure Portal's Shared Access Policies panel. After clicking "Connect to Destination" and receiving a Connected confirmation, provide a descriptive name for the connection, specify the target event hub name, and save. The resulting destination connection appears in Destinations → Browse and is immediately available for segment activation.
Capability: Audience Segmentation
Parallel implementation not yet available.
Hightouch routes qualified segments to Azure Event Hubs via its Event Streaming framework — there is no dedicated Azure Event Hubs destination connector in Hightouch's catalog (hightouch.com/docs/destinations/azure-event-hubs returns 404). Configuration uses the Event Streaming destination type, which requires the same four Azure credential parameters as AEP: Event Hubs Namespace, Event Hub name, SAS Key Name, and SAS Key Value. A Hightouch Sync on a real-time or micro-batch cadence (Lightning Sync Engine, formerly Live Syncs) routes segment qualification events to the Event Hub as JSON payloads, producing the same downstream consumer behavior as AEP's streaming destination. Note: Hightouch's Lightning Sync Engine approaches real-time but is not sub-second; use pattern.micro-batching-workaround if latency gap is relevant to the use case.
Capability: Reverse-ETL (CDW-to-Destination Sync)
Task-level sources
- technical-training/module13/index.md
- technical-training/module13/ex2.md
How is this implementation?
Sign-in-gated. Tomorrow morning's curriculum-ingestor consumes your feedback: "Inaccurate" queues the task for re-review, "needs update" queues it for a refresh, and "one vendor panel is wrong" re-drafts just that panel.