Hi @SCB21,   What's the use case that you are trying to solve? Also which activation channel are you planning to use? How many ids are you currently storing in AEP?   Regards, Chetanya

Hi @Ivan_Mironchuk we have JO being used, will it work for that as well or it's only for AJO?

Hi @Ikmoo,   Here are some options: As Anuhya mentioned you can use OOB Action "Update Profile" and update the details at the profile level. The schema can be created based on your needs, there's no OOB schema available. Keep in mind that you need to design for a larger scope, multiple campaigns, an...

This would be the right channel to post your question - https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/bd-p/adobe-analytics-qanda 

Hi @Varunima for which product is this?

Hi @digitalNick    As far as I know, we do not have a way to filter (at datastream level) if we need to send it to Adobe solutions. For event forwarding, you should still be able to control it with rules/data elements at the data stream level. Alternatively, you can create multiple data streams to s...

Hi @KshamaN,   ECID is (by default) captured within IdentityMap, part of your web SDK schema (alloy.js).If you need to access ECID, then you can follow this https://experienceleague.adobe.com/docs/experience-platform/edge/extension/accessing-the-ecid.html?lang=en This way you can even store in a dat...

Hi @navink386520 please create an issue here - https://github.com/adobe/experience-platform-postman-samples/issues so that the team can prioritize it.

Thank you for the clarification @woutervangeluwe. Appreciate it!

@Gokul_Agiwal I am referencing the same video and he mentions this being legacy now. I have explicitly given the time where he mentions that. Looks like in the long run we all want to move toward the server-side and enforce FPID.