A cruise and theme-park company has implementations of Adobe Experience Platform and Target.
Which two statements correctly describe the requirements for using Edge segment implementation to support next-page personalization?
Because the Edge Network only has access to a limited, cached slice of profile data, edge (streaming) segmentation can evaluate only certain segment definition shapes: a single incoming event, a single incoming event combined with profile attributes, profile-attribute-only definitions, or a segment-of-segments where a nested segment referenced via an inSegment condition is itself profile-only (and therefore free of the sub-24-hour constraint, allowing a longer lookback such as 20 days). Definitions that aggregate multiple discrete events are not eligible for edge evaluation. Separately, delivering an audience for next-page personalization through an Edge Network destination requires the merge policy governing that audience to be explicitly marked active/enabled on Edge, since the default (non-edge) merge policy is not used to resolve identities and attributes during edge-time evaluation.
Community Discussion