While using 'Segment Qualification' activity in journey, even after a profile getting qualified for segment, Journey is not getting triggered.
Journey is in ‘Live’ state and we are ingesting data using HTTP API streaming ingestion.
PFB details of the setup done.
Segment details:
Segment Name: IN Customers
Criteria: HomeAddress-->CountryCode eq "IN"
Journey Details
Journey Name: POCsegmentqualification
We are able to see data in segment
Solved! Go to Solution.
Views
Replies
Total Likes
@sankar1 Try creating a new segment and see if that helps to see that the profile qualifies for the segment. If not query the data lake and look at the specifics. Also, If it's a widespread issue that affects data used in Journey, I would suggest opening a ticket with support to troubleshoot the problem.
A couple of questions,
Views
Replies
Total Likes
Hi @SatheeskannaK @nnakirikanti ,
We are still seeking a resolution for this issue. Your help would be highly appreciated.
PFB my findings.
Batch Data Load (CSV/MySQL):
Segment Type-Streaming/Batch
Expected Result : Segment qualification will be triggered on Batch evaluation and Profile Fragment/Identity graph will be generated.
Actual Result :Segment qualification is getting triggered on Batch evaluation. Profile fragment/identify graph is getting created in 3-4 mins.
API Data Load:
Segment Type-Streaming
Expected Result : Segment qualification will be triggered near real time and Profile Fragment/Identity graph will be generated.
Actual Result :Segment qualification is getting triggered on Batch evaluation. Profile fragment/identify graph is not getting generated.
Views
Replies
Total Likes
Re. API Data Load:
Views
Replies
Total Likes
Hi @SatheeskannaK ,
We are adding profile data using API call, we have tried using postman and the data was getting loaded successfully in Profile dataset. But segment qualification is not getting triggered.
Views
Replies
Total Likes
@sankar1 Try creating a new segment and see if that helps to see that the profile qualifies for the segment. If not query the data lake and look at the specifics. Also, If it's a widespread issue that affects data used in Journey, I would suggest opening a ticket with support to troubleshoot the problem.
Thank you for your response
1.Yes, the journey was getting triggered in test mode.
2.No, profile was added to segment after publishing the journey.
Views
Replies
Total Likes
@sankar1 Add a "wait activity" of 1 to 3 minutes after read segmentation event, before consuming profile data, this is a guardrail/limitation of this.
Hope this solve the problem..
Views
Replies
Total Likes
Hi @nnakirikanti ,
Thank you for your response, I would definitely try this.
But my query is, the Segment qualification event itself is not getting triggered even if the profile becomes the member of a segment. We can consider adding wait activity if the event /journey is getting triggered .
Views
Replies
Total Likes
Views
Likes
Replies