@shubham10  For that specific profile's identity graph, are there more than 50 identities associated with it by chance?

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.

Hi @SwathiBu  It may be helpful to look into the computed attributes function of AEPhttps://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview

Hello @SamPo1  From my understanding, AEP does not keep a historical record of those sample jobs used in the estimator tool. Here is some information I found regarding the sample jobs: Audience estimates are generated by using a sample size of that day’s sample data. If there are less than 1 millio...

@jlasso71 @brekrut  Thanks Bryan, this answer is very helpful! This type of segment still would not be available for edge evaluation though, correct? Because the edge profile is only going to be updated once per day on batch evaluation?

Hi @jlasso71  If the data feeding this attribute is ingested via batch, the audience will automatically default to Batch evaluation, and would not qualify for Edge evaluation. Real time evaluation warrants the need for real time data.

Hi @Michael_Soprano  Please check out this information here: Segment definitions Whether created using the API or using the Segment Builder, segment definitions are ultimately defined using Profile Query Language (PQL). This is where the conceptual segment definition gets described in the language ...

@BitunSenAEP I do agree with you on this. It becomes very complex this way. I would recommend adding an enhancement request in the "idea's" section of the community stating this request. I have seen success in doing this.

Hi @NickMannion  I don't believe the documentation states directly which day of the week it would be, but if I had to guess, it would be over the weekend sometime. It may help to reach out to your Adobe Support rep to find out more info specific to your org.

@PratheepArunRaj I thought this as well, but I don't think that you would be able to use before/after conditions in this instance since we can't capture a rolling "current timestamp" in the before or after condition within the UI? Please correct me if i'm wrong here.