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 returnin...
Description - Allow AT 2.x access to edge profile from AEPWhy is this feature important to you - it would keep me from removing AT on the siteHow would you like the feature to work - Target audiences have a new drop down for edge profileCurrent Behaviour - It seems that you only get access to AEP se...
Would give this a read - https://experienceleague.adobe.com/docs/target/using/activities/experience-targeting/create-targeting/xt-switching-experiences.html?lang=en
So this is doable ... its not much fun though. https://developers.adobetarget.com/api/#admin-apis You essentially need to fetch all activities. Then all the activity info. Then all the audience ids in said activity. Then fetch each audience id. I manage to do with with a few mysql tables. After the ...
I believe it is done at the mbox level: "mboxes":[{"name":"asldkfjlaksdjflksjfd-pos-1","index":1,"parameters": {"bucket": "d","asdfas": "83833","erdaf": "eradf"}}]
If you are comfortable with little bit of client-side javascript and firing off a custom mbox name, you could wire up all of your HTML event clicks to the same mbox name and then set up your Conversion metric to be "Viewed an mbox" instead of clicked an element. The implementation would depend on wh...
I think a bit more information would be needed to help solve your problem. Your activity location field should be some key that you come up. They were formerly known as mbox names. I haven't seen any implementation with the location name being the url string. I would rely on the entry audience for l...