Not yet

Yes, we do have it enable along with Edge segmentation.

You don't need it until you do, then, it is too late haha. I guess you have also encountered the profile richness license usage guardrail, at least that was the first time I wish I had this function.  Really helpful idea, you have all my support. 

Descripción - Me and my colleagues are using the set auto_to_json function a ton while querying, partially it is because it only works for a single session. Therefor, one day, I thought that it would be a low effort hight reward implementation inside the query service UI.  This function might be imp...

Yes, they are, the last screenshot I sent are from the Profile Endpoint: https://platform.adobe.io/data/core/ups/access/entities

This is the exact problem, with this call, I am getting this response for this call: No profile attributes. As I show in the screenshot above, this profile does have attributes but I am unable to see them. We exported first name and custom_personalization attributes to the Custom personalization wit...

Thank you, @maggod You are totally right. I tried the interaction API call and I got this response: I was expecting the segmentMembership and the attributes, but I can't see those. Did I forget to toggle anything? Any idea of what could be possible happening?

We have configured the destination and mapped some attribues: The flow was as following: 1. Created a audience2. Created a profile3. Send an event that qualified the profile for the audience4. Checked the audienceMembership5. Sent a pageView via Web SDK and received this response: As you can see, th...

I am trying to send a payload va HTTP API, but I am getting this error: The user authorization token does not have 'DATASET.WRITE' permissions for the '*******-dev' sandbox. Could anyone tell me what exact permission and where should I enable it? Thank you in advance

Hi @Pradeep-Jaiswal, The problems that I see with the Map object that @Tof_Jossic sent the documentation are the restrictions:Map types MUST be of type object. --> No problemMap types MUST NOT have properties defined (in other words, they define “empty” objects). --> No problemMap types MUST include...