Ingest streaming events via HTTP API or SDK

This task produces a live event stream flowing from a web or mobile property into a platform dataset with sub-second latency. The output is a profile-enabled dataset whose record count and batch-status indicators grow as users interact with the property. Streaming ingestion is the primary path for capturing real-time behavioral signals that must be available for segmentation and personalization within seconds of occurrence.

Endpoint configuration. Streaming ingestion requires a named endpoint (a Datastream in AEP, a Source slug in Segment) linked to a destination dataset and schema. The endpoint validates each inbound event against the target schema; events failing validation are quarantined in an error dataset rather than silently dropped. Selecting the correct sandbox and enabling the "Profile" toggle on both the schema and dataset is a prerequisite — without it events land in storage but never hydrate profile records.

SDK vs. direct HTTP. An SDK (Web SDK, Mobile SDK) handles authentication, batching, retry on failure, and XDM serialization automatically. A direct HTTP API call gives more control for server-side or non-browser environments but requires the implementer to manage authentication tokens, construct the XDM payload explicitly, and handle HTTP errors. Both approaches result in the same inbound event shape; the choice is driven by deployment context.

Verification. The Dataset Activity dashboard shows total record counts and a time-series of recent batches. Each batch carries a Batch ID that can be used to retrieve detailed error information if records fail validation. The AEP Debugger extension (for SDK-based deployments) allows real-time inspection of edge network requests before they reach the dataset.

Parallel viability (high). Any cloud data platform provides an equivalent streaming ingest path: Segment's HTTP Source, Snowflake's Snowpipe, BigQuery's streaming insert API, or Kafka Connect. The structural pattern — endpoint + schema contract + dataset destination + monitoring — is universal. Phase 3 will document Segment HTTP Source configuration as a parallel implementation.