


I opened an idea for this topic as well. It would be great if AT 2.x call can get scope to AEP segment for the same ECID in context. I would be nice to avoid migrating all of our AT logic to behind alloy. I see that edge profile is available in the AT 2.x debug session but it looks like its returning a 404.
Topics help categorize Community content and increase your ability to discover relevant content.
Bumping this post as I'm my company has purchased AEP and we are currently operating with a hybrid implementation of WebSDK for AEP and at.js 2.x for Target.
My edgeProfile is also returning a 404 when observed with an mbox trace.
Has anyone had any luck with this?