We are following the instructions here to set the identity name space for our mobile app: https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/app-implementation/identity. But I am unable to verify it in adobe assurance and no identifies are coming through. Has anyone run i...

I see. What I am trying to do is the opposite.

I failed to mention that this is a mobile application implementation. Are you saying that the below worked for you? I am assuming _mycompany would be a custom schema we have to create before sending the data, correct?_mycompany.shoolName -> _experience.analytics.customDimensions.eVars.eVarX

Thank you, I will review the article!

Thank you for your answers. Regarding context data, do you know if we can just have context data at the same level as experience? Below is what I have from the devs. Or do you think the values should be inside of the context data field under _experience? Here is the context data field i found 

Context:This is Mobile app implementationwe are successfully receiving pageview events, events, props, and evars without mapping, by simply doing the below (getting the mob dev team to send an XDM in the payload that matches the _experience fields, sending event type, and web:webPageDetails datasend...

That's neat. Thank you for sharing. Where do the contextdata values go? Are you able to map those into props and evars?

interesting. do you have an example of what the payload looked like? Also how did adobe analytics know what to map to props and evars?

ok. i will try that!

Hi John,  Yes this helps a lot. You asked:"For your first example that shows up in reporting, is there any reason why you need to map the same field (_experience.analytics.customDimensions.props.prop36) to itself?" I was surprised I had to map it. it doesn't work unless I do. This might be because I...