Correct, I have edited my comment  thanks for flagging

@MrMAK here you have an API that gets some properties from Journeys like created by, published by inside the metadata object https://developer.adobe.com/journey-optimizer-apis/references/journeys/#operation/com/adobe/voyager/service/authoring/restapis/v1_0/swaggerendpoints/post/list_endpointconfigs....

Hey @Parvesh_Parmar thanks for your answer! Still where in the documentation it states that it will treat them as an "OR" as per my understanding is "AND" so if one field is available and the other is not, it won't push it to the destination 

@Caveman77 Have you try using audience composition? - This will create other audiences and if you are only trying to get counts might not be the best option. But you will be sure that you are not sending any actionshttps://experienceleague.adobe.com/en/docs/experience-platform/segmentation/ui/audien...

Did you add other environment requirements - like sandbox name etc? Which error are you getting? Are you able to generate the token to execute the API calls?

@HariKo1  Where you able to get those fields? 

For this current case @ElenaGor I have used a split condition inside the journey using this function matchRegExp(<parameters>) to identify if the language is written in Arabic or Latin alphabet (this also validate if the first name exist or not). Then in the Content you added specific personalizatio...

Have you tried by excluding users of the journey version id? that way you make you sure you don't target them again 

Hi @ZoeAG @SatheeskannaK We are also having the same issue, seems that the "data-medialibrary-id" and "data-mediarepo-id" tags are being generated inside the "src" tagAdobe is investigating the issue still. See below example - Blue box how it should be configured - Red box how its being configured a...