I am currently working on integrating RT-CDP audiences to be used in Adobe Target activities, but for the time being using at.js, instead of Adobe Experience Platform Web SDK.
During that work I found the following question:
Has anyone successfully used AEP edge profile with... - Adobe Experience League Community - 442184
CC: @Eric_Vidana and @Jacob_T1
I noticed that it was quite old and thus locked for commenting, so I wanted to create a post to share some of my findings.
First off, I too was getting the "404" status of my test profiles in the Adobe Target trace. I managed to change this to "200", after I ensured to include the following parameters in our Adobe Target implementation:
- aepSandboxId
- aepSandboxName
Documentation: How Do I Use the targetGlobalSettings() Function? | Adobe Target
The only way to fetch the Sandbox ID (in UUID format), is either to create a test audience in the relevant sandbox and activate it towards Adobe Target - once in Target you can open the audience details and get the ID. Otherwise, you should be able to ask Adobe support for the information.
Next up was to test the audiences towards Target activities - this one was a bit trickier, as I had created both an AEP Web SDK and at.js destination towards Adobe Target. This is not possible, as only one(?) destination is allowed per sandbox. Once I deleted the destination based on the AEP Web SDK the at.js based worked as intended.
It could also be that there can only be one type of destination; AEP Web SDK or at.js based - I have yet to test this.
The way to troubleshoot this is to look at the Target trace information and then note down the value in the projectionName parameter.
Using that, together with the sandbox name and ID, you are able to use the "List an edge projection" API call to fetch information about the destination in use.
There does not seem to be any documentation on the API framework for projections yet, but you can fetch the Postman collection containing the API requests on Adobe's GibHub:
experience-platform-postman-samples/apis/experience-platform/Real-time Customer Profile API.postman_...
One update is needed though, because the following header is missing from the collection; "x-sandbox-id", where the aforementioned sandbox ID is required.
I hope this can help you in your efforts to utilise AEP audiences in Adobe Target 🙂
