Has anyone successfully used AEP edge profile with AT 2.x?

[Eric_Vidana]

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: "A29bnpLCe91cZPLPX7teFC8P", imsOrg: "XXXXX@AdobeOrg",…},…}

identity: "XXXXX"

latency_ms: 3

request: {xid: "A29bnpLCe91cZPLPX7teFC8P", imsOrg: "XXXXX@AdobeOrg",…}

allowCallToUps: false

imsOrg: "XXXXX@AdobeOrg"

liveDataMode: "MERGE_STRICT"

projectionName: "activationpulldefault"

requestId: "ac317ff2-2297-4212-a341-0fd1a913b0bb"

schemaName: "_xdm.context.Profile"

xid: "A29bnpLCe91cZPLPX7teFC8P"

status: "404"

[Jacob_T1]

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?