Edge segmentation is the correct choice for same-page and next-page personalization because it evaluates segments with extremely low latency directly on the Adobe Experience Platform Edge Network. As data is collected from a user's interaction, segment qualification happens instantaneously, allowing for immediate personalization on the current page or the very next one the user visits. This process avoids the latency inherent in sending data to the central Real-Time CDP store for processing, which is crucial for in-the-moment user experiences.

A. Streaming segmentation: While it offers near real-time qualification, it processes data as it arrives at the central platform, which introduces more latency than edge evaluation, making it less ideal for instantaneous, same-page personalization.

C. Batch segmentation: This method processes data on a fixed schedule (typically daily), making it unsuitable for any real-time use case as segment qualifications are not updated immediately after a user's action.

1. Adobe Experience League Documentation - Segmentation overview: This document explicitly contrasts the evaluation methods. It states

"Edge segmentation: The ability to evaluate segments in Experience Platform instantaneously on the Edge Network

allowing for same-page and next-page personalization use cases."

Source: Adobe Experience Platform Documentation

"Segmentation overview

" Section: "Evaluation methods."

2. Adobe Experience League Documentation - Edge segmentation: This guide details the specific purpose of edge segmentation. It clarifies

"The primary benefit of performing segmentation on the Edge is that it allows for same-page and next-page personalization use cases... evaluation is performed as data is streamed into Platform

rather than running a segmentation job on existing data in the data lake."

Source: Adobe Experience Platform Documentation

"Edge segmentation

" Section: "Introduction to edge segmentation."

3. Adobe Experience League Documentation - Batch and streaming segmentation: This page describes the other methods

highlighting their different latency characteristics. For batch

it notes

"A new segmentation job is created every 24 hours." For streaming

it notes qualification happens as data flows in

but the context is always data arriving at the central service

not at the edge.

Source: Adobe Experience Platform Documentation

"Create a segment

" Section: "Batch and streaming segmentation."