Streaming segment (profile attribute + event attribute) qualification behaviour. | Community
Skip to main content
R
RNA_Rohan
Level 2
June 22, 2026
Question

Streaming segment (profile attribute + event attribute) qualification behaviour.

  • June 22, 2026
  • 1 reply
  • 24 views

There is a streaming segment with condition - 

AttributesInclude First name equals latency

Events(Include audience who have at least 1 Any event where (Event Type equals latency.ingested) ) and occurs in last 10 minute(s)
 

Scenario 1 - 

event ingested first - no qualification

after 2 min profile ingested - imediate qualified to the segment.

--

Scenario 2 - 

after 10 min from first event ingestion 

the Profile got exited from the same segment.

qa) IS THIS EXPECTED? I have not ingested any event or profile attribute during this 10min.

--

Scenario 3 - 

after the profile got disqualified from the segment

Event ingested again without altering profile attributes - re qualified 

qb) IS THIS EXPECTED? Just event is ingested and the profile attributes from previous ingestion stays as it is.

 

Can some one give answers to qa and qb with supporting adobe documents.

 

 

 

 

    1 reply

    DineshK
    DineshK
    Level 3
    June 23, 2026

    Hi ​@RNA_Rohan, 

    Your segment has two conditions that must be true at the same time:

    • Profile attribute: firstName = "latency"
    • Event: eventType = "latency.ingested" within the last 10 minutes

    Scenario 1 — Expected

    The event came in first, but the profile didn't exist yet, so the attribute condition failed. No qualification.

    Two minutes later the profile ingested — attribute condition now true, and the event was still within the 10-minute window. Both conditions true at the same time → qualified immediately. Correct behaviour.
     

    qa — Scenario 2 — Expected

    The 10-minute event window is a sliding window that AEP re-evaluates continuously in real time. At T+10, the original event aged out. The event condition dropped to false, so the profile exited — even though you didn't change anything.

    This is the most misunderstood part of AEP streaming segmentation. It's not a one-time gate. The segment is evaluated continuously, and if a time-bound event condition lapses, the profile exits automatically.
     

    qb — Scenario 3 — Expected

    Profile attributes persist until overwritten. firstName = "latency" was still on the profile. When the new event came in, the event condition was true again, attribute condition was still true → re-qualified immediately. You never needed to re-ingest the profile data.


    https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/methods/streaming-segmentation

     

    R
    RNA_RohanAuthor
    Level 2
    June 24, 2026

    Hi Dinesh, thanks for the reply… I have one more doubt regaridng the diswualification of the profile after 10min - 
    So as per this faq - 
     

    the disqualificatoin depends on the profile attributes right? then in the 10min duration, I havenot altered any of the profile attributes… which mean it should not be disqualified .

    Or
    Is it like event is taking priority on the profile attributes?

    DineshK
    DineshK
    Level 3
    June 24, 2026

    The segment has two conditions: a profile attribute AND a time-bound event. That makes it a mixed segment, not a pure profile-attribute audience.

    The FAQ covers two separate cases:

    • Event-based condition → disqualification happens in real time as the lookback window expires
    • Profile attribute condition → disqualification happens when the attribute value changes

    The segment hits the first case, not the second.

    The 10-minute window on the event condition is what caused the exit — not anything to do with the profile attribute. The profile attribute was true the whole time and still is. But both conditions must be true simultaneously for the profile to stay qualified. When the event aged out, the event condition dropped to false. One condition false = exit. Profile attributes didn't change, and they didn't need to — the event window expiring was enough.

    So to directly answer the question — events aren't taking priority over profile attributes. Both conditions carry equal weight. The profile exited because the event side of the segment lapsed, not because anything changed on the profile side.

    Terms & ConditionsAccessibility statement

    Loading footer...