Adobe Target API Information

[aem_2718]

Hello Team,

We are currently working on a proof of concept (POC) where we intend to use the AEP audience and profile attribute in Adobe Target. We plan to consume the audience and profile attributes in an m-box, which will be consumed for a mobile app using API.

However, we are having difficulties using the delivery API to call such mbox, which uses AEP audience and returns profile attributes. We've noticed that such AEP audience reflects as platform segments rather than actual attributes. Could you please guide us on whether the delivery API supports the AEP audience and returns AEP profile attributes? If not, would we need to explore any other API (AEP Web SDK) to accomplish this?

Thanks.

[shafiiub · Accepted solution]

 (mBox) Profile attribute in Adobe Target populated the values in Target Admin console for audience selection 

In Target Legacy API v2 this is referred as (profileParameters)
https://developers.adobetarget.com/api/legacy-api/index.html#batch-input-parameters

In Target Delivery API this is referred as (context)

https://developer.adobe.com/target/implement/delivery-api/#operation/execute

AEP Segments and mBox Profile attribute (context/profileParameters) all will be available part of target campaign creation part of the Audience selection

[bryan_w_bounteo]

Are the AEP profile attributes available to enable in the Response Tokens?

Also, for mobile you might consider using the `Adobe Journey Optimizer - Decisioning Extension` with accompanying Optimize library.  The Delivery API hits Target directly whereas this goes through an Edge datastream.