To deliver next-page personalization using Adobe Target and AEP segments, several technical "handshakes" must be correctly configured within theEdge Networkarchitecture.

Step Bis foundational. For Adobe Target to receive segment membership information from AEP via the Web SDK, theDatastreammust be explicitly configured to support this. Under the Adobe Experience Platform service within the Datastream UI, the consultant must ensure that theEdge Segmentationtoggle is enabled. This setting allows the Edge Network to evaluate segments in real-time during the request. Additionally, thePersonalization Destinationsmust be active to allow Target to "see" these segment IDs in the edge response.

Step Caddresses the data assembly layer. Not all segments are automatically projected to the Edge Network. A segment must be evaluated using aMerge Policythat is marked asActive-on-edge. This flag tells the Profile Service to synchronize the necessary profile fragments and segment statuses to the Edge Network's distributed data centers. If the merge policy is not edge-enabled, the segment will only be evaluated in the Hub, causing a delay that prevents "next-page" personalization.

Option A is a legacy concern, as the Web SDK handles the delivery regardless of the specific Target extension version. Option D is incorrect because Target destinations are managed through Datastream configurations and segment activation, not a single-destination restriction. Debugging these two points (B and C) ensures the infrastructure is ready to process and deliver segment data at the speed required for real-time web experiences.