A marketer wants to create a segment and define the segmentation evaluation in Edge. Which would the team enable to ensure these events are ingested and processed for segmentation in real-time on the

Question

Options

• ACapture web event data through HTTP API
• BCapture web event data through WebSDK
• CCapture web event data through Adobe Analytics Data Connector
• DCapture web event data through Azure Data Lake Storage

• A
  14% (6)
• B
  75% (33)
• C
  7% (3)
• D
  5% (2)

Explanation

Option B is correct because Adobe's Web SDK (WebSDK/Alloy.js) is specifically designed to stream event data directly to the Adobe Experience Platform Edge Network, enabling real-time evaluation of segmentation rules at the edge before data even reaches the core platform.

Why the distractors are wrong:

• A (HTTP API): While the Edge Network HTTP API can ingest events, it is a server-side solution intended for server-to-server or non-browser contexts and does not natively support real-time edge segmentation in the same seamless way WebSDK does for web properties.
• C (Adobe Analytics Data Connector): This is a source connector that imports historical Analytics data in batch format into AEP - it has no capability for real-time edge processing.
• D (Azure Data Lake Storage): This is a cloud storage service for bulk/batch data ingestion, entirely incompatible with real-time edge event processing.

Memory tip: Think of the Web SDK as the "on-ramp to the Edge highway" - it's the only client-side tool built natively for the Edge Network, so any question involving real-time, edge, and web events together should immediately point you to WebSDK.

No community discussion yet for this question.