Creating an audience from specific index position from Array of obj

[Pradeep-Jaiswal]

This is the array of object field in AEP schema

{

   "model":[

      {

         "modelName":"PRP_TRIGGER_1Y_14DLAG",

         "modelScore":0.1243792474269867,

      },

      {

         "modelName":"PRP_60D_LAPS_1Y_REV1",

         "modelScore":0.7769704461097717,

      },

{

         "modelName":"PRP_SALON_TRIGGER_1Y_15DLAG",

         "modelScore":0.1443792474269867,

      }

   ],

   "sysIdentifiers":{

      "mId":"3646278"

   }

}

How can we create an audience by specifying the condition from specific index ?

lets say list of all customer where on 2nd index of the model object has "modelName"="PRP_60D_LAPS_1Y_REV1" ?

[TylerKrause]

Hey Pradeep, this should be an easy one! Because you've declared it as an object array in the schema it will load as such within the audiences UI. You just need to say where model name = PRP_60D_LAPS_1Y_REV1 and then filter on whatever criteria you need for the model score with an AND.

You won't be able to see it in the audience UI until you've made the dataset and loaded data through of an object array type.

Let me know if you have any questions!

Tyler Krause

[Pradeep-Jaiswal]

But how do I specify the index position, so it doesnt search across whole array ?

[TylerKrause]

That's the great thing - you ARE specifying the index position by doing this. By specifying which modelName you're looking for, it will pull that modelNames value automatically without you having to specify which index position itself.

AEP truly made it easier than you would expect.

Tyler Krause

[Pradeep-Jaiswal]

But the requirement is not to scan the entire array, but only scan the particular object from specific index position to find the MATCH.

[Prateek-Garg]

I don't think you can specify an index position when creating an audience. Besides that how will you make sure that index position is always 0 or 1 for model 1 and model 2.

I also stored data science models in AEP as an array and we are accessing it through model name in segmentation.

Data in profile store is stored in Cosmos DB as a distributed architecture. Queries are optimized by AEP based on audience filter criteria so performance should not be concern.

[Pradeep-Jaiswal · Accepted solution]

it have been told by adobe engineering that unfortunately current AEP segmentation UI doesnt support index based audience creation.