New Participant

Invalid profile qualified in segmentation

Forum|Forum|1 year ago
January 29, 2025
4 replies
2066 views

Hi All,

In my source file I noticed conflicting values for a specific attribute for the same identity and ingested data in the customer profile dataset as shown below:

Customer ID	Gender	LastUpdated
ID1	Female	2025-01-13 12:00:00
ID1	Male	2025-01-13 12:00:00

After fragmentation, in profile store I can see the value updated as "Male" (see below screenshot). I've verified using API and it gives me the same result

However, when I created an audience it qualified for "Female" only. I have cross checked the merge policy and its selected as default timebased (see below screenshot)

In my sandbox, I used only default timebased merge policy only.

Please help me to understand is there anything that I missed something or how segmentation works?

Experience Platform

kautuk_sahni

Employee

@shubham10 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

Kautuk Sahni

TylerKrause

New Participant

@shubham10 Have you tried rebuilding the audience? Obviously not ideal, but we have unfortunately seen issues similar to this in the past. We opened up a support ticket to get it resolved, it required an Adobe back end refresh.

I would additionally set up an additional audience for that customer id with an experience for male as well. If the profiles qualifies for both, that is a clear issue that would need to get resolved by the Adobe support team.

S

shubham10Author

New Participant

Yes @tylerkrause , I created a test segment and can see the same result. I'll also create a Adobe ticket to understand why this type of issues occur frequently now.

PratheepArunRaj

New Participant

Dear @shubham10 ,

Is the attribute a part of the batch source/dataset? Because data ingested using a batch-based source will be evaluated nightly, even if it qualifies for streaming segmentation.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

S

shubham10Author

New Participant

Hi @pratheeparunraj yes its a part of batch data and I ingested this on 13th Jan 2025. Even after 15 days I can see in profile store its "male" but the profile is qualified for female in segmentation.

nnakirikanti

New Participant

@shubham10 Can you share your segmentation screenshot?

DavidRoss91

New Participant

Hi @shubham10

Trying to understand better here.. Did you ingest a gender value of "Male" and "Female" for the same identity value, at the same timestamp? I know that this can potentially cause issues when ingested at the exact same time.