Journey condition targeting segment doesn’t work
Learn why inSegment evaluates segment membership incorrectly.
Description description
Environment
Adobe Journey Optimizer (AJO)
Issue
A condition in a Journey using an inSegment clause did not execute as expected and returns incorrect results:
Journey starts with Read Segment (Segment A)
Journey contains condition with inSegment (Segment B)
=======================
Profile does not match condition criteria despite being in Segment B
=======================
Resolution resolution
inSegment evaluates segment membership incorrectly due to different merge policies in Read Segment journeys.
The merge policy needs to be the same for both segments.
Check the merge policy on a segment:
- Go to Segments.
- Open the segment and select Edit segment.
- Click on the gear icon and see the merge policy.
Alternatively, make an API call to check the merge policy ID for the two segments. For steps, refer to Retrieve a segment definition in API References in Adobe Experience Platform APIs.
Cause
This can happen if Segment A and Segment B have different merge policies. Make sure that both segments have the same merge policy.