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. trace: {clientCode: "XXXXX",…}campaigns:
[]clientCode: "XXXXX"edgeProfile: {,…}profiles: [{request: {xid:
"A29bnpLCe91cZPLPX7teFC8P", imsOrg: "XXXXX@AdobeOrg",…},…}]0: {request:
{xid: "A29bnp...